In a flurry of recycled electrons, Mark Sapiro wrote:
> Larry Stone wrote:
>
> >> I'd stay away from an ampersand. It has a special meaning in Unix commands
> >> (means execute the previous command in the background) and unless properly
> >> escaped, will be taken for that special meaning every ti
John Fleming wrote:
Larry Stone wrote:
>> I'd stay away from an ampersand. It has a special meaning in Unix commands
>> (means execute the previous command in the background) and unless properly
>> escaped, will be taken for that special meaning every time it occurs in a
>> shell command.
>
>Than
I'd stay away from an ampersand. It has a special meaning in Unix commands
(means execute the previous command in the background) and unless properly
escaped, will be taken for that special meaning every time it occurs in a
shell command.
Thanks, Larry. I didn't find anything about it in the FAQ.
On 3/6/05 7:01 AM, John Fleming at [EMAIL PROTECTED] wrote:
> Well, it let me create the list and I could use bin/withlist commands on it
> by enclosing listname in single quotes. Everything looked fine, but when I
> tried my first post to the list, I got this back:
>
> The Postfix program
>
>
Well, it let me create the list and I could use bin/withlist commands on it
by enclosing listname in single quotes. Everything looked fine, but when I
tried my first post to the list, I got this back:
The Postfix program
.org>: Command died with status 127:
"/var/lib/mailman/mail/mailman pos
