09.11.2018 3:26, Eric Borisch wrote: > What I find interesting is that with the 'wrong' setting, you can log still > in just fine, and run most commands, but 'sudo' alone fails as described > above. (I've had the same experience on Serial-over-IPMI, but 'su' worked > fine so I never dug into it.) > > It's an easy fix, but I'm still (academically) interested in what it is > that sudo is doing that is unique.
It calls syslog() function with parameters that (for default /etc/ttys and /etc/syslog.conf) makes an attempt to write to the console that blocks. You can easily verify this using "ktrace -i sudo ..." and "kdump" after. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
