-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 24 Sep 2003 09:26:55 +0800, Edward Dekkers wrote:
> OK, the real log files tell me the job was run at 4:08.31 and 'su news'
> was executed then, and logged out one second later.
>
> There IS a job in cron.daily called inn-cron-expire.
>
> T
On Wed, 24 Sep 2003 09:26:55 +0800
Edward Dekkers <[EMAIL PROTECTED]> wrote:
> Michael Schwendt wrote:
>
> > Check the real log files in /var/log, not the stripped-down
> > information presented to you by logwatch. Also check whether
> > it's a daily cron job in /etc/cron.daily
>
> OK, the real
Michael Schwendt wrote:
Check the real log files in /var/log, not the stripped-down
information presented to you by logwatch. Also check whether
it's a daily cron job in /etc/cron.daily
OK, the real log files tell me the job was run at 4:08.31 and 'su news'
was executed then, and logged out one s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 24 Sep 2003 08:20:42 +0800, Edward Dekkers wrote:
> I've googled on this and it HAS been asked before on a few lists, but
> I've found no answer.
>
> Logwatch tells me:
>
> su:
> Sessions Opened:
>(uid=0) -> news: 1 Time(s)
>
>
I've googled on this and it HAS been asked before on a few lists, but
I've found no answer.
Logwatch tells me:
su:
Sessions Opened:
(uid=0) -> news: 1 Time(s)
Every day I believe.
I don't have a news server installed, so I was just wondering what is
causing it. It's done it since day
