editing syslog to stop a particular daemon logging

[hcclnoodles]

Hi there

I get the following message im my messages file 2 or 3 times a second

Dec 4 11:44:18 my-box in.timed[29691]: [ID 927837 daemon.info] connect from localhost

I would like to stop in.timed from logging to syslog altogether as this message is filling up my disk.

I dont want to stop daemon.info altogether because we need it ....but i would like to configure syslog.conf somehow so that in.timed doesnt log at all

any help on this would be greatly appreciated

 

[Annihilannic]

Unfortunately syslog isn't that flexible.

I'd be more inclined to investigate the cause of the messages in the first place, and disable in.timed if it's not required?

What version of the OS?

Annihilannic.

 

[hcclnoodles]

Thankyou for your response.Im running Solaris 10 on Sunfire x4100 ....The in.timed packets are required by our application (it uses it to sync with its backup box) So unfortunately i cant stop them ....

Weve only just moved to the Solaris 10 x86 platform (it wasnt happening on our old Sparc solaris 8 platform). It would unfortunately be too much of a major thing to rewrite our application to resolve this ...so i have to come up with a solution

 

[Annihilannic]

You could certainly configure it to send the daemon.info output to another log file, that way at least it wouldn't be cluttering up your messages file.

Annihilannic.

 

[KenCunningham]

...and then do a regular cull of that log file, so that the space is released.

I don't mind people who aren't what they seem. I just wish they'd make their mind up.

 

[Annihilannic]

You must have customised the logging already? On my Solaris 10 box (where I haven't touched syslog.conf) daemon.info is not configured to go to /var/adm/message. Only daemon.notice and higher go there?

[tt]*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages
[/tt]

Annihilannic.