Thank you, Theo. I know this is true. I was tempted to jump right to 5.9 but decided to heed the directions on
http://www.openbsd.org/faq/upgrade56.html " *Note: Upgrades are only supported from one release to the release immediately following it. Do not skip releases. If you got lucky skipping releases in the past, you may not this time."* On Wed, May 25, 2016 at 1:39 PM, Theo de Raadt <dera...@cvs.openbsd.org> wrote: > We only "support" the last release, and we only make errata available > for the last two releases. We don't maintain old code because none of > us run it. > > 5.6 is end-of-life, so you are on your own. > > > So far I haven't been able to get syslog to log anything other than it's > > startup message. > > > > I'm using the stock syslog.conf file. > > > > logger test message does nothing so I ktraced it. > > > > The interesting part is: > > > > 22461 logger RET sigprocmask ~0x10100<SIGKILL|SIGSTOP> > > 22461 logger CALL sendsyslog(0xcfbda6a8,0x27) > > 22461 logger RET sendsyslog -1 errno 57 Socket is not connected > > 22461 logger CALL sigprocmask(SIG_BLOCK,~0<>) > > 22461 logger RET sigprocmask 0<> > > 22461 logger CALL > mprotect(0x39cd6000,0x1000,0x3<PROT_READ|PROT_WRITE>) > > > > So how would I re-connect sendsyslog? > > > > Rebooted a couple of times after upgrading to 5.6--I'll be glad to get > past > > all of these hurdles so I can get up to 5.9! > > > > Thanks, > > > > Jeff Ross
