Subject: daily script file problem
To: netbsd <amiga@NetBSD.ORG>
From: Berndt Josef Wulf <wulf@hotdog.apana.org.au>
List: amiga
Date: 09/20/1995 19:58:42
Hi all,
since the installation of netbsd-current-950902, I have problems with the
execution of the daily script file being executed.
There are no error messages, neither does it cause the system to crash, but it
leaves a trail of not completed/terminated processes behind:
PID TT STAT TIME COMMAND
0 ?? DLs 0:00.54 (swapper)
1 ?? Is 0:00.45 /sbin/init
2 ?? DL 0:02.23 (pagedaemon)
20 ?? Is 0:01.16 mfs -s40560 /dev/sd1b /tmp (mount_mfs)
48 ?? IWs 0:00.18 portmap
56 ?? Ss 0:07.93 syslogd
72 ?? Ss 0:07.38 update
74 ?? Is 0:04.16 cron
78 ?? Ss 0:02.50 routed -q
81 ?? Is 0:05.36 named
87 ?? IWs 0:00.30 lpd
109 ?? Is 0:00.74 sendmail: accepting connections (sendmail)
112 ?? Is 0:00.81 inetd
143 ?? Is 0:04.79 /usr/local/etc/innd -p4 -i0
1122 ?? IW 0:00.13 /usr/local/infosystems/WWW/bin/httpd -r /usr/local/infosystems/WWW/con
>1281 ?? IW 0:00.15 CRON (cron)
>1284 ?? IWs 0:00.27 /bin/sh -c /bin/sh /etc/daily 2>&1 | tee /var/log/daily.out | mail -s
>1288 ?? IW 0:01.33 /bin/sh /etc/daily
>1289 ?? IW 0:00.31 tee /var/log/daily.out
>1291 ?? IW 0:00.33 mail -s daily output root
>1344 ?? IW 0:03.46 sh /etc/security
>1345 ?? IW 0:00.31 mail -s daily insecurity output root
>1908 ?? IW 0:00.20 sh /etc/security
>1909 ?? DW 1:45.15 / (find)
>1910 ?? IW 0:00.39 sort
>1911 ?? IW 0:00.24 sed -e s/^/ls -ldgT /
>1912 ?? IW 0:00.20 sh
2513 ?? I 0:00.21 sendmail: server pain.lcs.mit.edu cmd read (sendmail)
146 e0 IWs+ 0:00.32 /usr/libexec/getty Pc ttye0
163 e1- IW 0:00.04 slattach -h -s19200 /dev/tty00
2519 e1 Ss 0:01.45 -csh (csh)
2527 e1 R+ 0:00.14 ps -ax
The daily.out logfile was created, but the mail notifier never made it to its
destination. I had the same problem once before when trying an earlier version of
netbsd-current (can't remember the actuell version).
Mail seems to get in and out the system without problem, since I am still receiving
the netbsd mailing lists ;-)
A similar problem which I have noticed before, was that in some cases I was
unable to kill slattach (kill -9 slattach_process_number). The only way of terminating
this process was to reboot (changing into single user mode didn't work).
Anyone with some ideas????
cheerio Berndt
--
Name : Berndt Josef Wulf | Amiga 4000/40-25, 16MB, NetBSD-1.0-950902
E-Mail : wulf@hotdog.apana.org.au | Cybervision64 4MB , Retina-Z2 4MB,
Phone : ++61 411 245170 | Z3-Fastlane, A2065 Ethernet