home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!mimsy!afterlife!adm!news
- From: jyacc!dtroxell%aspen@uunet.uu.net (Dan Troxell - SysAdm (NE))
- Newsgroups: comp.unix.questions
- Subject: dump/rdump in single-user
- Message-ID: <32121@adm.brl.mil>
- Date: 20 Aug 92 03:20:08 GMT
- Sender: news@adm.brl.mil
- Lines: 38
-
- Mark,
-
- >I'm trying to set up a dump schedule for various Suns. I want to dump to a
- >cartridge drive on an IBM RS/6000. So I read the FM and it says that I need
- >to use rdump, and that I should use it from single-user mode.
- >
- >Mark Flynn
- >Liquid Crystal Institute
- >Kent State University
- >flynn@nematic.kent.edu
-
-
- Forget the single-user stuff -- the keywords here for SUN's dump/rdump
- are ( quote from SUN )
-
- '... on a quiescent system.'
-
- This means you will lose updates to files made after the 'dump' takes it's
- inode count. Bringing the system up single-user ensures that no one can
- get in the way with their pesky file updates.
-
- One way around this is to simply distribute the file /etc/nologin to
- all systems. A check for this file's existence takes place during every
- login attempt -- if it exists, it displays its text ( like motd ) and boots
- the user out. The shutdown command also does this with a certain flag
- ( i ferget ) but then you get those stupid broadcast messages ( and who's
- gonna see them at 3am, anyway? ). I have a simple script that sends the
- /etc/nologin's out and then deletes them again upon completion. Be sure to
- run a cron job later on to check for /etc/nologin's -- if there's any
- hangin' around you'll get some angry users. :^)
-
- dan
-
- =================================================================
- dan troxell, SysAdm Jyacc,Inc. 55 William Street Ste 300
- dtroxell@jyacc.com Wellesley, MA 02181
- uunet!jyacc!dtroxell 617.431.7431 x113
- =================================================================
-