Date: Sun, 3 May 1998 09:56:32 -0400 From: Randall Hopper <rhh@ct.picker.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/5296 Message-ID: <19980503095632.A4644@ct.picker.com> In-Reply-To: <10642.894177796@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, May 03, 1998 at 08:43:16AM %2B0200 References: <19980502202633.A2574@ct.picker.com> <10642.894177796@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp: |In message <19980502202633.A2574@ct.picker.com>, Randall Hopper writes: |>Poul-Henning Kamp: |> |Synopsis: slattach fails creating pidfile with ioctl(TIOCSCTTY): |> | Operation not permitted |> | |> |State-Changed-From-To: open-closed |> |State-Changed-By: phk |> |State-Changed-When: Thu Apr 30 12:55:02 PDT 1998 |> |State-Changed-Why: |> |bruce spoke. |> |>What does this mean? Was it fixed? What does "Bruce spoke" imply? | |see: | http://www.freebsd.org/cgi/query-pr.cgi?pr=5296 No new info here. Bruce sent me this msg last December. So did someone make the change he suggested (re above URL): | slattach can't do controlling tty stuff properly if the tty is already | open. It should fail completely when the TIOCSCTTY fails, but its | cleanup is incomplete - it removes the pid file but doesn't unattach | slip :-). And if in fact slattach now must assume that it can become the controlling tty for the slip device (and given that this 3.0-current slattach works in an xterm and doesn't work off a window manager menu), it sounds like there's some bug there with it making the "wrong" device the controlling tty (or having some erroneous dependency on slattach already having or not having a controlling tty). Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980503095632.A4644>