Date: Sun, 14 Dec 1997 19:26:16 GMT From: rhh@ct.picker.com To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: rhh@ct.picker.com Subject: bin/5296: slattach fails creating pidfile with ioctl(TIOCSCTTY): Operation not permitted Message-ID: <199712141926.TAA16235@stealth.ct.picker.com> Resent-Message-ID: <199712150030.QAA26779@hub.freebsd.org>
index | next in thread | raw e-mail
>Number: 5296
>Category: bin
>Synopsis: slattach fails creating pidfile with ioctl(TIOCSCTTY): Operation not permitted
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Dec 14 16:30:01 PST 1997
>Last-Modified:
>Originator: Randall Hopper
>Organization:
self
>Release: FreeBSD 3.0-971208-SNAP i386
>Environment:
Straight 3.0-971208 installation with stock slattach.
>Description:
If I run my SLIP script (which invokes slattach) from inside an
xterm, it works fine (doesn't log errors in /var/log/messages,
and does correctly create the var/run/slattach.cuaa1.pid pidfile.
However, if I run my SLIP script from my window manager menus
(i.e. not inside a vtty), then slattach logs the following error
in /var/log/messages:
slattach[15882]: ioctl(TIOCSCTTY): Operation not permitted
and does not create a /var/run pidfile.
3.0-current slattach otherwise appears to work; it just doesn't
create the pidfile that I use in other scripts & cron jobs.
>How-To-Repeat:
Here is a clip from my "slip-on" script that shows how I invoke
slattach (error checking removed for simplicity):
#!/bin/sh
...
exec 0< /dev/cuaa1
exec 1> /dev/cuaa1
chat TIMEOUT 2 "" AT OK AT OK
chat "" "$INITSTRING" "OK" "AT$DIALSTRING" ...<request slip cmds>
slattach -h -c -s 57600 /dev/cuaa1 > /dev/null 2>&1 &
>Fix:
Not known.
>Audit-Trail:
>Unformatted:
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712141926.TAA16235>