Re: unlinkd usage

In article <199801150444.PAA09839@grey.interact.net.au>,
Tom Minchin <tom@interact.net.au> wrote:
>Hi,
> I've noticed that on my 1.NOVM.19/20 caches unlinkd doesn't seem
>to get any use. On Linux, it's swapped out and doing nothing according to
>strace, even though Squid is currently deleting objects by the score -
>strace on squid shows it happily unlinking away on its own.
>
> Looking at the cachemgr, it does show that requests have been
>sent to unlinkd. It looks like it is not getting them.

I have exactly the same problem, but I cannot see for the life of
me why it doesn't work. Squid is dead-slow at the moment - every
request takes 2 or 3 seconds to get processed.

Unlinkd in itself works fine:

# touch /tmp/la
# /usr/lib/squid/unlinkd
hi there
/tmp/la
# ll /tmp/la
ls: /tmp/la: No such file or directory
#

Since I run this under Linux, I can locate the pipe that connects squid and
unlinkd together (in /proc/squid.pid/fd/13 or so) and write something to it.
If I then strace unlinkd, I can see that it's working OK.

It's just that squid never seems to write to the unlinkd pipe. Nothing
in the logfiles (debug_trap() should always log something, right?).

Hmm, while I am writing this, unlinkd suddenly started running. Heisenbug?
I am doing an strace on it, and for the first time in three days (since
squid started) requests are being sent to unlinkd. But the strace had
been hanging idle on the unlinkd process for at least 5 minutes..

Really strange !

Mike.

-- 
 Miquel van Smoorenburg |  The dyslexic, agnostic, insomniac lay in his bed
    miquels@cistron.nl  |  awake all night wondering if there is a doG