"74457d3d4327f7169df5e5596a955d1862b76270" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"74457 d3d4327f7169df5e5596a955d1862b76270" (Results 1 – 8 of 8) sorted by relevance

/freebsd/usr.sbin/ppp/
H A D	server.h	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.
H A D	radius.c	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.
H A D	prompt.c	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.
H A D	server.c	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.
H A D	bundle.c	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.
H A D	main.c	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.
H A D	ppp.8	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.
H A D	command.c	diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous. diff 74457d3d4327f7169df5e5596a955d1862b76270 Fri Jan 26 02:41:34 CET 2001 Brian Somers <brian@FreeBSD.org> Allow ``set server closed'' to close the diagnostic socket. Allow ``set server open'' to re-open the diagnostic socket. Handle SIGUSR1 by re-opening the diagnostic socket When receiving SIGUSR2 (and in ``set server none''), don't forget the socket details so that ``set server open'' and SIGUSR1 open it again. Don't create the diagnostic socket as uid 0 ! It's far to dangerous.