Thanks for the reply, i tried that and i got the following:
total 16184
drwxrwxrwt 16 root root 4096 Jul 26 11:25 .
drwxr-xr-x 20 root root 4096 Jul 24 12:25 ..
drwxrwxrwt 2 root root 4096 Jul 26 11:24 .ICE-unix
drwxrwxrwt 2 root root 4096 Jul 26 11:24 .X11-unix
drwxr-xr-x 2 root root 4096 Jul 20 12:41 .initrd
drwx------ 2 root root 4096 Jul 24 11:05 .xorg.conf10031
drwx------ 2 root root 4096 Jul 24 11:46 .xorg.conf1631
drwx------ 2 root root 4096 Jul 24 11:46 .xorg.conf1671
drwx------ 2 root root 4096 Jul 24 08:41 .xorg.conf21897
drwx------ 2 root root 4096 Jul 24 10:57 .xorg.conf9760
drwx------ 2 root root 4096 Jul 24 10:59 .xorg.conf9802
drwx------ 2 1003 513 4096 Jul 26 09:13 gconfd-rafael
drwxr-xr-x 2 root root 4096 Jul 26 11:19 hsperfdata_root
-rw-r--r-- 1 1003 513 16482873 Jul 26 08:33
jre-1_5_0_07-linux-amd64.bin
drwx------ 2 1003 513 4096 Jul 26 11:24 kde-rafael
drwx------ 2 1003 513 4096 Jul 26 11:24 ksocket-rafael
drwx------ 2 1003 513 4096 Jul 26 09:13 orbit-rafael
anyway, this also happens when cleaning /var/run and
/var/lock
the biggest file i ve got is
"jre-1_5_0_07-linux-amd64.bin" whichs was
put in the /tmp after this error began to appear, could it
be a
permission issue?
i guess a quick fix would be to comment the corresponding
lines in
/etc/init.d/bootmisc but i suppose those lines are there for
reason
thanks for the help
J'raxis 270145 wrote:
> Could just an enormous number of temp files something
left behind? Try
> adding a line such as:
>
> ls -la /tmp 2>&1 | tee /var/tmp/tmp-listing
>
> right before the "Clean up /tmp directory"
comment block in
> /etc/init.d/bootmisc. That'll print it to the screen,
and save it to
> /var/tmp/tmp-listing if you want to look back on it
later.
>
> At 2006-07-25T12:42:33+0000, <rafael akyasociados.com.ar> wrote:
>
>
>> Whenever my system boots, it hangs on
"Cleaning /tmp directory ..." for
>> a long time, a very uncomfortable, irrational, no
good, painful,
>> desperating long time.
>>
>> I have an Athlon64 with x86_84
gentoo-sources-2.6.16-r13 and no idea how
>> to fix it.
>>
>> Any ideas of what could be wrong? anyone? sure?
>>
>> Thanks in advance
>>
>> Rafael
>> --
>> gentoo-amd64 gentoo.org mailing list
>>
>
>
--
gentoo-amd64 gentoo.org mailing list
|