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