On Tuesday 17 November 2009 04:35:23 Neil Walker wrote:
Alan McKinnon wrote:
I have to ask - what the blazes are those servers doing??? :-)
HTTP, SMTP and IMAP, mostly. ;)
Which raises another question I have to ask - why are those logging to wtmp?
Do all your users have shell accounts
On Mon, 16 Nov 2009 17:55:51 +0200, Eray Aslan wrote:
On 16.11.2009 14:46, Neil Bothwick wrote:
On Mon, 16 Nov 2009 09:05:18 +0200, Eray Aslan wrote:
- No need to logrotate with time based filenames. Hence, no
need to kill -HUP the syslog daemon. No missed logs.
Then how do
On 17.11.2009 10:59, Neil Bothwick wrote:
Then how do you get the server to use the new logfile names each
day/week?
It creates and uses a new file each hour/day/etc. Perhaps, you missed
the file(...) directive?
I didn't miss it. My question was how to you get the process to USE the
new
On Tuesday 17 November 2009 14:08:00 Eray Aslan wrote:
You wouldn't miss a log messsage by sending a SIGHUP to your mail server,
the logger woulsd keep running.
When syslog-ng cannot process messages for whatever reason, it will
buffer them. When the buffer is full, it will drop the
On Tue, 17 Nov 2009 14:08:00 +0200, Eray Aslan wrote:
I didn't miss it. My question was how to you get the process to USE
the new file. Unless you SIGHUP the process, it will continue using
the config in pace when it started.
Last sentence is correct. What you are missing is that the
On 17.11.2009 17:08, Neil Bothwick wrote:
You wouldn't miss a log messsage by sending a SIGHUP to your mail
server, the logger would keep running.
When syslog-ng cannot process messages for whatever reason, it will
buffer them. When the buffer is full, it will drop the messages. There
is no
On Tue, 17 Nov 2009 17:25:02 +0200, Eray Aslan wrote:
How does sending a SIGHUP to smtpd increase the load on the syslog
server?
Ugh, smtpd? Where did that come from? There was no mention of smtpd in
the thread.
destination mail {
On Tuesday 17 November 2009 18:08:21 Neil Bothwick wrote:
Hectic day at work? :)
I' m not working today, decorating is even more stressful :(
Sign in my local paint store:
Husbands choosing colours must have a note from their wives
I feel your pain. I redid a bathroom sink the other day
On 15.11.2009 13:45, Mick wrote:
On Saturday 14 November 2009 16:53:24 Alex Schuster wrote:
I assume you are using logrotate, and have the /etc/logrotate.d/kernel
file? I guess the 'compytruncate' is misspelled and should be
'copytruncate'. And 'endscript' is used after using 'prerotate' or
Eray Aslan eray.as...@caf.com.tr writes:
- No need to logrotate with time based filenames. Hence, no need to
kill -HUP the syslog daemon. No missed logs.
But you still need some system (eg tmpwatch) to delete old log files
otherwise the disk will (eventually) fill with log files.
On 16.11.2009 10:08, Graham Murray wrote:
Eray Aslan eray.as...@caf.com.tr writes:
- No need to logrotate with time based filenames. Hence, no need to
kill -HUP the syslog daemon. No missed logs.
But you still need some system (eg tmpwatch) to delete old log files
otherwise the disk
On Mon, 16 Nov 2009 09:05:18 +0200, Eray Aslan wrote:
- No need to logrotate with time based filenames. Hence, no need to
kill -HUP the syslog daemon. No missed logs.
Then how do you get the server to use the new logfile names each
day/week? You only need to send a SIGHUP to the server
On 16.11.2009 14:46, Neil Bothwick wrote:
On Mon, 16 Nov 2009 09:05:18 +0200, Eray Aslan wrote:
- No need to logrotate with time based filenames. Hence, no need to
kill -HUP the syslog daemon. No missed logs.
Then how do you get the server to use the new logfile names each
day/week?
Mick writes:
On Saturday 14 November 2009 16:53:24 Alex Schuster wrote:
Something like that, I never used logrotate by myself. See the man
page for more information.
Hmm ... how do you keep your log files under control?
I am using app-admin/metalog (http://metalog.sourceforge.net/) as
Alex Schuster wrote:
SUBJECT: Cron r...@obelix test -x /usr/sbin/run-crons
/usr/sbin/run-crons
error: kernel:9 unknown option 'compytruncate' -- ignoring line
error: kernel:12 unknown option 'endscript' -- ignoring line
--
I assume you are using logrotate, and have the
On Monday 16 November 2009 17:55:51 Eray Aslan wrote:
On 16.11.2009 14:46, Neil Bothwick wrote:
On Mon, 16 Nov 2009 09:05:18 +0200, Eray Aslan wrote:
- No need to logrotate with time based filenames. Hence, no need to
kill -HUP the syslog daemon. No missed logs.
Then how do you
Jarry writes:
Alex Schuster wrote:
Something like that, I never used logrotate by myself. See the man
page for more information.
Let me ask: how do you deal with /var/log/wtmp? I think it does not
go through syslog, and even it it does, it is not easy to process it
whit that
Alex Schuster wrote:
I just let it grow and grow and grow... on my server, which is running
Gentoo for seven years now, it has 27,000 entries, and is at 24 MB.
Wow! Do you even need a server? It can't be doing much. My servers top that
in a few hours. ;)
Be lucky,
Neil
On Monday 16 November 2009 22:09:11 Neil Walker wrote:
Alex Schuster wrote:
I just let it grow and grow and grow... on my server, which is running
Gentoo for seven years now, it has 27,000 entries, and is at 24 MB.
Wow! Do you even need a server? It can't be doing much. My servers top that
Neil Walker writes:
Alex Schuster wrote:
I just let it grow and grow and grow... on my server, which is
running Gentoo for seven years now, it has 27,000 entries, and is at
24 MB.
Wow! Do you even need a server? It can't be doing much. My servers top
that in a few hours. ;)
It's a
Alan McKinnon wrote:
I have to ask - what the blazes are those servers doing??? :-)
HTTP, SMTP and IMAP, mostly. ;)
Be lucky,
Neil
http://www.easy-ebay.com
On Saturday 14 November 2009 16:53:24 Alex Schuster wrote:
Jarry writes:
Hi, I'm getting strange mails from vixie-cron-4.1-r10:
--
SUBJECT: Cron r...@obelix test -x /usr/sbin/run-crons
/usr/sbin/run-crons
error: kernel:9 unknown option 'compytruncate' -- ignoring line
Hi, I'm getting strange mails from vixie-cron-4.1-r10:
--
SUBJECT: Cron r...@obelix test -x /usr/sbin/run-crons
/usr/sbin/run-crons
error: kernel:9 unknown option 'compytruncate' -- ignoring line
error: kernel:12 unknown option 'endscript' -- ignoring line
--
Jarry writes:
Hi, I'm getting strange mails from vixie-cron-4.1-r10:
--
SUBJECT: Cron r...@obelix test -x /usr/sbin/run-crons
/usr/sbin/run-crons
error: kernel:9 unknown option 'compytruncate' -- ignoring line
error: kernel:12 unknown option 'endscript' -- ignoring line
24 matches
Mail list logo
