>The last 6 months our school has been running a RH6
>firewall+proxy(squid)
>A few weeks ago squid fell over.
>Status command gave the following:
>
>squid dead but subsys locked
>squid: ERROR: no running copy.
This means that squid wasn't running but there was a lockfile left behind
in /var/lock/subsys
>( I think) it was due to the log files filling the drive so I proceeded
>to delete them.
>All was well until yesterday. Now a status gives the following:
>
>squid dead but pid file exists
>squid: ERROR: could not send signal to 0 to process 1785: (3) No such
>process
>the '1785' is not constant.
Same thing. Squid died but the file /var/run/squid.pid (I think) still
exists. So the script could not send a signal 0 (used to check if a
process is running) to that process since it didn't exist anymore.
>If any one can shed some light onto this probem I would greatly
>appreciate it.
What you have to find out is why squid is keeling over, then these
side-effects will go away.
Cc'ed to the Linux In Australian Schools list, you may want to subscribe
at http://lists.linux.org.au
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
