aboutsummaryrefslogtreecommitdiff
path: root/sys/netipsec
diff options
context:
space:
mode:
authorKyle Evans <kevans@FreeBSD.org>2019-11-30 20:10:50 +0000
committerKyle Evans <kevans@FreeBSD.org>2019-11-30 20:10:50 +0000
commit1b50b999f9b57eff89002c40559487de9ac43646 (patch)
treee9ccddcce63daa5a58b1d8e07d340f979edce297 /sys/netipsec
parent46413cedf7efc0551beee17a323101632f41ac98 (diff)
downloadsrc-1b50b999f9b57eff89002c40559487de9ac43646.tar.gz
src-1b50b999f9b57eff89002c40559487de9ac43646.zip
tty: implement TIOCNOTTY
Generally, it's preferred that an application fork/setsid if it doesn't want to keep its controlling TTY, but it could be that a debugger is trying to steal it instead -- so it would hook in, drop the controlling TTY, then do some magic to set things up again. In this case, TIOCNOTTY is quite handy and still respected by at least OpenBSD, NetBSD, and Linux as far as I can tell. I've dropped the note about obsoletion, as I intend to support TIOCNOTTY as long as it doesn't impose a major burden. Reviewed by: bcr (manpages), kib Differential Revision: https://reviews.freebsd.org/D22572
Notes
Notes: svn path=/head/; revision=355248
Diffstat (limited to 'sys/netipsec')
0 files changed, 0 insertions, 0 deletions