tomc@oakhill.UUCP (Tom Cunningham) (11/30/88)
I've just latched onto this group so I hope you'll bear with me if these
queries are reruns. We have a DN4000 running DOMAIN/IX 9.5 4.2BSD. The
system has a 170MB (~?) internal hard disk and a cartridge tape drive (no
floppy). It has an Ethernet interface card which hooks the machine into a
network of (primarily) Suns; it is not on an Apollo ring at all. We are
running TCP/IP and NFS.
I noticed that when using the Unix who command some users would be reported
as being logged in when in fact they weren't (these were usually rlogin
users). These entries would stay around for some time, so finally I decided
to flush the /etc/utmp file by deleting it and recreating it as empty.
Well, after doing that who does not work at all (e.g. it doesn't report that
anyone is logged on)! The /etc/utmp file appears to be getting updated, but
I haven't a clue as to whether the data is valid or not (who doesn't
complain, just returns silently).
Also I cannot get tar to work with the cartridge tape. I have tried
/dev/rct8 and /dev/rct12 (the only reasonable-looking device entry points
for the cartridge tape), but in both cases tar says it cannot open the
device. Have I failed to configure something properly, or am I just missing
something? A sample tar command I use from within csh is:
tar cvf /dev/rct8 . .
Thanks for any help you can give!
--
Tom Cunningham Motorola Inc. Austin TX
{sun,uunet!mnetor,cs.utexas.edu}!oakhill!tomcdclemans.falcon@mntgfx.mentor.com (Dave Clemans) (12/02/88)
From article <1716@bouwsma.oakhill.UUCP>, by tomc@oakhill.UUCP (Tom Cunningham): > > Also I cannot get tar to work with the cartridge tape. I have tried > /dev/rct8 and /dev/rct12 (the only reasonable-looking device entry points > for the cartridge tape), but in both cases tar says it cannot open the > device. Have I failed to configure something properly, or am I just missing > something? A sample tar command I use from within csh is: > tar cvf /dev/rct8 . . > Try using an Aegis command first (for example, /com/rbak -dev ct -rewind). Before doing that I usually see problems like you describe; after that everything works fine. dgc