Could it be an file system issue or something like that? or maybe an
outdated init script?
Rafael Barrera Oro wrote:
I ran the commands without any problems and the disk seems to work
fine, can i just remove those 2 lines from the bootmisc script until i
find a better solution? or is it kind of a tactic a redneck that came
from Texas Chainsaw Massacre would use? :P
Thanks for the reply
"Hmm, are you sure your disk drive isn't about to die?" <- disturbing,
i hope not! :P
Richard Fish wrote:
On 7/26/06, Rafael Barrera Oro <[EMAIL PROTECTED]> wrote:
anyway, this also happens when cleaning /var/run and /var/lock
Hmm, are you sure your disk drive isn't about to die? Any other disk
IO performance problems?
What happens if you run the commands yourself manually after booting?:
rm -f /tmp/.X*-lock /tmp/esrv* /tmp/kio* /tmp/jpsock.* /tmp/.fam*
rm -rf /tmp/.esd* /tmp/orbit-* /tmp/ssh-* /tmp/ksocket-* /tmp/.*-unix
-Richard
--
[email protected] mailing list
