Hi Garance, Hi list,
I spend some time thinking about all this newsyslog stuff and I am
starting to feel that maybe I am making too much noise for minor
problems. After all disk space is very cheap and turning over the logs
is not something that we have to do very often. In many cases we can
At 12:08 PM +0300 7/2/03, Jim Xochellis wrote:
I suspected that some processes are confused because
a *new* log file is created and these processes are
making the assumption that their log file will be always
the same and perhaps they open it once and then work with
the FILE pointer.
If a program
Hi list,
I am using the newsyslog utility to turn over my log files
automatically. I have noticed that some processes have problem to
continue using their log file after newsyslog has turned it over and
need to receive the SINGHUP signal to re-start logging correctly.
However sending SINGHUP
On Wed, Jul 02, 2003 at 12:08:31PM +0300, Jim Xochellis wrote:
I am using the newsyslog utility to turn over my log files
automatically. I have noticed that some processes have problem to
continue using their log file after newsyslog has turned it over and
need to receive the SINGHUP
Hi Matthew, hi list,
On Wednesday, July 2, 2003, at 02:01 PM, Matthew Seaman wrote:
On Wed, Jul 02, 2003 at 12:08:31PM +0300, Jim Xochellis wrote:
I am using the newsyslog utility to turn over my log files
automatically. I have noticed that some processes have problem to
continue using their
On Wed, Jul 02, 2003 at 03:50:15PM +0300, Jim Xochellis wrote:
[ Dealing with processes that keep an open file descriptor on their
log files, and that don't understand the use of SIGHUP to reopen the
file]
1) Many servers (netatalk, samba, apache, etc) are creating many
processes which are
