On Thursday, January 15, 2004 5:17 PM [GMT+1=CET],
Barak Korren [EMAIL PROTECTED] wrote:
Ian Brayshaw wrote:
On Tuesday 13 January 2004 9:29 am, Christian Schuerer wrote:
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan
On Tue, Jan 13, 2004 at 10:29:10AM +0100, Christian Schuerer wrote:
Hello!
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 00:05:01 asterix su[2102]: + ??? root:bin
Today there is even an additional line:
On Thursday, January 15, 2004 5:17 PM [GMT+1=CET],
Barak Korren [EMAIL PROTECTED] wrote:
Ian Brayshaw wrote:
On Tuesday 13 January 2004 9:29 am, Christian Schuerer wrote:
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan
On Tue, Jan 13, 2004 at 10:29:10AM +0100, Christian Schuerer wrote:
Hello!
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 00:05:01 asterix su[2102]: + ??? root:bin
Today there is even an additional line:
Ian Brayshaw wrote:
On Tuesday 13 January 2004 9:29 am, Christian Schuerer wrote:
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 06:25:01 asterix su[5741]: + ??? root:nobody
I now get similar messages in my logs
Yes, 'su' isn't called in the cron files, it's used to run the commands in
the cron files as the specified user.
So for example, my /etc/cron.d/mrtg contains:
0-55/5 ** * * rootif [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ]; then /usr/bin/mrtg /etc/mrtg.cfg
/var/log/mrtg/mrtg.log;
Ian Brayshaw wrote:
On Tuesday 13 January 2004 9:29 am, Christian Schuerer wrote:
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 06:25:01 asterix su[5741]: + ??? root:nobody
I now get similar messages in my
Yes, 'su' isn't called in the cron files, it's used to run the commands in
the cron files as the specified user.
So for example, my /etc/cron.d/mrtg contains:
0-55/5 ** * * rootif [ -x /usr/bin/mrtg ] [ -r
/etc/mrtg.cfg ]; then /usr/bin/mrtg /etc/mrtg.cfg
Hello!
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 00:05:01 asterix su[2102]: + ??? root:bin
Today there is even an additional line:
Jan 13 06:05:01 asterix su[5684]: + ??? root:bin
Jan 13 06:25:01 asterix
On Tue, 2004-01-13 at 10:29, Christian Schuerer wrote:
Hello!
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 00:05:01 asterix su[2102]: + ??? root:bin
Today there is even an additional line:
Jan 13
On Tuesday 13 January 2004 9:29 am, Christian Schuerer wrote:
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 06:25:01 asterix su[5741]: + ??? root:nobody
I now get similar messages in my logs after a recent upgrade of
Hello!
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 00:05:01 asterix su[2102]: + ??? root:bin
Today there is even an additional line:
Jan 13 06:05:01 asterix su[5684]: + ??? root:bin
Jan 13 06:25:01 asterix
On Tuesday 13 January 2004 9:29 am, Christian Schuerer wrote:
Since updating my debian server yesterday I get the following error
messages every hour (generated by logcheck):
Jan 13 06:25:01 asterix su[5741]: + ??? root:nobody
I now get similar messages in my logs after a recent upgrade of
13 matches
Mail list logo