Re: RE: [gentoo-user] kmail delete problem

Re: RE: [gentoo-user] kmail delete problem

[Michael Kintzios]

[-- Attachment #1: Type: text/plain, Size: 2525 bytes --]

> From:: "Michael Kintzios" <michaelkintzios@lycos.co.uk>
> To: <gentoo-user@lists.gentoo.org>
> Subject: RE: [gentoo-user] kmail delete problem
> Date: Thu, 2 Feb 2006 11:24:50 -0000

> > -----Original Message-----
> > From: Paul [mailto:gentoo@appjaws.plus.com] 
> > Sent: 02 February 2006 10:04
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] kmail delete problem
> > 
> > 
> > On Wednesday 01 Feb 2006 16:29, Michael Kintzios wrote:
> > > > -----Original Message-----
> > > > From: Paul [mailto:gentoo@appjaws.plus.com]
> > 
> > > > I raised the original mouse problem which I thought was
> > > > resolved by changing
> > > > the mouse protocal to "ExplorerPS/2". Although the mouse
> > > > works OK It still
> > > > appears to be SOMETIMES double clicking.
> > > > I have noticed that on boot I get an error "module mousedev
> > > > not found" and
> > > > something else but I don't appear to have a boot log!!!
> > >
> > > For besides the hardware related messages in dmesg and xorg.0.log
> > > messages you can also check the last boot cycle in /var/log/syslog.
> > 
> > Mick
> > I don't have a directory /var/log/syslog. I have been looking 
> > for a boot log, 
> > I suppose I need to turn it on somehow.
> > Do you know how?
> > Thanks
> 
> I'll try to look into it tonight (away from my PC now) and get back to
> you.

Sorry, it's taken me some time to look into this (working all hours at the moment!)

Check if your /etc/syslog-ng/syslog-ng.conf has a destination/filter like this:
=============================================
#This is the source of the messages to be logged.
source src { unix-stream("/dev/log"); internal(); pipe("/proc/kmsg"); };
source kernsrc { pipe("/proc/kmsg"); };

#This is the destination where we want to capture some of the messages.
destination syslog { file("/var/log/syslog"); };

#This the relevant filter.
filter f_syslog { not facility(authpriv, mail); };

#This connects them together.
log { source(src); filter(f_syslog); destination(syslog); };
=============================================

To rotate the logs I have set this up in my /etc/logrotate.conf:
=============================================
# when /var/log/syslog gets big 
/var/log/syslog
{   
    rotate 1
    weekly
    size=1M
}
=============================================

Not sure if the above is syntatictally perfect, or a bit crude, but it works on two of my boxen without apparent problems.  Someone with scripting skills may want to comment on improving it?
-- 
Regards,
Mick