home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zephyr.ens.tek.com!uw-beaver!micro-heart-of-gold.mit.edu!rutgers!usc!wupost!darwin.sura.net!jvnc.net!netnews.upenn.edu!eniac.seas.upenn.edu!chip
- From: chip@eniac.seas.upenn.edu (Charles H. Buchholtz)
- Newsgroups: comp.unix.questions
- Subject: Re: Finger and .plan, .project
- Message-ID: <84433@netnews.upenn.edu>
- Date: 26 Jul 92 15:21:57 GMT
- References: <19076@fritz.filenet.com> <14u80cINNbd8@grasp1.univ-lyon1.fr>
- Sender: news@netnews.upenn.edu
- Organization: University of Pennsylvania
- Lines: 25
- Nntp-Posting-Host: eniac.seas.upenn.edu
-
- scotth@felix.filenet.com (Scott Hopson) suggested using a named pipe
- as your .plan file.
-
- Christophe.Wolfhugel@univ-lyon1.fr (Christophe Wolfhugel) gave lots of
- good reason why this is a bad idea.
-
- To which I'll add one more: we share a lot of home directories via NFS
- between machines. So, you may have the same home directory on dozens
- of machines. If your .plan is a named pipe, it is associated with a
- process on *one* of those machines, on all of the other machines any
- access will hang.
-
- I got tired of having to kill off hung fingerd processes (owned by
- "nobody", so only root can get rid of them), so I installed a new
- version of finger. Works great - only accesses regular .plan and
- .project files, gives an error for named pipes, sockets, etc, etc.
-
- I considered writing one which would execute .plan if it was
- executable, to allow people to run a program when they got fingered,
- but I got overwhelmed by the security issues.
-
-
- Charles H. Buchholtz Systems Programmer chip@seas.upenn.edu
- School of Engineering and Applied Science
- University of Pennsylvania
-