From: "Jim Gifford" <maillist@jg555.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Strange udev problem - More Detail of the problem
Date: Sun, 20 Jun 2004 08:55:40 +0000 [thread overview]
Message-ID: <0a7101c456aa$1a7f0ea0$d100a8c0@W2RZ8L4S02> (raw)
The fcron developer gave me a patch, but it didn't work. Which he made
figuring it was a umask issue, but the patch didn't work. Patch is available
for viewing at http://ftp.jg555.com/patches/fcron/fcron-2.9.4-udev-1.patch
After talking to a few people and doing some testing I can describe the
problem a lot better now.
(root@server)-(10:50 PM Sat Jun 19)-(/tmp)
# ls -lc /dev/null
crw------- 1 root root 1, 3 2004-06-19 22:49 /dev/null
(root@server)-(10:50 PM Sat Jun 19)-(/tmp)
# cat /var/log/fcron.log | grep 22:49
Jun 19 22:49:20 server fcron[15999]: Job
/etc/firewall/blacklist --current-only started for user root (pid 16000)
(root@server)-(10:51 PM Sat Jun 19)-(/tmp)
#
In the complete file it shows the rest of blacklist update script running.
The script in question is posted at
http://svn.jg555.com/viewcvs.cgi/trunk/blacklist?rev=2&view=markup . Which I
wrote
I enabled udev debugging, and nothing showed up
I run the script without using fron, no problem.
Checked all my logs for events at the same time, nothing except for this
script and fcron.
Which also leaves udev as a potential cause.
I can set this script to 1 minute, and it will cause this issue every time.
-------------------------------------------------------
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-20 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 8:55 Jim Gifford [this message]
2004-06-20 14:21 ` Strange udev problem - More Detail of the problem Kevin P. Fleming
2004-06-20 16:23 ` Jim Gifford
2004-06-20 16:40 ` Kay Sievers
2004-06-20 20:30 ` 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='0a7101c456aa$1a7f0ea0$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