From: "Jim Gifford" <maillist@jg555.com>
To: linux-hotplug@vger.kernel.org
Subject: Strange udev problem
Date: Thu, 17 Jun 2004 06:04:45 +0000 [thread overview]
Message-ID: <042401c45430$fd8c72e0$d100a8c0@W2RZ8L4S02> (raw)
I'm using udev027 and sometimes I notice that the permissions change on my
/dev entries. Here is the scenario
I run distcc on an internal lan. I was compiling the kernel on one of the
machines, when the main machines /dev/null changed it's permissions. I have
the udev set to log, but never see any for the creation of /dev/null. I
rebooted the machine in question and double checked my config files, and
everything looks to be in proper order. I also noticed that some of my tty
and psaux devices also changed permissions. The exact same permissions 0600,
which is listed in udev.conf
I verified in my permissions file that
null:root:root:0666,tty[0-9]*:root:tty:0666, and psaux:root:root0644.
The only common things on these boxes is distcc. I'm currently trying to
disable distcc to see if it is the cause of the problem, but I doubt it
since distcc is setup to run as a non-privileged user. Will update after
testing with out distcc is completed.
----
Jim Gifford
maillist@jg555.com
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-06-17 6:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 6:04 Jim Gifford [this message]
2004-06-17 11:37 ` Strange udev problem Kay Sievers
2004-06-17 12:45 ` Jim Gifford
2004-06-17 13:31 ` Jim Gifford
2004-06-17 15:01 ` Kay Sievers
2004-06-17 15:03 ` Richard Troth
2004-06-18 0:23 ` Jim Gifford
2004-06-18 16:16 ` Jim Gifford
2004-06-18 17:51 ` Greg KH
2004-06-18 18:24 ` Jim Gifford
2004-06-19 4:40 ` Jim Gifford
2004-06-19 16:31 ` Jim Gifford
2004-06-20 0:34 ` Jim Gifford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='042401c45430$fd8c72e0$d100a8c0@W2RZ8L4S02' \
--to=maillist@jg555.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox