Well, all this suggests to me that there must be some issue with the client
syslog code in the libc, so that if syslog daemon hangs or has some
internal issue that would basically render system mostly unusable. I think
that might be an interesting project for somebody who has some spare time
on hands to take syslogd as of (r317033 - 1) and see what can be done to
improve resilience of the system against such a failure mode.

-Max

On Sun, Apr 16, 2017 at 5:50 PM, Ben Woods <woods...@gmail.com> wrote:

> On 16 April 2017 at 03:24, Larry Rosenman <l...@lerctr.org> wrote:
>
> > Current SVN seems to have fixed it (via sobomax@ syslogd commit).
> >
>
>
> I experienced this issue too, and can confirm that it existing on r316952,
> but is resolve on r317033.
>
> It was extremely strange. The symptoms I was experiencing were:
> - lightdm display manager would fail to start
> - slim display manager would start, but then fail to login to xfce
> - "service hald restart" and "service dbus restart" would fail
> - "pkg upgrade hal" would fail
>
> Regards,
> Ben
>
> --
> From: Benjamin Woods
> woods...@gmail.com
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
>
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to