Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Apr 1999 11:58:33 -0700 (PDT)
From:      Doug White <dwhite@resnet.uoregon.edu>
To:        "Ronald F. Guilmette" <rfg@monkeys.com>
Cc:        questions@FreeBSD.ORG
Subject:   Re: Two questions about newsyslog(8)
Message-ID:  <Pine.BSF.4.03.9904221156510.7869-100000@resnet.uoregon.edu>
In-Reply-To: <29748.924798861@monkeys.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Apr 1999, Ronald F. Guilmette wrote:

> 
> I have a couple of system log files that would benefit from the magic
> performed by newsyslog(8), however I am concerned about trying to
> employ this program on these specific log files, because the man page
> for newsyslog(8) is not clear about a few important details of what
> this program actually does.  Specifically:
> 
>      #1) When the current log file is being archived, is that current log
>      file (simply renamed and then gzipped), or are its current contents
>      copied first to `logfile.0', followed by truncation to zero length
>      of the existing `logfile' file?
> 
>      (The answer to this question may perhaps make a BIG difference as
>      to whether I can use newsyslog(8) or not on the specific log files
>      I am concerned about.  If it just tries to rename `logfile' to
>      `logfile.0' and if the daemon process that is writing the log file
>      is just holding `logfile' continuously open, then this may perhaps
>      not produce the desited results.)

If the daemon reopens its logfiles with a HUP signal, you can point
newsyslog at a pid file to run through 'kill -HUP `cat /path/to/pidfile`'.

>      #2) The man page for newsyslog(8) says that it will send a signal
>      to the daemon process that is writing the log file.  But when exactly
>      will it do this? 

Just after it moves the log out of the way and touches the new log.

>      What I mean is:  Does newsyslog(8) send the signal
>      to the daemon process just after it makes a copy of (or just after
>      it renames) the current log file?  Is the assumption then that this
>      signal should cause the daemon to close the current logfile and open
>      a new one having the original (pre-archiving) filename?

Yes.  It will touch(1) the new log file since most daemons don't open
logfiles with O_CREAT.

Read the Source, Luke! :-)

Doug White                               
Internet:  dwhite@resnet.uoregon.edu    | FreeBSD: The Power to Serve
http://gladstone.uoregon.edu/~dwhite    | www.freebsd.org



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9904221156510.7869-100000>