home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!mips!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!rutgers!noao!amethyst!organpipe.uug.arizona.edu!neilb
- From: neilb@scs.leeds.ac.uk (Neil Bowers)
- Newsgroups: alt.hackers
- Subject: Re: making the named pipe work on a cluster
- Message-ID: <1992Jul27.211627.1584@organpipe.uug.arizona.edu>
- Date: 27 Jul 92 21:16:27 GMT
- References: <14q0udINNl6o@agate.berkeley.edu> <end1H060q8@atlantis.psu.edu> <1992Jul27.190402.13876@bradley.bradley.edu>
- Sender: news@organpipe.uug.arizona.edu
- Distribution: usa
- Organization: The University of Leeds, School of Computer Studies
- Lines: 18
- Approved: jef@netcom.com
-
- pwh@bradley.bradley.edu (Pete Hartman) writes:
- >Ok, drop the other shoe, then.
- >
- >I don't want code, just an idea of what a better solution for a random
- >sig generator would be.
-
- Couple of quick ideas, depends on how often you want to change your sig
-
- daily: setup a script which soft-links .signature to one of your collection
- of signatures.
-
- each rn session:
- have a script "my<newsreader>", which makes a soft-link before exec'ing
- <newsreader>
-
- every post:
- take a copy of (Pnews|inews) and modify it, to pick a different sig
- each time
-