Displaying 4 results from an estimated 4 matches for "second_path".
2006 Sep 27
0
dovecot checkpassword passdb and vmailmgr
...odule is
supposed to
behave like dovecot expects from it. Otherwise, a comma appear after
the first path.
e.g.
passdb checkpassword {
args = /xyz/checkvpw,/libexec/vmailmgr-reply
}
if one needs to specify paths with commas in the first one, commas
can be escaped with \
(eg args=first\,path,second_path)
Last but not least, the patch addresses again the problem with colons
in paths.
Currently, dovecot dictates no colons can exist in mailbox path
names. In UNIX,
no such constraint exist. Moreover, paths with colons are common when
working
specifically with qmail (see dot-qmail).
When doveco...
2017 Mar 06
0
PATH directive searches in reverse order with wrong separator
...ive, in an attempt to reduce potential issues, was/is the
recommendation to use multiple PATH directives, each in a different
line/row in the configuration file, instead of using the path separator
within one same PATH directive.
In other words, the PATH directive accepts:
PATH first_path
PATH second_path
and the paths are appended to the list of searched-for paths (looking
for c32 (library) modules). I would suggest trying this alternative for
a test, independently of how the code might parse / mess up this
notation anyway.
Yet, again, real-world cases were not presented here.
Important remi...
2008 May 01
20
link_to meta programming question
I am trying to create a dynamic menu using the following construct:
<%- menu_list = [ ''first'', ''second'', ''third''] -%>
<ul>
<%- menu_list.each do |m| -%>
<%= link_to "List All #{m.titlecase.pluralize} <m>_path %>
<%- end -%>
</ul>
What I cannot determine is what I have to do to replace
2017 Mar 06
3
PATH directive searches in reverse order with wrong separator
I've been trying to get syslinux.efi working in my environment again...
Found what look like a bunch of little bugs that are very frustrating...
First, the documentation on the Wiki says that as of 5.11, the list
separator is space, not colon. But I can find no evidence that 5.11
was ever officially released or that a commit to git was made to make
this change. 6.00 and following still use