From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13024 invoked from network); 16 Jul 1998 14:04:12 -0000 Received: from math.gatech.edu (root@130.207.146.50) by ns1.primenet.com.au with SMTP; 16 Jul 1998 14:04:12 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id JAA17764; Thu, 16 Jul 1998 09:53:44 -0400 (EDT) Resent-Date: Thu, 16 Jul 1998 09:43:30 -0400 (EDT) To: zsh-users@math.gatech.edu Subject: Re: rolling over high-traffic logfiles? Newsgroups: dis.lists.zsh References: <19980715234957.51065@astaroth.nit.gwu.edu> Reply-To: sinclair@dis.strath.ac.uk Date: Thu, 16 Jul 1998 14:45:20 +0100 Message-ID: <15546.900596720@dis.strath.ac.uk> From: Duncan Sinclair Resent-Message-ID: <"ikc1-1.0.RI4.2EWhr"@math> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/1678 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > is there some easy way to roll over high-traffic logfiles >in zsh, without losing any possible incoming data? As it is a syslog log file there is a standard way to do this: mv /var/adm/extlog /var/adm/extlog.`date` cp /dev/null /var/adm/extlog kill -HUP `cat /etc/syslog.pid` syslogd will continue writing to the old log file until the kill signal is sent to it. Nothing is ever lost - as long as syslog is behaving itself! Hope this helps. Duncan Sinclair. >From zsh-workers-request@math.gatech.edu Thu Jul 16 14:07:47 1998 Return-Path: Delivered-To: mason-zsh@primenet.com.au Received: (qmail 13065 invoked from network); 16 Jul 1998 14:07:46 -0000 Received: from math.gatech.edu (root@130.207.146.50) by ns1.primenet.com.au with SMTP; 16 Jul 1998 14:07:46 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id JAA17764; Thu, 16 Jul 1998 09:53:44 -0400 (EDT) Resent-Date: Thu, 16 Jul 1998 09:43:30 -0400 (EDT) To: zsh-users@math.gatech.edu Subject: Re: rolling over high-traffic logfiles? Newsgroups: dis.lists.zsh References: <19980715234957.51065@astaroth.nit.gwu.edu> Reply-To: sinclair@dis.strath.ac.uk Date: Thu, 16 Jul 1998 14:45:20 +0100 Message-ID: <15546.900596720@dis.strath.ac.uk> From: Duncan Sinclair Resent-Message-ID: <"ikc1-1.0.RI4.2EWhr"@math> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/1678 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > is there some easy way to roll over high-traffic logfiles >in zsh, without losing any possible incoming data? As it is a syslog log file there is a standard way to do this: mv /var/adm/extlog /var/adm/extlog.`date` cp /dev/null /var/adm/extlog kill -HUP `cat /etc/syslog.pid` syslogd will continue writing to the old log file until the kill signal is sent to it. Nothing is ever lost - as long as syslog is behaving itself! Hope this helps. Duncan Sinclair. >From zsh-workers-request@math.gatech.edu Thu Jul 16 14:12:59 1998 Return-Path: Delivered-To: mason-zsh@primenet.com.au Received: (qmail 13119 invoked from network); 16 Jul 1998 14:12:58 -0000 Received: from math.gatech.edu (root@130.207.146.50) by ns1.primenet.com.au with SMTP; 16 Jul 1998 14:12:58 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id JAA17764; Thu, 16 Jul 1998 09:53:44 -0400 (EDT) Resent-Date: Thu, 16 Jul 1998 09:43:30 -0400 (EDT) To: zsh-users@math.gatech.edu Subject: Re: rolling over high-traffic logfiles? Newsgroups: dis.lists.zsh References: <19980715234957.51065@astaroth.nit.gwu.edu> Reply-To: sinclair@dis.strath.ac.uk Date: Thu, 16 Jul 1998 14:45:20 +0100 Message-ID: <15546.900596720@dis.strath.ac.uk> From: Duncan Sinclair Resent-Message-ID: <"ikc1-1.0.RI4.2EWhr"@math> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/1678 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > is there some easy way to roll over high-traffic logfiles >in zsh, without losing any possible incoming data? As it is a syslog log file there is a standard way to do this: mv /var/adm/extlog /var/adm/extlog.`date` cp /dev/null /var/adm/extlog kill -HUP `cat /etc/syslog.pid` syslogd will continue writing to the old log file until the kill signal is sent to it. Nothing is ever lost - as long as syslog is behaving itself! Hope this helps. Duncan Sinclair.