Thanks Philip, On Sunday 23 July 2006 14:29, Philip Webb wrote: > 060723 Philip Webb wrote:
> I deleted all the sh-np's in my own /tmp & rebooted without any problem. I assume what you say is that they were not recreated? > Also looking in my archives at the output of Elog , > there were 2 packages which was updated around both those dates, ie > > bzip2-1.0.2-r4 -> r5 & 1.0.3 -> 1.0.3-r4 > shadow-4.0.5-r2 -> r3 & 4.0.5-r3 -> 4.0.7-r3 > > Perhaps this may point someone to an explanation. If you are not getting these creatures in your /tmp dir anymore and assuming that they are kernel dependent, it may be that they will cease to be created soon as I update this (stable) machine and roll up my next kernel version (I'm on 2.6.16-gentoo-r13 now). This leaves the gnupg problem. Any idea what the log-socket file is all about? srwxr-xr-x 1 michael users 0 Jun 6 20:29 log-socket I moved it, it was not re-created yet and there doesn't seem to be a problem so far, other than the error message when I manually launch gpg: ================================ $ eval "$(gpg-agent --daemon)" can't connect to `/home/michael/.gnupg/log-socket': No such file or directory ================================ If you remember my previous message when the lock file was still there, I was getting: can't connect to `/home/michael/.gnupg/log-socket': Connection refused So it seems to need the lock file but I don't really know how it is (re)created. Any ideas anyone? -- Regards, Mick
pgp4h4LDISh54.pgp
Description: PGP signature
