Re: Logrotate

2011-01-23 Thread Matthew Seaman
On 23/01/2011 14:10, Grant Peel wrote:
> Is there a way or method to ignore the symlinks (or a workaround) that
> anyone knows of, other than making a logrotate.conf container for each
> individal directory.

Use something other than logrotate?

Three possibilities:

   * rotatelogs

  This is a utility that comes with Apache.  To use it, you need to
  modify your apache config to change the logging directives.
  Instead of (eg.)

  CustomLog "/var/log/httpd-access.log" common

  You'ld use:

  CustomLog "|/usr/local/sbin/rotatelogs \
 /var/log/httpd-access.log 86400" common

  which will generate a new log file every day at midnight,
  labelled by the date as the standard seconds-since-the-epoch
  unit time.  (Other time formats can be applied)

   * cronolog -- in ports as sysutils/cronolog

  This is rotatelogs on steroids -- it lets you use strftime(3)
  format codes to build the path and/or filename the logfile is
  saved as, so you could have a scheme giving paths like:

  /var/logs/apache22/2011/01/23/virtual-host-name/access_log

   [One advantage of rotatelogs or cronolog for busy sites -- you
   get log file rotation without any requirement to restart apache
   at all.  One disadvantage: neither of these programs *delete*
   over-aged log files.  You'll need to write a very small cron job to
   do that bit.]

   * newsyslog -- part of the base system.

 You can use wildcards to match a range of different file names.
 If you rotate the logs based on age or size, it /should/ only do
 one cycle per invocation.  (Not tested -- so may be completely
 bogus).  Something like:


 /home/*/logs/access_log  644 14 * 24 GJ /var/run/httpd.pid 30

 added to /etc/newsyslog.conf should get you log files rotated once
 every 24h with two weeks worth kept on hand.

Otherwise, you could rearrange your directory structure to give you a
unique path distinguishable by globbing.  So, instead of having:

 /home/domain1.com as the real directory

 and sym-linking

 domain1.net -> domain1.com
 domain1.org -> domain1.com

Make the directory be:

 /home/_domain1/

and create symlinks:

 domain1.com -> _domain1
 domain1.net -> _domain1
 domain1.org -> _domain1

Then you can wildcard as '/home/_*/logs/access_log' [Note '_' was chosen
because that character is specifically disallowed in host / domain
names: it's guaranteed not to accidentally collide]

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature


Logrotate

2011-01-23 Thread Grant Peel

Hi all,

Not sure if there is a better list to ask this, so here goes.

I use logrotate to rotate the apache log files within each domains log 
directory. They are in the home directory as such:


/home/domain1.com/logs/access_log
/home/domain2.com/logs/access_log
/home/domain3.com/logs/access_log
...

In the home directory, I also have symlinks that point to specific domain 
directories, example


cd /home

domain1.ca -> domain1.com
domain1.net -> domain1.com
domain1.org -> domain1.com
someothername.com -> domain1.com
...

All this have beein said, when I use logrotate, it rotates the logs within 
the directories that have sym links pointing to them over and over again. In 
the case of domain1.com, the log would be rotated 5 times.


I am using a logrotate.conf container that looks like so:

# more logrotate.conf
...
/home/*/logs/access_log {
   missingok
   rotate 14
   daily
   create 644 root
   }
...

So, obviously because I am using a wildcard within the container logrotate 
is going through the symlinks and rotating the logs over and over.


Is there a way or method to ignore the symlinks (or a workaround) that 
anyone knows of, other than making a logrotate.conf container for each 
individal directory.


Thanks all,

-Grant 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Logrotate

2008-10-02 Thread Frank Shute
On Wed, Oct 01, 2008 at 07:52:48PM -0400, Grant Peel wrote:
>
> Hi all,
> 
> I have recently started using logrotate to rotate all the logs in the users 
> home directories. These are all apache logs files.
> 
> /home/domain.com/logsaccess_log
> /home/domain.com/logsaccess_log.0.gz
> /home/domain.com/logsaccess_log.1.gz
> /home/domain.com/logsaccess_log.2.gz
> 
> I have a problem though. Some of my domains have softlinks pointing to 
> them, this causes the logs to be rotated 2 or more times (i.e. 1 time for 
> the 'real' directory, and 1 time each for each softlink pointing to them).
> 
> Example
> 
> /home/domain.com/logs/
> domain2.com -> domain.com
> domain3.com -> domain.com
> 
> will result in the 'access_log' being rotated 3 times in one run, causing 
> my log dirs to look like this:
> 
> -rw-r--r--   1 root  holt   160 Oct  1 05:44 access_log
> -rw-r--r--   1 root  holt   446 Oct  1 05:44 error_log
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.1.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.2.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.3.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.4.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.5.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.6.gz
> -rw-r--r--   1 root  holt   224 Oct  1 03:46 access_log.7.gz
> -rw-r--r--   1 root  holt20 Sep 30 03:46 access_log.8.gz
> -rw-r--r--   1 root  holt20 Sep 30 03:46 access_log.9.gz
> 
> Here is this appropriate part of my logrotate.conf
> 
> # logrotate.conf
> 
> compress
> 
> ...
> 
> /home/*/logs/access_log {
>missingok
>rotate 14
>daily
>create 644 root
>sharedscripts
>postrotate
>/usr/local/sbin/apachectl restart
>endscript
>}
> 
> # End of logrotate.conf
> 
> 
> Question, is there a way to stop this from happening?
> 
> -Grant
> 

Aswell as doing what Jeremy Chadwick mentioned, you might want to use
newsyslog(8) to rotate your logs.

It's got a couple of advantages that I know of: it's part of the base
system and it gracefully sends Apache a signal (SIGUSR1) to stop it
writing to the logfile before it rotates it.

You want something like the following in newsyslog.conf(5):

/var/log/httpd-access.log   644  5   200  * B/var/run/httpd.pid  30

Obviously, adjust the parameters to suit your needs. You want the 30
at the end. All explained in the manpage.

Regards,

-- 

 Frank 


 Contact info: http://www.shute.org.uk/misc/contact.html 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Logrotate

2008-10-01 Thread Jeremy Chadwick
On Wed, Oct 01, 2008 at 07:52:48PM -0400, Grant Peel wrote:
> I have recently started using logrotate to rotate all the logs in the 
> users home directories. These are all apache logs files.
>
> /home/domain.com/logsaccess_log
> /home/domain.com/logsaccess_log.0.gz
> /home/domain.com/logsaccess_log.1.gz
> /home/domain.com/logsaccess_log.2.gz
>
> I have a problem though. Some of my domains have softlinks pointing to 
> them, this causes the logs to be rotated 2 or more times (i.e. 1 time for 
> the 'real' directory, and 1 time each for each softlink pointing to 
> them).
>
> Example
>
> /home/domain.com/logs/
> domain2.com -> domain.com
> domain3.com -> domain.com
>
> will result in the 'access_log' being rotated 3 times in one run, causing 
> my log dirs to look like this:
>
> -rw-r--r--   1 root  holt   160 Oct  1 05:44 access_log
> -rw-r--r--   1 root  holt   446 Oct  1 05:44 error_log
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.1.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.2.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.3.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.4.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.5.gz
> -rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.6.gz
> -rw-r--r--   1 root  holt   224 Oct  1 03:46 access_log.7.gz
> -rw-r--r--   1 root  holt20 Sep 30 03:46 access_log.8.gz
> -rw-r--r--   1 root  holt20 Sep 30 03:46 access_log.9.gz
>
> Here is this appropriate part of my logrotate.conf
>
> # logrotate.conf
>
> compress
>
> ...
>
> /home/*/logs/access_log {
>missingok
>rotate 14
>daily
>create 644 root
>sharedscripts
>postrotate
>/usr/local/sbin/apachectl restart
>endscript
>}
>
> # End of logrotate.conf
>
>
> Question, is there a way to stop this from happening?

The problem is that you're using a wildcard in your log list:

/home/*/logs/access_log is going to expand to:

/home/domain.com/logs/access_log
/home/domain2.com/logs/access_log
/home/domain3.com/logs/access_log
/home/...anythingelse.../logs/access_log

So the software will do exactly what you asked for.

What we use on our production webservers:

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" 
combined
CustomLog "/var/log/httpd-access.log" combined

This puts the VirtualHost name being accessed as the first field
in the logfile.  Every night, via a cronjob, we split the file
up per VirtualHost using a script that comes with Apache called
split-logfile.  E.g.:

cd where_you_want_the_logs
/usr/local/sbin/split-logfile < /var/log/httpd-access.log

This will make a separate logfile per virtual host name, and you
can do whatever you want from there on out.

There's a performance advantage here as well: one logfile means only
one file descriptor open, which is Good(tm).  Multiple logfiles opened
under Apache does not scale well.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Logrotate

2008-10-01 Thread Sebastian Tymków
Hi,

I'm not sure but I think you can try use "sharedscripts" in yor logrotete
script.
Another solution is make script which unlink/link logs.

Best regards,

Shamrock
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Logrotate

2008-10-01 Thread Grant Peel

Hi all,

I have recently started using logrotate to rotate all the logs in the users 
home directories. These are all apache logs files.


/home/domain.com/logsaccess_log
/home/domain.com/logsaccess_log.0.gz
/home/domain.com/logsaccess_log.1.gz
/home/domain.com/logsaccess_log.2.gz

I have a problem though. Some of my domains have softlinks pointing to them, 
this causes the logs to be rotated 2 or more times (i.e. 1 time for the 
'real' directory, and 1 time each for each softlink pointing to them).


Example

/home/domain.com/logs/
domain2.com -> domain.com
domain3.com -> domain.com

will result in the 'access_log' being rotated 3 times in one run, causing my 
log dirs to look like this:


-rw-r--r--   1 root  holt   160 Oct  1 05:44 access_log
-rw-r--r--   1 root  holt   446 Oct  1 05:44 error_log
-rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.1.gz
-rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.2.gz
-rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.3.gz
-rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.4.gz
-rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.5.gz
-rw-r--r--   1 root  holt20 Oct  1 03:46 access_log.6.gz
-rw-r--r--   1 root  holt   224 Oct  1 03:46 access_log.7.gz
-rw-r--r--   1 root  holt20 Sep 30 03:46 access_log.8.gz
-rw-r--r--   1 root  holt20 Sep 30 03:46 access_log.9.gz

Here is this appropriate part of my logrotate.conf

# logrotate.conf

compress

...

/home/*/logs/access_log {
   missingok
   rotate 14
   daily
   create 644 root
   sharedscripts
   postrotate
   /usr/local/sbin/apachectl restart
   endscript
   }

# End of logrotate.conf


Question, is there a way to stop this from happening?

-Grant


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: logrotate question

2008-08-20 Thread John Almberg


On Aug 20, 2008, at 8:48 AM, Rudi Kramer - MWEB wrote:




Zbigniew Szalbot
Sent: Wednesday, August 20, 2008 2:14 PM
To: User Questions
Subject: logrotate question

Dear all,

I am trying to use logrotate from ports and I am getting the  
following

error. Can anyone offer any insight?


Hi Zbigniew,

I started investigating logrotate but someone put me on to newsyslog
instead.
Newsyslog is part of the FreeBSD and amazing simple to setup:

1) vi /etc/newsyslog.conf

2) Add the following line:

/var/log/httpd/*.log www:www 644  60*   @T00BJG
/var/run/httpd.pid

I would recommend reading man pages newsyslog newsyslog.conf for more
info.



I use newsyslog for other log files, but when I decided I needed to  
rotate apache logs, recently (see "rotatelogs rotates logs too  
quickly" thread), I read the following in "Absolute FreeBSD, 2nd  
edition"


"If you simply use newsyslog to rotate your [Apache] logs as you do  
for other programs, Apache will corrupt its own logs. Apache supports  
logging to programs, however. I recommend handling your logs via  
rotatelogs(8), included with Apache."


It took me a whole day to switch over to rotatelogs and then  
investigate some odd behavior, but its working great now.


-- John

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: logrotate question

2008-08-20 Thread Zbigniew Szalbot

Rudi Kramer - MWEB pisze:

Zbigniew Szalbot
Sent: Wednesday, August 20, 2008 2:14 PM
To: User Questions
Subject: logrotate question

Dear all,

I am trying to use logrotate from ports and I am getting the following
error. Can anyone offer any insight?


Hi Zbigniew,

I started investigating logrotate but someone put me on to newsyslog
instead. 
Newsyslog is part of the FreeBSD and amazing simple to setup:


1) vi /etc/newsyslog.conf

2) Add the following line:

/var/log/httpd/*.log www:www 644  60*   @T00BJG
/var/run/httpd.pid

I would recommend reading man pages newsyslog newsyslog.conf for more
info.

Rudi
Thanks for your post! Well, I really like newsyslog but I miss some 
features in it.


1/ rotating based on time and size
2/ saving files with timestapms in their names
3/ moving rotated messages to another folder

This is why I am trying logrotate.

Thanks!

Zbigniew Szalbot
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


RE: logrotate question

2008-08-20 Thread Rudi Kramer - MWEB

> Zbigniew Szalbot
> Sent: Wednesday, August 20, 2008 2:14 PM
> To: User Questions
> Subject: logrotate question
> 
> Dear all,
> 
> I am trying to use logrotate from ports and I am getting the following
> error. Can anyone offer any insight?

Hi Zbigniew,

I started investigating logrotate but someone put me on to newsyslog
instead. 
Newsyslog is part of the FreeBSD and amazing simple to setup:

1) vi /etc/newsyslog.conf

2) Add the following line:

/var/log/httpd/*.log www:www 644  60*   @T00BJG
/var/run/httpd.pid

I would recommend reading man pages newsyslog newsyslog.conf for more
info.

Rudi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: logrotate question

2008-08-20 Thread Zbigniew Szalbot

Sorry for this monologue...

Zbigniew Szalbot:

Answering myself...

Zbigniew Szalbot:

Dear all,

I am trying to use logrotate from ports and I am getting the following 
error. Can anyone offer any insight?


/usr/local/sbin/logrotate -d /usr/local/etc/logrotate.conf
reading config file /usr/local/etc/logrotate.conf
reading config info for /var/log/httpd-error.log
error: /usr/local/etc/logrotate.conf:11 bad olddir path "/var/log/tmp/"
error: found error in /var/log/httpd-error.log  , skipping
error: /usr/local/etc/logrotate.conf:11 } expected
removing last 1 log configs


http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2008-August/147600.html 


So it seems there is a bug and it has not yet been solved?
I upgraded (!) logrotate and all is fine. I installed it a few days ago 
and thought I had the latest version. Shame on me!


$ /usr/local/sbin/logrotate -d /usr/local/etc/logrotate.conf
reading config file /usr/local/etc/logrotate.conf
reading config info for /var/log/httpd-error.log
olddir is now tmp/

Handling 1 logs

rotating pattern: /var/log/httpd-error.log   71680 bytes (5 rotations)
olddir is tmp/, empty log files are rotated, old logs are removed
considering log /var/log/httpd-error.log
  log needs rotating
rotating log /var/log/httpd-error.log, log->rotateCount is 5
dateext suffix '-20080820'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
glob finding logs to compress failed
glob finding old rotated logs failed
renaming /var/log/httpd-error.log to /var/log/tmp//httpd-error.log-20080820
creating new /var/log/httpd-error.log mode = 0644 uid = 0 gid = 0
running postrotate script
running script with arg /var/log/httpd-error.log: "
/sbin/killall -HUP httpd


--
Zbigniew Szalbot
www.LCWords.com


smime.p7s
Description: S/MIME Cryptographic Signature


Re: logrotate question

2008-08-20 Thread Zbigniew Szalbot

Answering myself...

Zbigniew Szalbot:

Dear all,

I am trying to use logrotate from ports and I am getting the following 
error. Can anyone offer any insight?


/usr/local/sbin/logrotate -d /usr/local/etc/logrotate.conf
reading config file /usr/local/etc/logrotate.conf
reading config info for /var/log/httpd-error.log
error: /usr/local/etc/logrotate.conf:11 bad olddir path "/var/log/tmp/"
error: found error in /var/log/httpd-error.log  , skipping
error: /usr/local/etc/logrotate.conf:11 } expected
removing last 1 log configs


http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2008-August/147600.html
So it seems there is a bug and it has not yet been solved?



The (simple) content of logrotate.conf is below:

# rotate apache logs
"/var/log/httpd-error.log"  {
rotate 5
monthly
compress
delaycompress
create
size=70k
missingok
sharedscripts
olddir="/var/log/tmp/"
postrotate
/sbin/killall -HUP httpd
endscript
}

I tried olddir argument with and without =, with and without "", with 
and without a trailing slash and still getting this error.


I am also not sure why it would expect } in line 11?

I have read the man but it does not answer my questions or at least I do 
not see the answers.


Many thanks for your advice!



--
Zbigniew Szalbot
www.LCWords.com


smime.p7s
Description: S/MIME Cryptographic Signature


logrotate question

2008-08-20 Thread Zbigniew Szalbot

Dear all,

I am trying to use logrotate from ports and I am getting the following 
error. Can anyone offer any insight?


/usr/local/sbin/logrotate -d /usr/local/etc/logrotate.conf
reading config file /usr/local/etc/logrotate.conf
reading config info for /var/log/httpd-error.log
error: /usr/local/etc/logrotate.conf:11 bad olddir path "/var/log/tmp/"
error: found error in /var/log/httpd-error.log  , skipping
error: /usr/local/etc/logrotate.conf:11 } expected
removing last 1 log configs

The (simple) content of logrotate.conf is below:

# rotate apache logs
"/var/log/httpd-error.log"  {
rotate 5
monthly
compress
delaycompress
create
size=70k
missingok
sharedscripts
olddir="/var/log/tmp/"
postrotate
/sbin/killall -HUP httpd
endscript
}

I tried olddir argument with and without =, with and without "", with 
and without a trailing slash and still getting this error.


I am also not sure why it would expect } in line 11?

I have read the man but it does not answer my questions or at least I do 
not see the answers.


Many thanks for your advice!

--
Zbigniew Szalbot
www.LCWords.com


smime.p7s
Description: S/MIME Cryptographic Signature


Re: libintl.so.5 issue when installing logrotate

2005-01-11 Thread Kris Kennaway
On Tue, Jan 11, 2005 at 11:53:52AM +0100, Olaf Greve wrote:
> Hi,
> 
> I ran into a rather funny issue (fbsd 5.3-release, i386).
> 
> I have an updated ports tree (that is: twice per week cron updates it 
> using cvsup).
> 
> Now, I tried installing /usr/ports/sysutils/logrotate (make install)
> 
> O.k., it failed, mentioning that it required gettext version 0.13 or higher.
> 
> No problem, just install that, right?
> O.k., so I installed /usr/ports/devel/gettext (make deinstall, make 
> reinstall)
> 
> All fine so far (it installef version 0.14.1).
> 
> Then I tried again to make install the /usr/ports/sysutils/logrotate
> and again it failed, this time the error is:
> [...]
> ===>  Building for logrotate-3.7_3
> /libexec/ld-elf.so.1: Shared object "libintl.so.5" not found
> 
> Hmmm, no what can that be?
> A quick look-up on Google shows: 
> http://tomster.org/geek/freebsdcookbook/tidbits/gettextupgrade
> 
> Nice, a "chicken and the egg" problem: logrotate requires gettext 0.13 
> or higher, but when installing that, apparently out goes a required 
> library! Duh!

It's probably some other binary that is missing libintl.so.5 (you
probably yanked it out from underneath when doing a previous upgrade -
if you'd used portupgrade, this wouldn't have happened because it
saves copies of the old libraries in case they're still in use).
gmake is a likely candidate; you'd need to rebuild it.  The libchk
port will tell you if any other applications need to be rebuilt.

Kris



pgpyzTTQvjqHt.pgp
Description: PGP signature


libintl.so.5 issue when installing logrotate

2005-01-11 Thread Olaf Greve
Hi,
I ran into a rather funny issue (fbsd 5.3-release, i386).
I have an updated ports tree (that is: twice per week cron updates it 
using cvsup).

Now, I tried installing /usr/ports/sysutils/logrotate (make install)
O.k., it failed, mentioning that it required gettext version 0.13 or higher.
No problem, just install that, right?
O.k., so I installed /usr/ports/devel/gettext (make deinstall, make 
reinstall)

All fine so far (it installef version 0.14.1).
Then I tried again to make install the /usr/ports/sysutils/logrotate
and again it failed, this time the error is:
[...]
===>  Building for logrotate-3.7_3
/libexec/ld-elf.so.1: Shared object "libintl.so.5" not found
Hmmm, no what can that be?
A quick look-up on Google shows: 
http://tomster.org/geek/freebsdcookbook/tidbits/gettextupgrade

Nice, a "chicken and the egg" problem: logrotate requires gettext 0.13 
or higher, but when installing that, apparently out goes a required 
library! Duh!

The same page mentions the following:
"The solution is to force the upgrade of the already currently installed 
version of gettext (by using the -f option) and doing the upgrade 
recursively (by using the -r option)."

I guess this means doing a pkg_add -f -r  as opposed to 
"make install-ing" the port, right?

Now, before doing this (and possibly messing up the installation by 
doing a force install), has anyone already done this, and is this really 
the best solution?

Tnx and cheerz,
Olafo
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: logrotate mail.log

2003-09-19 Thread Jett Tayer

if u have not disabled log rotation of ur maillog from the start u
installed ur box, log rotation of /var/log/maillog shoul rotate for it is
added by default in /etc/newsyslog.conf to rotate regularly

check ur /etc/newsyslog.conf file

\jett



> I installed courier and since then my /var/log/maillog is nog rotated.
> Can someone explain to me how to set this up myself on fbsd-4.8?
>
> --
> dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE
> ++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody)
> + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


logrotate mail.log

2003-09-19 Thread dick hoogendijk
I installed courier and since then my /var/log/maillog is nog rotated.
Can someone explain to me how to set this up myself on fbsd-4.8?

-- 
dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody)
+ Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


logrotate courier

2003-09-19 Thread dick hoogendijk
I installed courier and since then my /var/log/maillog does not get
'rotated'
How do I set this up myself?

-- 
dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody)
+ Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bind query logging stops after a logrotate.

2003-09-08 Thread Charlie Schluting

On Mon, 8 Sep 2003, John Ekins wrote:

> Hello Charlie,
>
> On Mon, 8 Sep 2003 12:04 , Charlie Schluting <[EMAIL PROTECTED]> sent:
> >
> >After a logrotate, it stops logging completely. The permissions are

Yes, I meant after a run of newsyslog.

> You could use the built in log rotation in Bind. Change your log line to, for 
> example:
>
>  file "/var/log/query.log" print-time yes; versions 5 size 10m;


THANKS! That will do nicely.

-Charlie
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bind query logging stops after a logrotate.

2003-09-08 Thread John Ekins
Hello Charlie,

On Mon, 8 Sep 2003 12:04 , Charlie Schluting <[EMAIL PROTECTED]> sent:

>
>FBSD 5.1:
>Using Bind9.2.2, and I have query logging turned on:
>
>logging {
>   channel "querylog" { file "/var/log/query.lo~g"; print-time yes; };
>   category queries { querylog; };
>};
>
>After a logrotate, it stops logging completely. The permissions are
>correct, and all I have to do to make it start logging again is: "rndc
>reload".
>
>Anyone heard of this? Any ideas?

You could use the built in log rotation in Bind. Change your log line to, for example:

 file "/var/log/query.log" print-time yes; versions 5 size 10m;

>TIA,
>
>-Charlie

Cheers,
John.

 Message sent via Global Webmail - http://www.global.net.uk/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bind query logging stops after a logrotate.

2003-09-08 Thread Garance A Drosihn
At 12:04 PM -0700 9/8/03, Charlie Schluting wrote:
FBSD 5.1:
Using Bind9.2.2, and I have query logging turned on:
logging {
   channel "querylog" { file "/var/log/query.lo~g"; print-time yes; };
   category queries { querylog; };
};
After a logrotate, it stops logging completely. The permissions
are correct, and all I have to do to make it start logging again
is: "rndc reload".
Anyone heard of this? Any ideas?
What do you mean by "a logrotate"?  Do you mean a run of the
newsyslog program?  Or are you using some other program?
--
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Bind query logging stops after a logrotate.

2003-09-08 Thread Charlie Schluting

FBSD 5.1:
Using Bind9.2.2, and I have query logging turned on:

logging {
   channel "querylog" { file "/var/log/query.lo~g"; print-time yes; };
   category queries { querylog; };
};

After a logrotate, it stops logging completely. The permissions are
correct, and all I have to do to make it start logging again is: "rndc
reload".

Anyone heard of this? Any ideas?

TIA,

-Charlie
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"