| 1 |
Could it be an file system issue or something like that? or maybe an |
| 2 |
outdated init script? |
| 3 |
|
| 4 |
|
| 5 |
Rafael Barrera Oro wrote: |
| 6 |
> I ran the commands without any problems and the disk seems to work |
| 7 |
> fine, can i just remove those 2 lines from the bootmisc script until i |
| 8 |
> find a better solution? or is it kind of a tactic a redneck that came |
| 9 |
> from Texas Chainsaw Massacre would use? :P |
| 10 |
> |
| 11 |
> Thanks for the reply |
| 12 |
> |
| 13 |
> "Hmm, are you sure your disk drive isn't about to die?" <- disturbing, |
| 14 |
> i hope not! :P |
| 15 |
> |
| 16 |
> Richard Fish wrote: |
| 17 |
>> On 7/26/06, Rafael Barrera Oro <rafael@××××××××××××××××.ar> wrote: |
| 18 |
>>> anyway, this also happens when cleaning /var/run and /var/lock |
| 19 |
>> |
| 20 |
>> Hmm, are you sure your disk drive isn't about to die? Any other disk |
| 21 |
>> IO performance problems? |
| 22 |
>> |
| 23 |
>> What happens if you run the commands yourself manually after booting?: |
| 24 |
>> |
| 25 |
>> rm -f /tmp/.X*-lock /tmp/esrv* /tmp/kio* /tmp/jpsock.* /tmp/.fam* |
| 26 |
>> rm -rf /tmp/.esd* /tmp/orbit-* /tmp/ssh-* /tmp/ksocket-* /tmp/.*-unix |
| 27 |
>> |
| 28 |
>> -Richard |
| 29 |
> |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-amd64@g.o mailing list |
Archives