Date: Fri, 9 Nov 2018 03:56:11 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Eric Borisch <eborisch@gmail.com>, ian@freebsd.org Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, jordancaraballo87@gmail.com Subject: Re: sudo not available after configuring ipmi serial over lan Message-ID: <67eb2aaa-fb93-0cf7-7f05-caf7c0e0c809@grosbein.net> In-Reply-To: <CAMsT2=kM3%2Biegze9CG_qZofTEm2UJ5JCpp07qg0EEyR%2BFPPs%2BA@mail.gmail.com> References: <CABoP_SQSc2wnJqYXg6AUF1C3_SbyDiLYOa2_0u5oRLcOERZOMg@mail.gmail.com> <fdf67645-130d-78fd-c3f7-b0d58c6343e5@grosbein.net> <1541691574.52306.94.camel@freebsd.org> <CABoP_SSm919C7n=ePJeYEn8BuR8TfR0zyaU%2Bbj%2B40F8Qc-JJVg@mail.gmail.com> <1541707622.52306.134.camel@freebsd.org> <CAMsT2=kM3%2Biegze9CG_qZofTEm2UJ5JCpp07qg0EEyR%2BFPPs%2BA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67eb2aaa-fb93-0cf7-7f05-caf7c0e0c809>