hanche@imf.unit.no (Harald Hanche-Olsen) (05/02/90)
Oooohhh, I've got egg on my face... Like John Thompson says, This is a GUESS only. I couldn't find reference in the help files either supporting or debunking it, and we don't run syslogd here. Might the separation between the priority-specifiers and the output file need to be a TAB? I know this occurs elsewhere in Unix-ey things, and a TAB is not the easiest character to generate on Aegis keyboards.... Yup, someone (or someTHING?) had replaced all tabs with spaces in the config file. I am sure I wrote it with tabs in the beginning... Now, let's all shout it out loud together... WE WANT MEANINGFUL ERROR MESSAGES!!! Thank you. - Harald Hanche-Olsen <hanche@imf.unit.no> Division of Mathematical Sciences The Norwegian Institute of Technology N-7034 Trondheim NORWAY
jos@ele.tue.nl (Jos van Eijndhoven) (05/03/90)
We have syslogd running on a set of DN3000s and DN2500s running 10.2, and everything works fine. We had no startup problems of any kind. Our configuration file is (on most apollos): *.err;daemon,auth.notice;mail.crit /usr/adm/messages lpr.info @ap18 mail.debug @ap1 *.emerg * The separators are indeed TABs. Jos van Eijndhoven Eindhoven Univ of Technology, The Netherlands jos@es.ele.tue.nl