Article View: mod.computers.pyramid
Article #10solution to /etc/.attwtmp problem
From: info-pyramid
Date: Fri, 31 Jan 1986 20:00
Date: Fri, 31 Jan 1986 20:00
21 lines
1646 bytes
1646 bytes
First off, I would like to thank all those people who replied to my
request for help. Second, I want to apologize for not getting back with a
response sooner than I have.
As it turns out, the problem was because the version of our LAN that was
connected to the Pyramid would leave carrier detect high, with or without
a real connection. Thus, our gettys (about 25) were being respawned every
30 secs. Each getty makes an entry in /etc/.attwtmp.
Our solution came about when we upgraded the firmware on our LAN. However,
since there are still entries being made in .attwtmp there is a more
elegant solution to the problem. Link /etc/.attwtmp to /dev/null. We
don't use the AT&T accounting system, we have our own, so there was no
need to have any of the entires. Also, since there is no way to disable
the entires being added, linking .attwtmp sends all of the junk to the
great bit bucket in the sky.
-- Brad Brahms
usenet: {decvax,ucbvax,ihnp4}!trwrb!trwspp!brahms
arpa: Brahms@usc-eclc
Technical Details
Message-ID:
<8601312000.AA16327@spp5.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!decvax!decwrl!ucbvax!info-pyramidShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: arc1-ca.pugleaf.net!utzoo!decvax!decwrl!ucbvax!info-pyramid From: info-pyramid@ucbvax.UUCP Newsgroups: mod.computers.pyramid Subject: solution to /etc/.attwtmp problem Message-ID: <8601312000.AA16327@spp5.UUCP> Date: Fri, 31-Jan-86 15:00:00 EST Article-I.D.: spp5.8601312000.AA16327 Posted: Fri Jan 31 15:00:00 1986 Date-Received: Sat, 1-Feb-86 18:42:33 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 21 Approved: info-pyramid@mimsy.umd.edu