On Fri, Nov 22, 2002 at 12:26:18PM -0700, dave mallery wrote:
> another addendum, here's the real symptom in daemon.log:
>
> c0n5:/var/log>> tail daemon.log
> Nov 22 12:24:13 c0n5 init: Id "3" respawning too fast: disabled for 5
> minutes
> Nov 22 12:24:13 c0n5 init: Id "4" respawning too fast: d
another addendum, here's the real symptom in daemon.log:
c0n5:/var/log>> tail daemon.log
Nov 22 12:24:13 c0n5 init: Id "3" respawning too fast: disabled for 5
minutes
Nov 22 12:24:13 c0n5 init: Id "4" respawning too fast: disabled for 5
minutes
Nov 22 12:24:13 c0n5 init: Id "5" respawning too fa
>
> You can do something like last -f /var/log/wtmp.1
wow! a decoder ring!
scanning a 14,8mb wtmp file, it produces very little output
:
-rw-rw-r--1 root utmp 14849280 Nov 22 06:20 wtmp.1
c0n5:/var/log>> last -f /var/log/wtmp.1
wtmp.1 begins Thu Nov 21 06:25:03 2002
this file grows
dave mallery wrote:
> the problem with wtmp is that it shows (without a decoder ring) that
> there are thousands of logins per day on tty1 thru 6. that's odd on a
> cluster node on a private network behind a server behind a firewall.
> also no node has a keyboard! i can eliminate the file, but w
thanks much for the answer. i was able to eliminate the setuid logging
via the conf file.
the problem with wtmp is that it shows (without a decoder ring) that
there are thousands of logins per day on tty1 thru 6. that's odd on a
cluster node on a private network behind a server behind a firewal
dave mallery wrote:
> tens of thousands of entries running thru the /dev directory. these
> nodes develop 20+mb files per day.
>
> i can't find documentation on what program writes these files. man
> setuid only documents the library call.
It's generated by the checksecurity program. You migh
6 matches
Mail list logo
