Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

syslog server

Status
Not open for further replies.

glampshire

Technical User
Aug 22, 2002
3
US
Can someone help with a simple question? I can't get one solaris box to syslog message on a second;

with the syslog.conf entry:
*.debug;kern.debug;daemon.notice;mail.crit /var/adm/messages, @vision10
I get the error;
Feb 21 12:35:42 fdc40 syslogd: /var/adm/messages, @vision10: No such file or directory

If I add parens, as in
*.debug;kern.debug;daemon.notice;mail.crit (/var/adm/messages, @vision10)

I don't get the error message, but neither do the messages show up on the 'vision10' box. Both machines are Solaris8, sparc. I've tried various combinations of commas, tabs, etc and can't seem to find the handle?

--Geff
 
Try this:

*.debug;kern.debug;daemon.notice;mail.crit @vision10

Stop and restart the syslog daemon on the sending server. And make sure your networking is OK and the sending server can see vision10.
 
Hey!! that did it. That's what I wanted. Someday I'll try to figure out how to write to a specific file on the receiving box.

Thanks,

--Geff
 
It seems that syslog.conf isn't flexible enough to do what you want; interstingly, Sun's own System Service Processor software (for E10000s and the like) points messages from the managed domains (systems) to a FIFO/pipe file, and then runs another programme to filter the contents into separate messages files for each domain. Maybe you could do the same? Annihilannic.
 
That's exactly what I have done; with my old friends awk/sed; someday I've got to become productive with Perl!

Thanks,

--Geff
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top