Prev: Linux is now a bona fide gaming platform!
Next: Building an Embedded Device/System? Tell VDC about your experiences for a chance to WIN!
From: Jim A on 15 May 2010 16:51
On 05/15/2010 09:41 PM, alexd wrote:
> On 15/05/10 19:05, Jim A wrote:
>
>> On Mandriva linux, the man page says:
>>
>> If MAILTO is defined but empty (MAILTO=""), no
>> mail will be sent.
>>
>> So I wonder if you're missing a couple of double-quotes?
>
> If I do that, it doesn't choke on that when loading it, it waits until
> it's running:
>
> A message that you sent contained a recipient address that was incorrectly
> constructed:
>
> (null) empty address
>
> The message has not been delivered to any recipients.
>
> ------ This is a copy of your message, including all the headers. ------
>
>
> From: root (Cron Daemon)
> To: (null)
> Subject: Cron <root(a)westogre> /usr/local/bin/mysar >>
> /usr/local/mysar/log/mysar-importer.log 2>&1 (failed)
> Content-Type: text/plain; charset=ISO-8859-1
> X-Cron-Env: <MAILTO=>
> X-Cron-Env: <SHELL=/bin/sh>
> X-Cron-Env: <HOME=/root>
> X-Cron-Env: <PATH=/usr/bin:/bin>
> X-Cron-Env: <LOGNAME=root>
>
> command failed with exit status 1
>
> However, reading this:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581612
>
> and putting || [ $? -eq 1 ] on the end of the command does the trick.
>

I'm glad you found a solution, and thanks for posting it. I'll watch
out for that one next time I upgrade.

--
www.slowbicyclemovement.org - enjoy the ride
From: Big and Blue on 15 May 2010 20:24
On 05/15/10 21:41, alexd wrote:

> and putting || [ $? -eq 1 ] on the end of the command does the trick.

or, presumably:

; exit 0

--
Just because I've written it doesn't mean that
either you or I have to believe it.
From: Bruce Stephens on 16 May 2010 06:50
Big and Blue <No_4(a)dsl.pipex.com> writes:

> On 05/15/10 21:41, alexd wrote:
>
>> and putting || [ $? -eq 1 ] on the end of the command does the trick.
>
> or, presumably:
>
> ; exit 0

I tend to use "|| true", FWIW.
From: Tony Houghton on 16 May 2010 07:48
In <87hbm8gly2.fsf(a)cenderis.internal>,
Bruce Stephens <bruce+usenet(a)cenderis.demon.co.uk> wrote:

> Big and Blue <No_4(a)dsl.pipex.com> writes:
>
>> On 05/15/10 21:41, alexd wrote:
>>
>>> and putting || [ $? -eq 1 ] on the end of the command does the trick.
>>
>> or, presumably:
>>
>> ; exit 0
>
> I tend to use "|| true", FWIW.

The bug report referred to above explains the reason for that construct:
it ignores the exit code of 1 but still warns about other non-zero codes
which you may want to know about.

--
TH * http://www.realh.co.uk
From: Bruce Stephens on 16 May 2010 09:07
Tony Houghton <h(a)realh.co.uk> writes:

> In <87hbm8gly2.fsf(a)cenderis.internal>,
> Bruce Stephens <bruce+usenet(a)cenderis.demon.co.uk> wrote:
>
>> Big and Blue <No_4(a)dsl.pipex.com> writes:
>>
>>> On 05/15/10 21:41, alexd wrote:
>>>
>>>> and putting || [ $? -eq 1 ] on the end of the command does the trick.
>>>
>>> or, presumably:
>>>
>>> ; exit 0
>>
>> I tend to use "|| true", FWIW.
>
> The bug report referred to above explains the reason for that construct:
> it ignores the exit code of 1 but still warns about other non-zero codes
> which you may want to know about.

Yes, that's a good reason.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Linux is now a bona fide gaming platform!
Next: Building an Embedded Device/System? Tell VDC about your experiences for a chance to WIN!