|
Bugzilla – Full Text Bug Listing |
| Summary: | Empty file /success | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Christian Boltz <suse-beta> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /var/log/messages | ||
|
Description
Christian Boltz
2005-08-17 21:14:23 UTC
Please attatch y2logs and timestamp of that file. # 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...
Created attachment 46471 [details]
/var/log/messages
So the file is in fact a flag and will also be removed in boot.localfs. Everything is fine. |