Bug 105331 - Empty file /success
Summary: Empty file /success
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-17 21:14 UTC by Christian Boltz
Modified: 2005-08-18 12:41 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
/var/log/messages (76.15 KB, text/plain)
2005-08-18 12:33 UTC, Christian Boltz 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2005-08-17 21:14:23 UTC 
After updating to 10.0 beta1, I found an empty file /success on my harddisk. 
 
Who or what is creating this file? 
Should it stay there intentional or is its deletion just forgotten?
Comment 1 Arvin Schnell 2005-08-18 07:21:59 UTC 
Please attatch y2logs and timestamp of that file.
Comment 2 Christian Boltz 2005-08-18 12:31:30 UTC 
# ls -l success 
-rw-r--r--  1 root root 0 2005-08-15 21:04 success 
 
I doubt that it has something to do with YaST - nearly every file 
in /var/log/YaST2 is two days older. Only y2start.log is newer that /success. 
Aditionally, I found the problem in an init script, so: no y2logs this 
time ;-) 
 
I'll attach /var/log/messages instead - please note it ends at Aug 15 21:03:56 
with a reboot (init 6). (I didn't start 10.0 beta since then.) 
 
One moment... 
# grep "/success" /etc/init.d/* 
 
Found it: It's in /etc/init.d/halt (and its symlink /etc/init.d/reboot) 
in line 67: 
    # Set a flag that we had success upto this point 
    > /success 
 
It seems the / filesystem is still mounted writeable at this moment...
Comment 3 Christian Boltz 2005-08-18 12:33:42 UTC 
Created attachment 46471 [details]
/var/log/messages
Comment 4 Arvin Schnell 2005-08-18 12:41:57 UTC 
So the file is in fact a flag and will also be removed in boot.localfs.
Everything is fine.