Date: Thu, 24 Feb 2000 15:37:31 +0000 (GMT) From: <bsd@web3.valley-internet.com> To: andrew@ugh.net.au Cc: freebsd-questions@FreeBSD.ORG Subject: Re: poppassd broken in 3.4 RELEASE ? Message-ID: <Pine.BSF.4.21.0002241534290.94185-100000@web3.valley-internet.com> In-Reply-To: <Pine.BSF.4.21.0002242143230.43014-100000@beebite.ugh.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmmm gets stranger even.. For whatever reason it spawns another process that is used to open up the slave pty, and that process runs as the user who's password is being changed. Ok no problem there all the /dev/ttypxx entries should be mode 666. However I have some program somewhere that is changing the permissions on ttyp3 through ttyp5 to 644, and when that happens the child process can't open it.. Just have to go track down what is changing the permissions like that. Chris On Thu, 24 Feb 2000 andrew@ugh.net.au wrote: > > > On Mon, 21 Feb 2000 bsd@web3.valley-internet.com wrote: > > > poppassd just hangs and logs this: > > > > web3 poppassd[15526]: can't open slave pty: Permission denied > > I'm running 3.3-STABLE about the same age (almost) as 3.4 RELEASE and it > works fine for me. > > The error occurs when poppassd fails to open another tty (which it runs > passwd on). As poppassd is running as root its odd it failed with > permission denied. > > If you change line 349 to read: > > syslog(LOG_ERR, "can't open slave pty (%s): %m", slavedev); > > You will at least find which device it was that it couldn't open. > > Andrew > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0002241534290.94185-100000>