Searched hist:71657 (Results 1 - 8 of 8) sorted by relevance
| /freebsd-9.3-release/usr.sbin/ppp/ | ||
| H A D | server.h | diff 71657 Thu Jan 25 23:41:34 MST 2001 brian 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 71657 Thu Jan 25 23:41:34 MST 2001 brian 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 71657 Thu Jan 25 23:41:34 MST 2001 brian 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 71657 Thu Jan 25 23:41:34 MST 2001 brian 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 71657 Thu Jan 25 23:41:34 MST 2001 brian 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 71657 Thu Jan 25 23:41:34 MST 2001 brian 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 71657 Thu Jan 25 23:41:34 MST 2001 brian 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.m4 | diff 71657 Thu Jan 25 23:41:34 MST 2001 brian 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. |
Completed in 191 milliseconds