http://qa.mandrakesoft.com/show_bug.cgi?id=2337
------- Additional Comments From [EMAIL PROTECTED] 2003-03-31 15:36 ------- In my RC3 system (cooker burned after the freeze) with standard security level, I noticed after several reboots and logout/logins from GNOME that the GNOME logout process was taking 5-10 minutes to put up the logout/shutdown/reboot prompt. I've seen similar problems in the past having to do with stale lock files, so I looked and noticed that /tmp was no longer using tmpfs, but was a live directory, and that the .X* directories were not getting cleaned out. I reinstated tmpfs for /tmp in /etc/fstab, and the problem went away. This ties into a problem that existed pre-9.0 (when /tmp started to use tmpfs) that the MDK initscripts do not properly clean out /tmp when the boot option to do so is checked. They delete some files, but not others, probably because the cleanup is run too late in the sequence and /tmp is already in use by X. As far as I know, this was never fixed, but became a non-problem with the introduction of tmpfs. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Hi, by download, mozilla creates a temporary file (something.exe) in /tmp. However, /tmp is now a filesystem by default with size approximately 200MB. Thus one cannot download files larger than 200MB. Is it enough to delete the /tmp line in /etc/fstab? (Suse suggests aleso changes in /etc/init.d/boot.swap? Except of not using the tmpfs for /tmp, is it possible to change the behavior of mozilla? I did not find anything in Preferences. Thanks Milos
