Debian bug report logs - #1531
syslogd continues to write to old file after savelog
Package: syslogd; Reported by: andrew@kryten.it.com.au (Andrew Howell); 29 days old.
Message received at debian-bugs:
From olis.north.de!indrom!joey Sat Oct 7 17:57:00 1995
Return-Path: <indrom!joey@olis.north.de>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t1cAb-000HsZC; Sat, 7 Oct 95 09:32 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA29084
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 7 Oct 1995 08:36:51 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
id <m0t1aHB-0000BuC>; Sat, 7 Oct 95 15:30 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
id <m0t1aCv-0001nCC@olis.north.de>; Sat, 7 Oct 95 15:26 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
by finlandia.Infodrom.North.DE from joey (Martin Schulze)
id m0t1YMt-000K0vC; Sat, 7 Oct 95 13:28 MET
Message-Id: <m0t1YMt-000K0vC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
To: andrew@kryten.it.com.au, debian-bugs@pixar.com
Date: Sat, 7 Oct 1995 13:28:43 +0100 (MET)
In-Reply-To: <m0szyTf-000AZYC@kryten.it.com.au> from "Andrew Howell" at Oct 3, 95 11:57:10 am
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1470
Hallo Andrew Howell!
}Package: syslogd
}Version: 1.2-11
}
}As you can see below the syslogd is still writing to daemon.0 after
}savelog ran on Oct 1st.
}
}-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
}-rw-r--r-- 1 root adm 207110 Oct 3 11:52 /var/log/daemon.0
}
}root 97 0.0 0.8 73 132 ? S Sep 28 1:01 /sbin/syslogd
}
}After I kill -HUPed the syslogd process it started writing to the
}proper logs i.e. daemon again.
}I just looked into this a little more. It seems that the /var/run
}file for syslog has changed. /etc/cron.weekly/sysklogd tries to
}do this.
}
}kill -1 `cat /var/run/syslog.pid`
}
}but the file in /var/run is now this
}
}-rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
I have problems to follow you. In my version 1.2-11 the
/etc/cron.weekly/sysklogd file calls:
--------------------------------------------------
# Restart syslogd.
kill -1 `cat /var/run/syslogd.pid`
--------------------------------------------------
So this is the correct file.
Regards,
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ +49-441-777884 * Login&Passwd: nuucp * Index: ~/ls-lR.gz /
/ Whenever you meet yourself you're in a time loop /
/http://home.pages.de/~joey/ or in front of a mirror /
----------------------------------------------------------------
16.10.95: Oldenburger Usenet(ter) Treffen, ab 20h im Dreieck
Acknowledgement sent to joey@finlandia.Infodrom.North.DE (Martin Schulze)
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From olis.north.de!indrom!joey Sat Oct 7 17:52:59 1995
Return-Path: <indrom!joey@olis.north.de>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t1bRB-000HoJC; Sat, 7 Oct 95 08:45 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA29084
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 7 Oct 1995 08:36:51 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
id <m0t1aHB-0000BuC>; Sat, 7 Oct 95 15:30 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
id <m0t1aCv-0001nCC@olis.north.de>; Sat, 7 Oct 95 15:26 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
by finlandia.Infodrom.North.DE from joey (Martin Schulze)
id m0t1YMt-000K0vC; Sat, 7 Oct 95 13:28 MET
Message-Id: <m0t1YMt-000K0vC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
To: andrew@kryten.it.com.au, debian-bugs@pixar.com
Date: Sat, 7 Oct 1995 13:28:43 +0100 (MET)
In-Reply-To: <m0szyTf-000AZYC@kryten.it.com.au> from "Andrew Howell" at Oct 3, 95 11:57:10 am
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1470
Hallo Andrew Howell!
}Package: syslogd
}Version: 1.2-11
}
}As you can see below the syslogd is still writing to daemon.0 after
}savelog ran on Oct 1st.
}
}-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
}-rw-r--r-- 1 root adm 207110 Oct 3 11:52 /var/log/daemon.0
}
}root 97 0.0 0.8 73 132 ? S Sep 28 1:01 /sbin/syslogd
}
}After I kill -HUPed the syslogd process it started writing to the
}proper logs i.e. daemon again.
}I just looked into this a little more. It seems that the /var/run
}file for syslog has changed. /etc/cron.weekly/sysklogd tries to
}do this.
}
}kill -1 `cat /var/run/syslog.pid`
}
}but the file in /var/run is now this
}
}-rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
I have problems to follow you. In my version 1.2-11 the
/etc/cron.weekly/sysklogd file calls:
--------------------------------------------------
# Restart syslogd.
kill -1 `cat /var/run/syslogd.pid`
--------------------------------------------------
So this is the correct file.
Regards,
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ +49-441-777884 * Login&Passwd: nuucp * Index: ~/ls-lR.gz /
/ Whenever you meet yourself you're in a time loop /
/http://home.pages.de/~joey/ or in front of a mirror /
----------------------------------------------------------------
16.10.95: Oldenburger Usenet(ter) Treffen, ab 20h im Dreieck
Acknowledgement sent to joey@finlandia.Infodrom.North.DE (Martin Schulze)
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From olis.north.de!indrom!joey Sat Oct 7 09:44:53 1995
Return-Path: <indrom!joey@olis.north.de>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t1cMi-000HwhC; Sat, 7 Oct 95 09:44 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA29084
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 7 Oct 1995 08:36:51 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
id <m0t1aHB-0000BuC>; Sat, 7 Oct 95 15:30 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
id <m0t1aCv-0001nCC@olis.north.de>; Sat, 7 Oct 95 15:26 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
by finlandia.Infodrom.North.DE from joey (Martin Schulze)
id m0t1YMt-000K0vC; Sat, 7 Oct 95 13:28 MET
Message-Id: <m0t1YMt-000K0vC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
To: andrew@kryten.it.com.au, debian-bugs@pixar.com
Date: Sat, 7 Oct 1995 13:28:43 +0100 (MET)
In-Reply-To: <m0szyTf-000AZYC@kryten.it.com.au> from "Andrew Howell" at Oct 3, 95 11:57:10 am
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1470
Hallo Andrew Howell!
}Package: syslogd
}Version: 1.2-11
}
}As you can see below the syslogd is still writing to daemon.0 after
}savelog ran on Oct 1st.
}
}-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
}-rw-r--r-- 1 root adm 207110 Oct 3 11:52 /var/log/daemon.0
}
}root 97 0.0 0.8 73 132 ? S Sep 28 1:01 /sbin/syslogd
}
}After I kill -HUPed the syslogd process it started writing to the
}proper logs i.e. daemon again.
}I just looked into this a little more. It seems that the /var/run
}file for syslog has changed. /etc/cron.weekly/sysklogd tries to
}do this.
}
}kill -1 `cat /var/run/syslog.pid`
}
}but the file in /var/run is now this
}
}-rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
I have problems to follow you. In my version 1.2-11 the
/etc/cron.weekly/sysklogd file calls:
--------------------------------------------------
# Restart syslogd.
kill -1 `cat /var/run/syslogd.pid`
--------------------------------------------------
So this is the correct file.
Regards,
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ +49-441-777884 * Login&Passwd: nuucp * Index: ~/ls-lR.gz /
/ Whenever you meet yourself you're in a time loop /
/http://home.pages.de/~joey/ or in front of a mirror /
----------------------------------------------------------------
16.10.95: Oldenburger Usenet(ter) Treffen, ab 20h im Dreieck
Acknowledgement sent to joey@finlandia.Infodrom.North.DE (Martin Schulze)
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From olis.north.de!indrom!joey Sat Oct 7 17:50:14 1995
Return-Path: <indrom!joey@olis.north.de>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t1bJL-000HnBC; Sat, 7 Oct 95 08:37 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA29084
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 7 Oct 1995 08:36:51 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
id <m0t1aHB-0000BuC>; Sat, 7 Oct 95 15:30 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
id <m0t1aCv-0001nCC@olis.north.de>; Sat, 7 Oct 95 15:26 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
by finlandia.Infodrom.North.DE from joey (Martin Schulze)
id m0t1YMt-000K0vC; Sat, 7 Oct 95 13:28 MET
Message-Id: <m0t1YMt-000K0vC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
To: andrew@kryten.it.com.au, debian-bugs@pixar.com
Date: Sat, 7 Oct 1995 13:28:43 +0100 (MET)
In-Reply-To: <m0szyTf-000AZYC@kryten.it.com.au> from "Andrew Howell" at Oct 3, 95 11:57:10 am
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1470
Hallo Andrew Howell!
}Package: syslogd
}Version: 1.2-11
}
}As you can see below the syslogd is still writing to daemon.0 after
}savelog ran on Oct 1st.
}
}-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
}-rw-r--r-- 1 root adm 207110 Oct 3 11:52 /var/log/daemon.0
}
}root 97 0.0 0.8 73 132 ? S Sep 28 1:01 /sbin/syslogd
}
}After I kill -HUPed the syslogd process it started writing to the
}proper logs i.e. daemon again.
}I just looked into this a little more. It seems that the /var/run
}file for syslog has changed. /etc/cron.weekly/sysklogd tries to
}do this.
}
}kill -1 `cat /var/run/syslog.pid`
}
}but the file in /var/run is now this
}
}-rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
I have problems to follow you. In my version 1.2-11 the
/etc/cron.weekly/sysklogd file calls:
--------------------------------------------------
# Restart syslogd.
kill -1 `cat /var/run/syslogd.pid`
--------------------------------------------------
So this is the correct file.
Regards,
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ +49-441-777884 * Login&Passwd: nuucp * Index: ~/ls-lR.gz /
/ Whenever you meet yourself you're in a time loop /
/http://home.pages.de/~joey/ or in front of a mirror /
----------------------------------------------------------------
16.10.95: Oldenburger Usenet(ter) Treffen, ab 20h im Dreieck
Acknowledgement sent to joey@finlandia.Infodrom.North.DE (Martin Schulze)
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From olis.north.de!indrom!joey Sat Oct 7 17:49:47 1995
Return-Path: <indrom!joey@olis.north.de>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t1bh1-000HpYC; Sat, 7 Oct 95 09:01 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA29084
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 7 Oct 1995 08:36:51 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
id <m0t1aHB-0000BuC>; Sat, 7 Oct 95 15:30 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
id <m0t1aCv-0001nCC@olis.north.de>; Sat, 7 Oct 95 15:26 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
by finlandia.Infodrom.North.DE from joey (Martin Schulze)
id m0t1YMt-000K0vC; Sat, 7 Oct 95 13:28 MET
Message-Id: <m0t1YMt-000K0vC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
To: andrew@kryten.it.com.au, debian-bugs@pixar.com
Date: Sat, 7 Oct 1995 13:28:43 +0100 (MET)
In-Reply-To: <m0szyTf-000AZYC@kryten.it.com.au> from "Andrew Howell" at Oct 3, 95 11:57:10 am
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1470
Hallo Andrew Howell!
}Package: syslogd
}Version: 1.2-11
}
}As you can see below the syslogd is still writing to daemon.0 after
}savelog ran on Oct 1st.
}
}-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
}-rw-r--r-- 1 root adm 207110 Oct 3 11:52 /var/log/daemon.0
}
}root 97 0.0 0.8 73 132 ? S Sep 28 1:01 /sbin/syslogd
}
}After I kill -HUPed the syslogd process it started writing to the
}proper logs i.e. daemon again.
}I just looked into this a little more. It seems that the /var/run
}file for syslog has changed. /etc/cron.weekly/sysklogd tries to
}do this.
}
}kill -1 `cat /var/run/syslog.pid`
}
}but the file in /var/run is now this
}
}-rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
I have problems to follow you. In my version 1.2-11 the
/etc/cron.weekly/sysklogd file calls:
--------------------------------------------------
# Restart syslogd.
kill -1 `cat /var/run/syslogd.pid`
--------------------------------------------------
So this is the correct file.
Regards,
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ +49-441-777884 * Login&Passwd: nuucp * Index: ~/ls-lR.gz /
/ Whenever you meet yourself you're in a time loop /
/http://home.pages.de/~joey/ or in front of a mirror /
----------------------------------------------------------------
16.10.95: Oldenburger Usenet(ter) Treffen, ab 20h im Dreieck
Acknowledgement sent to joey@finlandia.Infodrom.North.DE (Martin Schulze)
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From olis.north.de!indrom!joey Sat Oct 7 09:44:53 1995
Return-Path: <indrom!joey@olis.north.de>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t1cMi-000HwhC; Sat, 7 Oct 95 09:44 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA29084
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 7 Oct 1995 08:36:51 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
id <m0t1aHB-0000BuC>; Sat, 7 Oct 95 15:30 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
id <m0t1aCv-0001nCC@olis.north.de>; Sat, 7 Oct 95 15:26 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
by finlandia.Infodrom.North.DE from joey (Martin Schulze)
id m0t1YMt-000K0vC; Sat, 7 Oct 95 13:28 MET
Message-Id: <m0t1YMt-000K0vC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
To: andrew@kryten.it.com.au, debian-bugs@pixar.com
Date: Sat, 7 Oct 1995 13:28:43 +0100 (MET)
In-Reply-To: <m0szyTf-000AZYC@kryten.it.com.au> from "Andrew Howell" at Oct 3, 95 11:57:10 am
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1470
Hallo Andrew Howell!
}Package: syslogd
}Version: 1.2-11
}
}As you can see below the syslogd is still writing to daemon.0 after
}savelog ran on Oct 1st.
}
}-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
}-rw-r--r-- 1 root adm 207110 Oct 3 11:52 /var/log/daemon.0
}
}root 97 0.0 0.8 73 132 ? S Sep 28 1:01 /sbin/syslogd
}
}After I kill -HUPed the syslogd process it started writing to the
}proper logs i.e. daemon again.
}I just looked into this a little more. It seems that the /var/run
}file for syslog has changed. /etc/cron.weekly/sysklogd tries to
}do this.
}
}kill -1 `cat /var/run/syslog.pid`
}
}but the file in /var/run is now this
}
}-rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
I have problems to follow you. In my version 1.2-11 the
/etc/cron.weekly/sysklogd file calls:
--------------------------------------------------
# Restart syslogd.
kill -1 `cat /var/run/syslogd.pid`
--------------------------------------------------
So this is the correct file.
Regards,
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ +49-441-777884 * Login&Passwd: nuucp * Index: ~/ls-lR.gz /
/ Whenever you meet yourself you're in a time loop /
/http://home.pages.de/~joey/ or in front of a mirror /
----------------------------------------------------------------
16.10.95: Oldenburger Usenet(ter) Treffen, ab 20h im Dreieck
Acknowledgement sent to joey@finlandia.Infodrom.North.DE (Martin Schulze)
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From cus.cam.ac.uk!iwj10 Tue Oct 3 05:19:22 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t06Je-000H1wC; Tue, 3 Oct 95 05:19 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA17947
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 3 Oct 1995 05:19:02 -0700
Received: by bootes.cus.cam.ac.uk
(Smail-3.1.29.0 #36) id m0t06JX-000C0KC; Tue, 3 Oct 95 13:19 BST
Received: by chiark
id <m0t061z-0002ZJZ@chiark.al.cl.cam.ac.uk>
(Debian /\oo/\ Smail3.1.29.1 #29.33); Tue, 3 Oct 95 13:01 BST
Message-Id: <m0t061z-0002ZJZ@chiark.al.cl.cam.ac.uk>
Date: Tue, 3 Oct 95 13:01 BST
From: Ian Jackson <iwj10@cus.cam.ac.uk>
To: debian-bugs@pixar.com
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
Andrew Howell writes ("Bug#1531: syslogd continues to write to old file after savelog"):
> I just looked into this a little more. It seems that the /var/run
> file for syslog has changed. /etc/cron.weekly/sysklogd tries to
> do this.
>
> kill -1 `cat /var/run/syslog.pid`
>
> but the file in /var/run is now this
>
> -rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
How about using something like
start-stop-daemon --stop --signal 1 --user root --exec /sbin/syslogd
?
Ian.
Acknowledgement sent to Ian Jackson <iwj10@cus.cam.ac.uk>
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From kryten.it.com.au!andrew Mon Oct 2 21:23:00 1995
Return-Path: <andrew@kryten.it.com.au>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0szyse-000BsQC; Mon, 2 Oct 95 21:23 PDT
Received: from kryten.it.com.au by pixar.com with SMTP id AA29520
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 2 Oct 1995 21:22:36 -0700
Received: by kryten.it.com.au
id <m0szysI-000AZXC@kryten.it.com.au>
(Debian /\oo/\ Smail3.1.29.1 #29.33); Tue, 3 Oct 95 12:22 WST
Message-Id: <m0szysI-000AZXC@kryten.it.com.au>
From: andrew@kryten.it.com.au (Andrew Howell)
Subject: Re: Bug#1531: syslogd continues to write to old file after savelog
To: debian-bugs@pixar.com
Date: Tue, 3 Oct 1995 12:22:38 +0800 (WST)
X-Mailer: ELM [version 2.4 PL24 PGP2]
Content-Type: text
Content-Length: 720
I just looked into this a little more. It seems that the /var/run
file for syslog has changed. /etc/cron.weekly/sysklogd tries to
do this.
kill -1 `cat /var/run/syslog.pid`
but the file in /var/run is now this
-rw-r--r-- 1 root root 3 Sep 28 13:53 syslogd.pid
Andrew
-----------------------------------------------------------------------
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%. Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
-- Kryten in Red Dwarf `The Last Day'
Andrew Howell andrew@it.com.au
Perth, Western Australia howellaa@cs.curtin.edu.au
Acknowledgement sent to andrew@kryten.it.com.au (Andrew Howell)
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Message received at debian-bugs:
From kryten.it.com.au!andrew Mon Oct 2 20:57:27 1995
Return-Path: <andrew@kryten.it.com.au>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0szyTu-000Dv9C; Mon, 2 Oct 95 20:57 PDT
Received: from kryten.it.com.au by pixar.com with SMTP id AA27734
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 2 Oct 1995 20:57:03 -0700
Received: by kryten.it.com.au
id <m0szyTf-000AZYC@kryten.it.com.au>
(Debian /\oo/\ Smail3.1.29.1 #29.33); Tue, 3 Oct 95 11:57 WST
Message-Id: <m0szyTf-000AZYC@kryten.it.com.au>
From: andrew@kryten.it.com.au (Andrew Howell)
Subject: syslogd continues to write to old file after savelog
To: debian-bugs@pixar.com
Date: Tue, 3 Oct 1995 11:57:10 +0800 (WST)
X-Mailer: ELM [version 2.4 PL24 PGP2]
Content-Type: text
Content-Length: 881
Package: syslogd
Version: 1.2-11
As you can see below the syslogd is still writing to daemon.0 after
savelog ran on Oct 1st.
-rw-r--r-- 1 root adm 0 Oct 1 06:47 /var/log/daemon
-rw-r--r-- 1 root adm 207110 Oct 3 11:52 /var/log/daemon.0
root 97 0.0 0.8 73 132 ? S Sep 28 1:01 /sbin/syslogd
After I kill -HUPed the syslogd process it started writing to the
proper logs i.e. daemon again.
Andrew
-----------------------------------------------------------------------
Dehydration - 34%, Recollection of previous evening - 2%, embarrassment
factor - 91%. Advise repair schedule:- off line for 36 hours, re-boot
startup disk, and replace head - wow, what a night!
-- Kryten in Red Dwarf `The Last Day'
Andrew Howell andrew@it.com.au
Perth, Western Australia howellaa@cs.curtin.edu.au
Acknowledgement sent to andrew@kryten.it.com.au (Andrew Howell)
:
New bug report received and forwarded.
Full text available.
Report forwarded to debian-devel@pixar.com
:
Bug#1531
; Package syslogd
.
Full text available.
Ian Jackson /
iwj10@thor.cam.ac.uk,
with the debian-bugs tracking mechanism