[ Ron Emaus writes: ]
>
> I'm using 1.94.1 on a sunos 4.1.x system and I still see shlock errors
> referring to L.Log (can't open, can't unlink).
There are several places where shlock.pl emits unnecessary warnings, but
I was hesitant to remove all of them in 1.94.1 (I'm more sure of their
irrelevancy now). Prior to 1.94 they were being dumped into stderr and
never seen, but that got "fixed" so now they're getting logged/mailed.
If you're not seeing failures and aborts resulting from these warnings,
ignore them. I hate to issue untested patches and I don't have time to
do what's required right now, but it looks to me like the following
alert() calls can be commented out in shlock.pl:
255 #&alert("shlock: open('$file'): $!");
^
287 unlink($tempname);# || &alert("shlock: unlink('$tempname'): $!");
^^
If that doesn't stop the warnings, you need to be sure you don't have
a bogus L.Log (or L.whatever in the lists directory) lying around with
owner/permissions that Mj can't open/unlink. Failing that, modify each
of the &alert("shlock: ...") messages to be unique (__LINE__ comes to
mind) and let me know which one is complaining.
--
Dave Wolfe
References:
|
|
