home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.hackers
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!wupost!gumby!destroyer!ubc-cs!newsserver.sfu.ca!howesb
- From: howesb@fraser.sfu.ca (Charles Howes)
- Subject: Re: making the named pipe work on a cluster
- Message-ID: <1992Jul30.215954.22281@sfu.ca>
- Sender: news@sfu.ca
- Organization: Simon Fraser University, Burnaby, B.C., Canada
- References: <1992Jul27.231625.18562@constellation.ecn.uoknor.edu> <1992Jul28.045610.15540@reed.edu> <82mm#9=.xtifr@netcom.com>
- Distribution: usa
- Date: Thu, 30 Jul 1992 21:59:54 GMT
- Approved: uoknor@uoknor.edu
- Lines: 16
-
- In article <82mm#9=.xtifr@netcom.com> xtifr@netcom.com (Chris Waters) writes:
- >ObSheesh: named pipes, migawd! A classic example of approaching this
- >problem from the wrong end.
-
- How about a personal daemon to change the .signature file if its access time
- changes? Cron-ify it so that it doesn't waste CPU time. Much.
-
- Obhack: Writing a program that sits in a temporary directory and nukes files
- shortly after their access and modification times disagree. When all files are
- gone, self-destruct. This is useful if you're downloading files to a PC via
- ethernet and FTP. You can do an 'mget *' and the files will be gone when
- you're done.
-
- Actually, since a file exists if it is held open, you could create an
- 'imaginary file' server. How could anybody recover the data if they didn't
- go through the server?
-