Re: syslogd: Syscall 28 (SYS_sendmsg) in 18 October (i386) snapshot

2015-10-18 Thread Doug Hogan
On Sun, Oct 18, 2015 at 03:42:07PM -0400, Sonic wrote: > No clue if my bug is related. Attempting to upgrade -current today and I get: > Oct 18 14:29:39 stargate /bsd: ksh(4880): syscall 131 > Oct 18 14:29:46 stargate /bsd: ksh(30776): syscall 131 > etc. I don't think it's related since it's compl

Re: syslogd: Syscall 28 (SYS_sendmsg) in 18 October (i386) snapshot

2015-10-18 Thread Theo de Raadt
> On Sun, Oct 18, 2015 at 03:42:07PM -0400, Sonic wrote: > > No clue if my bug is related. Attempting to upgrade -current today and I > > get: > > Oct 18 14:29:39 stargate /bsd: ksh(4880): syscall 131 > > Oct 18 14:29:46 stargate /bsd: ksh(30776): syscall 131 > > etc. > > I don't think it's relat

Re: syslogd: Syscall 28 (SYS_sendmsg) in 18 October (i386) snapshot

2015-10-18 Thread Sonic
On Sun, Oct 18, 2015 at 3:22 PM, Scott Vanderbilt wrote: > Another pledge(2) related issue, this time in syslogd. No clue if my bug is related. Attempting to upgrade -current today and I get: Oct 18 14:29:39 stargate /bsd: ksh(4880): syscall 131 Oct 18 14:29:46 stargate /bsd: ksh(30776): syscall

syslogd: Syscall 28 (SYS_sendmsg) in 18 October (i386) snapshot

2015-10-18 Thread Scott Vanderbilt
Another pledge(2) related issue, this time in syslogd. Unfortunately, this occurs on an ancient Soekris box where rebuilding the syslogd executable will be a non-trivial task. Hopefully I am providing enough details to here to allow someone more knowledgeable with the information necessary to