Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> application bug: crond(1833) has SIGCHLD set to SIG_IGN but calls wait()
Something very strange lately.
I'm using Redhat Advanced Server 2.1
I have managed to do a few things recently.
1)
Upgrade the kernel to: 2.4.20-18.10.1
uname -a
Linux red 2.4.20-18.10.1 #1 Tue Jul 29 13:24:24 PDT 2003 i686 unknown
2)
Finally get the nvidia drivers to work.
3)
Reconfigure the firewire with Oracle OCFS.
Change /etc/modules.conf file, and add:
options sbp2 sbp2_exclusive_login=0
post-install sbp2 insmod sd_mod
post-remove sbp2 rmmod sd_mod
reboot (I know. shutup.)
/usr/local/bin/rescan-scsi-bus.sh
Host adapter 0 (sbp2_0) found.
Scanning for device 0 0 0 0 ...
NEW: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: QUANTUM Model: FIREBALL ST3.2A Rev: A0F. Type: Direct-Access ANSI SCSI revision: 061 new device(s) found.
lsmod
Module Size Used by Tainted: P nls_iso8859-1 3520 1 (autoclean) nls_cp437 5152 1 (autoclean) vfat 12764 1 (autoclean) fat 38072 0 (autoclean) [vfat] ide-cd 37888 0 (autoclean) cdrom 34400 0 (autoclean) [ide-cd] soundcore 6884 0 (autoclean) agpgart 47264 3 (autoclean) nvidia 1768064 11 (autoclean) sd_mod 13564 2 sbp2 20000 1 scsi_mod 119768 2 [sd_mod sbp2] ohci1394 28384 0 (unused) ieee1394 60352 0 [sbp2 ohci1394] autofs 12068 0 (autoclean) (unused) e100 52516 1 appletalk 24300 0 (autoclean) ipx 20692 0 (autoclean) usb-uhci 25828 0 (unused) usbcore 75104 1 [usb-uhci] ext3 69184 9 jbd 48724 9 [ext3]
Host scsi0 : SBP-2 IEEE-1394 (ohci1394) Driver version : $Rev: 906 $ James Goodwin <jamesg_at_filanet.com> Module options : max_speed : S800 max_sectors : 255 serialize_io : no exclusive_login : no Attached devices : [Channel: 00, Id: 00, Lun: 00] Direct-Access QUANTUM FIREBALL ST3.2A
application bug: crond(1708) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: crond(1758) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
scsi singledevice 0 0 0 0
blk: queue f6999414, I/O limit 4095Mb (mask 0xffffffff)
Vendor: QUANTUM Model: FIREBALL ST3.2A Rev: A0F.
Type: Direct-Access ANSI SCSI revision: 06blk: queue f6999614, I/O limit 4095Mb (mask 0xffffffff) Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 6306048 512-byte hdwr sectors (3229 MB) sda: sda1
What are all these bugs in dmesg? Are they anything to be concerned about? How to stop them from occuring?
Thanks Received on Sun Jan 11 2004 - 20:12:32 CST