/var/run/utmp permissions differ from those suggested in man 5 utmp
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Warning: utmp must not be writable, because many system programs (fool-
ishly) depend on its integrity. You risk faked system logfiles and
modifications of system files if you leave utmp writable to any user.
I checked on a clean install in a virtual machine, and the permissions are the same. Is this a problem?
I misunderstood the two statements: "utmp must not be writable" and subsequently "writable by any user" as meaning utmp must not be writable to anyone, no matter whether they owned the file or were part of its group (hence any user). I was expecting to see permissions of -r--r--r-- if anything. Thanks for pointing out the real meaning (though I think the man page could be worded less ambiguously).
Maybe replace "any user" with "other user" ?
English is not my first language though, so I can't tell
But if a Linux admin set any user in utmp group, he should be fired asap imo
Location: @ /home & @ my blog at http://saurabh-nigam.blogspot.com/
Distribution: Slackware , Fedora , Ubuntu
Posts: 35
Rep:
Hi all , did any of you figured the solution?
In my case too it says
Code:
touch /var/run/utmp :No such file or directory
chown /var/run/utmp :No such file or directory
chmod /var/run/utmp :No such file or directory
touch /var/lock/subsys/serial :No such file or directory
then it hangs on to
Code:
sysklogd
and doesn't boots further but it does boot in single user mode (& I can login as root).
Help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.