Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!tgr!rsk@asc.purdue.edu From: rsk@asc.purdue.edu (Wombat) Newsgroups: net.unix-wizards Subject: Re: Idle time logout mechanism (daemon) Message-ID: <11646@brl-tgr.ARPA> Date: Wed, 17-Jul-85 16:25:03 EDT Article-I.D.: brl-tgr.11646 Posted: Wed Jul 17 16:25:03 1985 Date-Received: Fri, 19-Jul-85 02:11:37 EDT Sender: news@brl-tgr.ARPA Lines: 31 > From: Barry Gold > DON'T DO IT. Try to educate your users to be more cooperative while you get > more ports. If necessary, increase the charge for connect time. In our environment, these are not viable alternatives; we are adding ports, and we have (in the past) increased the charge for connect time; neither has discouraged port-sitting. Therefore, we have such a daemon. > If you put in a daemon to monitor idle time, you'll just encourage your > users to write programs that make their terminals appear non-idle. 'Tis true. However, most users will not be so clever--we hope. In the case of those that are, 'we will find them, and we will kill them'.(1) > The solution to inadequate computing resources is to get more resources. > If you can't afford more resources, charge enough for your computing > that you CAN get more resources. Perhaps. Another solution is to make *intelligent* use of the resources one has; in our case, since we are a university computing center, it is clearly the preferred choice. I don't like the idea of using such a daemon; however, after much debate and discussion, we have concluded that it's the only way to solve our problem. It may be fascist, but it works. Rich Kulawiec Purdue University Computing Center (1) Saturday Night Live, 1984.