#1 Problems with OpenBSD 3.3

Unstable_(example)
open
nobody
None
5
2012-09-14
2004-03-09
No

hi,

I have a 2 problems on my OpenBSD 3.3 system:

  • the ps option -o comm= give a error-msg:
    ps: comm: illegal keyword specification

  • unless I use the -syslog option no output are show in
    daemon.log or message.log

At the first time I change the openlog facility to
daemon
because *.err a go to /dev/console, but no output are
in the files too!
Now I insert a setlogsock('unix') before openlog and
all
works very good for me!

cu

Thomas

Discussion

  • Thomas Spitz

    Thomas Spitz - 2004-03-09

    Patchfile for OpenBSD 3.3

     
  • Rocky Bernstein

    Rocky Bernstein - 2009-05-10

    Sorry for the very late delay. In version 1.06 OpenBSD support was added which I think may address one problem you mention.

    As for the other problem, the manual page for Sys::Syslog advises against calling setlogsock . (The first and second rules). However there probably should be an option to set the facility to be something other than 'err'. If this is still of interest I'll consider adding a patch to set that as an option.

     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks