Changes have been commited to the example syslog.conf in -current
to address this, mainly, stop spewing useless crap to root and the
console.
-Bob
* John Draper <[EMAIL PROTECTED]> [2005-06-20 19:47]:
> Stuart Henderson wrote:
>
> >On 2005/06/18 14:41:10, John Draper wrote:
> >
> >
> >>>Quickest way is probably 'pkill syslogd' (or 'kill `cat
> >>>/var/run/syslogd.pid`'
> >>>if you don't have pkill).
> >>>
> >>>...or just login as a user other than root, and use "sudo" to execute the
> >>>commands...
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>Ok, if I do that, then how do I enable it again?
> >>
> >>
> >
> >Start it running again with the command line as used in rc.conf,
> >often this would be "syslogd -a /var/empty/dev/log".
> >
> >You might want to edit syslog.conf and remove the lines with * or
> >root listed.
> >
> >
> ok
>
> >Might be stating the obvious, but if you're logging in at the console,
> >you have tried using a different screen haven't you? (alt-ctrl-f2 etc).
> >There's a load of logging normally output to /dev/console which is
> >shown on the first console screen.
> >
> >
> no - I'm ssh'ing into it. The box is 400 KM away.
>
> >
> >
> >>I also have a
> >>problem in that my "ps" command don't work.
> >>
> >>
> >
> >Ah, there's a fair chance that pkill would also be incompatible
> >then... You might try extracting a binary from the distribution tgz
> >files from the same or a different OpenBSD version (if it's -stable,
> >possibly one version newer than the reported version number).
> >
> >
> Although I haven't tried it, I suspect since my Userland is out of synch,
> I'm not sure it would even work.
>
> >Hope this helps...
> >
> >
> >
> Yes - thanx
>
> John
>
--
Bob Beck Computing and Network Services
[EMAIL PROTECTED] University of Alberta
True Evil hides its real intentions in its street address.
