home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!uwm.edu!ogicse!flop.ENGR.ORST.EDU!gaia.ucs.orst.edu!gaia.ucs.orst.edu!news
- From: mickel@OES.ORST.EDU (Paul M. Mickel)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: how to force readers to read a system message?
- Message-ID: <1gmbvbINNo17@gaia.ucs.orst.edu>
- Date: 16 Dec 92 04:40:11 GMT
- References: <15DEC92.09272432@cc4.crl.aecl.ca> <LARRY.92Dec15123709@shark.mitra.com>
- Organization: Oregon Extension Service, Oregon State University, Corvallis, Or.
- Lines: 20
- NNTP-Posting-Host: oes.orst.edu
-
- In article <LARRY.92Dec15123709@shark.mitra.com> larry@shark.mitra.com (Larry Williamson) writes:
- >You can lead a horse to water...
-
- Very true. I usually ignore it in most cases :) :)
-
- Seriously, you could write a shell script to do this. I did this once to
- force our users to change their passwds. I modified .login, after saving the
- old one, executed my .login, swap the old one back, then "source <real_.login>"
- While you can break out if a shell script, most of my customers don't know
- how, so I took advantage of this fact.
-
- Good luck.
-
- -pmm
-
- --
- Paul M. Mickel Internet:mickel@oes.orst.edu
- Sysadmin, Oregon Extension Service Corvallis, OR 97331
- Database Programmer, Teledyne Wah Chang Albany, OR
- Disclaimer: Neither employer has *ever* claimed any of my opinions.
-