Subject: | |
From: | |
Reply To: | |
Date: | Wed, 9 Aug 2006 19:54:36 +0200 |
Content-Type: | TEXT/PLAIN |
Parts/Attachments: |
|
|
Hi Jarek,
On Wed, 9 Aug 2006, Jaroslaw Polok wrote:
> Hi
>
> > Maybe your client is immune to the problem. Meaning you'd have an AFS
> > client that's POSIX compliant w.r.t. fcntl locks on deleted files, if I
> > got it right. I gave up extracting the changes from your SRPM last time I
> > looked at it, but maybe I should really try harder ;-)
>
> No it isn;t, but maybe our systems are more stable ? ;-)
Right, maybe. Or maybe our users simply aren't used to malfunctions like
this one and complain right away ;-)
> First problem report just came ..
[Stephan breathing a sigh of relief] Sooo sorry that after all this is not
a problem of PSI and DESY only.
> I think we'll use the firefox/mozilla/thunderbird init.d workaround ..
>
> >[ -e $HOME/.mozilla/firefox/profiles.ini ] &&
> > for i in $(grep Name= $HOME/.mozilla/firefox/profiles.ini | sed s/Name=//)
> > do
> > [ ! -L $HOME/.mozilla/firefox/*.$i/lock -a -e
> >$HOME/.mozilla/firefox/*.$i/.parentlock ] &&
> > rm -f $HOME/.mozilla/firefox/*.$i/.parentlock
> > done
This is what we actually rolled out for firefox (thunderbird to follow):
#!/bin/sh
[ -e $HOME/.mozilla/firefox/profiles.ini ] || exit 0
for i in $(grep Path= $HOME/.mozilla/firefox/profiles.ini | sed s/Path=//); do
[ ! -L $HOME/.mozilla/firefox/$i/lock -a -e
$HOME/.mozilla/firefox/$i/.parentlock ] &&
rm -f $HOME/.mozilla/firefox/$i/.parentlock
done
I know that "improvements" like this almost always backfire. Couldn't
resist anyway. Thanks again to Gerd! This workaround seems to be working
out very well here so far.
Cheers,
Stephan
--
Stephan Wiesand
DESY - DV - Phone: +49 33762 7 7370
Platanenallee 6 Fax: +49 33762 7 7216
15738 Zeuthen, Germany
|
|
|