Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 alpha 4/3/85; site ukma.UUCP Path: utzoo!watmath!clyde!cbosgd!ukma!david From: david@ukma.UUCP (David Herron, NPR Lover) Newsgroups: net.bugs.uucp Subject: Re: Read permission on /etc/phones Message-ID: <1953@ukma.UUCP> Date: Wed, 10-Jul-85 00:23:00 EDT Article-I.D.: ukma.1953 Posted: Wed Jul 10 00:23:00 1985 Date-Received: Sat, 13-Jul-85 08:28:00 EDT References: <472@qantel.UUCP> <170@motel6.UUCP> <> <154@telesoft.UUCP> <696@lsuc.UUCP> <697@lsuc.UUCP> Reply-To: david@ukma.UUCP (David Herron, NPR Lover) Organization: Univ. of KY Mathematical Sciences Lines: 32 Keywords: tip, uucp, LCK In article <697@lsuc.UUCP> dave@lsuc.UUCP (David Sherman) writes: >In article <696@lsuc.UUCP> I write: >||Why not just write a simple set-UID program which removes >||the LCK file and nothing else? You can get fancy with various >||checks, of course, but in its simplest form it's a one-line >||C program. > >Whoops, I forgot one thing. You want this done automatically >when tip exits. So move tip to /usr/lib and make tip a shell >file which reads > trap '/usr/lib/cleanLCK' 0 1 2 3 9 15 > /usr/lib/tip $* How does this solve anything? I don't see where this removes the lock file. 1) cleanLCK isn't called explicitly, only on a signal, which won't happen. 2) cleanLCK *cannot* know which lock file to delete. Answer me one question, why are we discussing tip problems in net.bugs.uucp? -- --- David Herron --- ARPA-> ukma!david@ANL-MCS.ARPA or ukma!david<@ANL-MCS> --- or david%ukma.uucp@anl-mcs.arpa --- Or even anlams!ukma!david@ucbvax.arpa --- UUCP-> {ucbvax,unmvax,boulder,oddjob}!anlams!ukma!david --- {ihnp4,decvax,ucbvax}!cbosgd!ukma!david "It's *Super*User* to the rescue!"