#264 closed defect (fixed)
Bootscripts: creating new /var/run/utmp doesn't work
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | highest | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: |
Description
Hello
I've been testing the 1.1 bootscripts. So far so good! Except for a couple of typos "Clearning -> Clearing" :-)
One thing that puzzled me slightly was this part of cleanfs
echo -n "Creating new /var/run/utmp..." touch /var/run/utmp && chmod 644 /var/run/utmp evaluate_retval
That won't achieve anything will it? I don't see the point. Was the intention to start a fresh utmp file every reboot? If so then methinks it is missing a "rm -f /var/run/utmp".
Greg
This only updates the "modified" time of /var/run/utmp. It's better to use
echo -n "" >/ver/run/utmp
instead
Change History (6)
comment:1 by , 23 years ago
comment:3 by , 23 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 by , 23 years ago
it's fixed, but new lfs-bootscripts tarball not uploaded yet. I'll do so when the other bugs pertaining bootscripts are taken care of too and make it one update rather than 3 small updates.
comment:6 by , 23 years ago
Keywords: | VERIFIED removed |
---|
Just for the record: as discussed in on the mailinglist already: cleanfs script removes /var/run/* so utmp is removed, then re-created with the touch command.