Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.sprintlink.net!ratty.wolfe.net!news.ATNET.NET!usenet From: jwshafto@atnet.net (John Shafto) Newsgroups: comp.unix.bsd.bsdi.misc,comp.unix.bsd.freebsd.misc Subject: Controlling Ports Date: Mon, 19 Feb 1996 11:29:30 GMT Organization: AtNet Connections Lines: 34 Message-ID: <4g9ms7$puj@news.atnet.net> Reply-To: john@shafto.org NNTP-Posting-Host: sysadmin.atnet.net X-Newsreader: Forte Free Agent 1.0.82 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:2415 comp.unix.bsd.freebsd.misc:14090 Hello, OK, I gotta beg in these groups for help :) I have a couple problems on my BSDI2.0 PPP Server that I can't seem to resolve. Please copy me via email with any resolution, as I may not get back here in time. Thanks for any and all help! 1.) When user hangs up in Pine or Lynx (amoung others) BSDI does not shut down jobs associated with the port, and worse, the modem doesn't reset, nor does the getty restart on the port. Hence, there is then a line in the middle of the hunt group that won't answer (until the errant job is killed, then everything resets). My FreeBSD boxes don't do this. I suspect that there is a simple STTY setting, but I am at a loss to find it. 2.) I am in need of a watchdog program to monitor ports, and kill them, or maybe send mail, if they are on for some set period of time. This software might also be a resolution for the first problem if it could check for jobs without controlling ports. Source, pointers to archives, or any ideas welcome. Regards, --- ::: John Shafto ::: JWShafto@atnet.net ::: N7YAO, I'll speak for anyone. AT-NET Connections, Inc. (509) 766-7253 Innovation is hard to schedule.