On Fri, 2008-10-17 at 19:45 +0300, Andrei Popescu wrote:
> On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
>
> > > this doesn't seem to be true the job runs and produces output and
> > > root mail is (via /etc/aliases - thanks to Doug!) sent to me but yet I
> > > don't get any o/p from /etc
On Fri, 17 Oct 2008 19:10:01 +0200, Emanoil Kotsev wrote:
>> On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
>>
>>> > this doesn't seem to be true the job runs and produces output
>>> > and root mail is (via /etc/aliases - thanks to Doug!) sent to me but
>>> > yet I don't get any o/p from
Andrei Popescu wrote:
> On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
>
>> > this doesn't seem to be true the job runs and produces output and
>> > root mail is (via /etc/aliases - thanks to Doug!) sent to me but yet I
>> > don't get any o/p from /etc/cron.daily jobs whereas I do from al
On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
> > this doesn't seem to be true the job runs and produces output and
> > root mail is (via /etc/aliases - thanks to Doug!) sent to me but yet I
> > don't get any o/p from /etc/cron.daily jobs whereas I do from all my
> > crontab jobs...
>
>
michael wrote:
> On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
>> On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
>>
>> > If I wish to have, say, a backup script running daily by the system (ie
>> > with su privileges) and to have access to any std out/err output what's
>> > the reco
On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
> On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
>
> > If I wish to have, say, a backup script running daily by the system (ie
> > with su privileges) and to have access to any std out/err output what's
> > the recommended Debian way to d
On Tue, Oct 14, 2008 at 02:55:15PM +0100, michael wrote:
> On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
> > On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
> > I think the standard output for jobs run out of cron.daily will
> > typically go to root's mailbox.
>
> Well, root seems not
On Tue, 2008-10-14 at 14:59 +0100, Dave Ewart wrote:
> On Tuesday, 14.10.2008 at 14:55 +0100, michael wrote:
>
> > > I suggest writing/rewriting backup.sh so that it writes its output
> > > to well-defined files, rather than relying on the behaviour of
> > > standard output/error.
> >
> > I thoug
On Tue, 2008-10-14 at 14:57 +0100, Steve Kemp wrote:
> On Tue Oct 14, 2008 at 14:55:15 +0100, michael wrote:
>
> > ratty:~# ls /var/mail
> > mail michael
> > ratty:~#
>
> You might find that /var/mail/mail is mail for the root user.
>
> Steve
well I did check it ;)
but it didn't have a rece
On Tuesday, 14.10.2008 at 14:55 +0100, michael wrote:
> > I suggest writing/rewriting backup.sh so that it writes its output
> > to well-defined files, rather than relying on the behaviour of
> > standard output/error.
>
> I thought about this but presumed if there was an already set-up
> mechani
On Tue Oct 14, 2008 at 14:55:15 +0100, michael wrote:
> ratty:~# ls /var/mail
> mail michael
> ratty:~#
You might find that /var/mail/mail is mail for the root user.
Steve
--
Managed Anti-Spam Service
http://mail-scanning.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
> On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
>
> > If I wish to have, say, a backup script running daily by the system (ie
> > with su privileges) and to have access to any std out/err output what's
> > the recommended Debian way to d
On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
> If I wish to have, say, a backup script running daily by the system (ie
> with su privileges) and to have access to any std out/err output what's
> the recommended Debian way to do so?
>
> I've tried
> a) create $HOME/bin/backup.sh script
>
13 matches
Mail list logo
