Re: sr1: CDROM not ready ???
> On Tue, 2004-01-27 at 15:06, Michael D Schleif wrote: >> OK, it can be nice to have devices _know_ when they are ready to be >> used ;> >> >> However, enough is enough: >> >> Jan 27 10:02:09 bragi kernel: sr1: CDROM not ready. Make sure >>there is > a disc in the drive. >>Jan 27 10:02:40 bragi last message repeated 31 times >>Jan 27 10:03:41 bragi last message repeated 61 times >>Jan 27 10:04:42 bragi last message repeated 61 times >> >> I know what /dev/sr1 is, and I often play audio CD's in that drive. >> Sometimes, that drive is empty, and that is the way it should be. >> >> How can I figure out what process is pummeling syslog with this >> useless information? >> >> What do you think? > > Install the lsof package if you don't have it. > > Try: lsof /dev/sr1 > > Tt should give you a clue as to what is opening the device, you may > have to run it as lsof -r /dev/sr1 over a minute or more if the process > only opens /dev/sr1 every now and then. It looks to be something > checking once a minute (61 log messages over 61 minutes) Are you > running > something like nautilus? I resolved an identical problem recently. Check out this post from the archives.http://lists.debian.org/debian-user/2004/debian-user-200401/msg05812.html I hope this helps -- Alphonse Ogulla Nairobi, Kenya - University of Nairobi Mail Services "You can't afford to stay offline" http://mail.uonbi.ac.ke/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sr1: CDROM not ready ???
* Michael Heldebrant <[EMAIL PROTECTED]> [2004:01:27:15:25:08-0600] scribed: > On Tue, 2004-01-27 at 15:06, Michael D Schleif wrote: > > OK, it can be nice to have devices _know_ when they are ready to be used > > ;> > > > > However, enough is enough: > > > > Jan 27 10:02:09 bragi kernel: sr1: CDROM not ready. Make sure there is a disc > > in the drive. > >Jan 27 10:02:40 bragi last message repeated 31 times > >Jan 27 10:03:41 bragi last message repeated 61 times > >Jan 27 10:04:42 bragi last message repeated 61 times > > > > I know what /dev/sr1 is, and I often play audio CD's in that drive. > > Sometimes, that drive is empty, and that is the way it should be. > > > > How can I figure out what process is pummeling syslog with this useless > > information? > > > > What do you think? > > Install the lsof package if you don't have it. > > Try: lsof /dev/sr1 > > Tt should give you a clue as to what is opening the device, you may have > to run it as lsof -r /dev/sr1 over a minute or more if the process only > opens /dev/sr1 every now and then. It looks to be something checking > once a minute (61 log messages over 61 minutes) Are you running > something like nautilus? Thank you. # lsof /dev/sr1 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME kscd1336 mds 10r BLK 11,1 163217 /dev/scd1 I got confused, because nothing really said `sr1'. Even ~/.kde/share/config/kscdrc specifies: /dev/cdrom. # ls -l /dev/sr1 lrwxrwxrwx1 root root4 May 25 2002 /dev/sr1 -> scd1 # ls -l /dev/scd1 brw-rw1 root cdrom 11, 1 Nov 30 2000 /dev/scd1 # ls -l /dev/cdrom lrwxrwxrwx1 root root6 Nov 15 18:29 /dev/cdrom -> ./scd1 kscd was sitting in the System Tray, and when I closed it, syslog bombardment also went away ;< I am still confused why the logs and console streaming insisted that the culprit was on /dev/sr1 . . . -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: sr1: CDROM not ready ???
On Tue, 2004-01-27 at 15:06, Michael D Schleif wrote: > OK, it can be nice to have devices _know_ when they are ready to be used > ;> > > However, enough is enough: > >Jan 27 10:02:09 bragi kernel: sr1: CDROM not ready. Make sure there is a disc in > the drive. >Jan 27 10:02:40 bragi last message repeated 31 times >Jan 27 10:03:41 bragi last message repeated 61 times >Jan 27 10:04:42 bragi last message repeated 61 times > > I know what /dev/sr1 is, and I often play audio CD's in that drive. > Sometimes, that drive is empty, and that is the way it should be. > > How can I figure out what process is pummeling syslog with this useless > information? > > What do you think? Install the lsof package if you don't have it. Try: lsof /dev/sr1 Tt should give you a clue as to what is opening the device, you may have to run it as lsof -r /dev/sr1 over a minute or more if the process only opens /dev/sr1 every now and then. It looks to be something checking once a minute (61 log messages over 61 minutes) Are you running something like nautilus? --mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sr1: CDROM not ready ???
OK, it can be nice to have devices _know_ when they are ready to be used ;> However, enough is enough: Jan 27 10:02:09 bragi kernel: sr1: CDROM not ready. Make sure there is a disc in the drive. Jan 27 10:02:40 bragi last message repeated 31 times Jan 27 10:03:41 bragi last message repeated 61 times Jan 27 10:04:42 bragi last message repeated 61 times I know what /dev/sr1 is, and I often play audio CD's in that drive. Sometimes, that drive is empty, and that is the way it should be. How can I figure out what process is pummeling syslog with this useless information? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
sr1: CDROM not ready ???
OK, it can be nice to have devices _know_ when they are ready to be used ;> However, enough is enough: Jan 27 10:02:09 bragi kernel: sr1: CDROM not ready. Make sure there is a disc in the drive. Jan 27 10:02:40 bragi last message repeated 31 times Jan 27 10:03:41 bragi last message repeated 61 times Jan 27 10:04:42 bragi last message repeated 61 times I know what /dev/sr1 is, and I often play audio CD's in that drive. Sometimes, that drive is empty, and that is the way it should be. How can I figure out what process is pummeling syslog with this useless information? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
