Date: Thu, 8 Nov 2018 14:26:43 -0600 From: Eric Borisch <eborisch@gmail.com> To: ian@freebsd.org Cc: jordancaraballo87@gmail.com, freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: sudo not available after configuring ipmi serial over lan Message-ID: <CAMsT2=kM3%2Biegze9CG_qZofTEm2UJ5JCpp07qg0EEyR%2BFPPs%2BA@mail.gmail.com> In-Reply-To: <1541707622.52306.134.camel@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. - Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMsT2=kM3%2Biegze9CG_qZofTEm2UJ5JCpp07qg0EEyR%2BFPPs%2BA>