From: "Sándor Bárány" <bs@tud.at>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 2.4.13 issue: /dev/null flags reset to 600
Date: Sun, 28 Oct 2001 14:18:37 +0100 [thread overview]
Message-ID: <3BDC05AD.432CCA22@tud.at> (raw)
After upgrading to 2.4.13 I recognised some programs are complaining
about /dev/null.
And yes, /dev/null flags were changed to crw------- , again and again.
It turned out that happens every morning when my cron.daily scripts run.
And more specifically it happens every time when:
1. sensord (version 0.5.0) is restarted (in about one-two seconds after
sensord starts again)
2. syslog-ng (1.5.9) initalizes after boot, is restarted, or get a kill
-1 (the flags change at the next minute when syslog-ng awakes).
I went back to 2.4.9 and was not able to reproduce the same there. Tried
out in 2.4.13 also with and without devfs, it does not matter; however
in the boot sequence with devfs there is (a perhaps unrelated) error in
reparent_to_init
sr1: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray
Adding Swap: 40952k swap-space (priority -2)
Adding Swap: 136512k swap-space (priority -3)
eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
******
task `ifconfig' exit_signal 17 in reparent_to_init
******
Real Time Clock Driver v1.10e
parport0: PC-style at 0x378 [PCSPP(,...)]
I would be glad to supply more debug info - please ask for them
specifically.
Some general system info:
Debian, testing;
Linux version 2.4.13 (root@zsuzsi) (gcc version 2.95.4 20011006 (Debian
prerelease)) #4 Sat Oct 27 17:24:05 CEST 2001
Kernel command line: BOOT_IMAGE=current ro root=307 pci=biosirq
devfs=nomount
Memory: 127124k/131056k available (832k kernel code, 3544k reserved,
212k data, 212k init, 0k highmem)
CPU: AMD-K6(tm) 3D processor stepping 0c
PCI: PCI BIOS revision 2.10 entry at 0xf0560, last bus=1
PCI: Using IRQ router ALI [10b9/1533] at 00:07.0
es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x06
i2c-proc.o version 2.6.1 (20010825)
w83781d.o version 2.6.1 (20010830)
Sándor /* not kernel hacker */
reply other threads:[~2001-10-28 13:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BDC05AD.432CCA22@tud.at \
--to=bs@tud.at \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.