[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
http://qa.mandrakesoft.com/show_bug.cgi?id=1661 [EMAIL PROTECTED] changed: What|Removed |Added Version|3.10.5-1mdk |3.10.5-2mdk --- Additional Comments From [EMAIL PROTECTED] 2003-01-07 17:12 --- This bug has been automatically updated to last version of product available. Please check if it is still valid. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: UNCONFIRMED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
http://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-01-07 19:47 --- This bug is still valid. Could someone apply that patch? -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: UNCONFIRMED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #210 is|0 |1 obsolete|| --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 16:57 --- Created an attachment (id=214) --> (https://qa.mandrakesoft.com/attachment.cgi?id=214&action=view) Unconditionally close STDIN OK, well the fix is pretty simple. This patch should be safe. Frederic Lepied, you can apply this to the package. It will be included upstream in the next version. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 06:34 --- /dev/vc/X is the devfs equivalent of /dev/ttyX About that virtual terminal thing. I've never tried, but your assumption sounds reasonable. I went back to -1mdk because I was concerned about disabling DEBUG as well. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 05:20 --- Well I suppose the daemon should be closing STDIN no matter what then. Maybe it's less dangerous if it's not /dev/console? Maybe not? I think /dev/vc/ is just devfs, but I guess tty1 is the non-devfs equivalent. That's a real vc though, what if it's a virtual terminal, like /dev/pts/0 ? Then you see apcupsd holding it open. And what if you close that virtual terminal, then open a new one that ends up at /dev/pts/0 ? You don't see apcupsd holding it open. Hey! Maybe it's because of apcupsd holding stdin open that I can't just Ctrl-D/exit the terminal if I've restarted apcupsd, I have to actually kill the rxvt (terminal emulator window). (to be more precise, I did ssh somewhere to a user account, su to root, restart apcupsd, can exit root shell there, can't exit user shell and return from ssh session) Yeah well anyway enough of my blabbering, the upstream author is working on a fix :o) PS - thanks for pointing this bug out. When it gets fixed upstream I'll make sure it gets fixed in Mandrake. No guarantees that'll be before 9.1 though. I'm not sure whether just disabling the DEBUG is really safe, that was just to test something to make sure we understood why you were seeing the problem, I've asked the author though if disabling it is safe. If so maybe we can do that. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 04:28 --- Here's something you might be interested in. If apcupsd is started at boot, it uses /dev/console. If you start it AFTER boot, it uses the vc you started it on. lsof /dev/vc/1 (or tty1) or whatever vc you started it on should show the nine handles. Hopefully you will see it now. I hate problems that aren't the same for everyone. They're messy. I'll leave reopening of the bug to you if you see what I see with this new information. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 03:29 --- Something I've been suspecting all along, and just now verified, you can only reproduce this if apcupsd was started during the boot process and not restarted afterward. If it's restarted on a running system, you don't get this. This tells me something about the init system is causing apcupsd (as well as gpm, crond, etc) to use /dev/console as its STDIN, and maybe *that* needs to be fixed. What do you think Frederic Lepied? --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 02:19 --- The no debug patch you posted today was all that was needed. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 01:10 --- Ok, the upstream author is going to make sure STDIN gets closed no matter what. BTW, on your fixed version, did you use both patches attached to this bug, or just the one I posted today? Thanks. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Additional Comments From [EMAIL PROTECTED] 2003-02-22 00:10 --- This works. Problem solved. Thank you. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: CLOSED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-21 22:31 --- Created an attachment (id=210) --> (https://qa.mandrakesoft.com/attachment.cgi?id=210&action=view) Don't #define DEBUG, so apcupsd actually *will* close standard filehandles Ok, same procedure as before, I've attached another patch, could you (reporter) try it? --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 20:20 --- Ok, I'll keep looking into it. If anybody else can confirm this, let me know. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 19:34 --- No change. There are still nine of them; three for each process. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 17:02 --- Created an attachment (id=187) --> (https://qa.mandrakesoft.com/attachment.cgi?id=187&action=view) have network information server close standard file handles Save this patch to your RPM SOURCES dir (the following command will tell you where that is: rpm --eval '%_sourcedir' ) Then install the SRPM for apcupsd, and add the patch into the spec file (let me know if you don't know how to do this), and rebuild the RPM and test it, and see if this fixes it. (rpm -bb apcupsd.spec to rebuild) --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 16:53 --- Oh, sorry. Yes, it persists. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 15:40 --- So does the problem persist after restarting apcupsd? --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 05:35 --- I have the random PID grsecurity kernel option enabled. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 04:40 --- That those PIDs from your ps axf listing are not in numeric order in that tree is curious. Try running this command: service apcupsd restart waiting a couple minutes (until you can sucessfully run service apcupsd status), and then trying lsof and see what the deal is. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 04:19 --- $ ps axf | grep apcupsd 30144 ?S 0:00 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf 3627 ?S 0:00 \_ /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf 23942 ?S 0:00 \_ /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf $ grep ^[^#] /etc/apcupsd/apcupsd.conf UPSCABLE940-0024C UPSTYPE smartups DEVICE /dev/tts/0 LOCKFILE/var/lock BATTERYLEVEL5 MINUTES 3 TIMEOUT 0 ANNOY 300 ANNOYDELAY 60 NOLOGON disable KILLDELAY 0 NETSERVER on NISIP 0.0.0.0 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 10 UPSCLASSstandalone UPSMODE disable STATTIME0 STATFILE/var/log/apcupsd.status LOGSTATSoff DATATIME0 SENSITIVITY H WAKEUP 60 SLEEP 020 RETURNCHARGE15 BEEPSTATE N LOWBATT 02 SELFTEST168 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-16 20:20 --- Is anybody else running apcupsd 3.10.5 that can or can't reproduce this? I just don't see how it can be. apcupsd's main() calls daemon_start() which fork()'s, exit()'s the parent, and the child runs: close(STDIN_FILENO); close(STDOUT_FILENO); close(STDERR_FILENO); The network information server starts the same way but doesn't close any fd's though. But then I have it enabled and can't reproduce this. Reporter, can you give me two things. First the output of the following command while apcupsd is running: ps axf | grep apcupsd and the output of: grep ^[^#] /etc/apcupsd/apcupsd.conf --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-16 18:54 --- $ rpm -q apcupsd apcupsd-3.10.5-1mdk $ rpm -V apcupsd S.5T c /etc/apcupsd/apcupsd.conf --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-16 15:40 --- I cannot reproduce this with apcupsd 3.10.5, on Linux or Solaris 9. I can reproduce this with older versions of apcupsd. Give me the output of the following commands: rpm -q apcupsd rpm -V apcupsd --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 --- Additional Comments From [EMAIL PROTECTED] 2003-02-16 02:58 --- very strange. $ lsof /dev/console COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME apcupsd 16721 root0u CHR5,148 /dev/console apcupsd 16721 root1u CHR5,148 /dev/console apcupsd 16721 root2u CHR5,148 /dev/console apcupsd 24278 root0u CHR5,148 /dev/console apcupsd 24278 root1u CHR5,148 /dev/console apcupsd 24278 root2u CHR5,148 /dev/console gpm 24463 root0u CHR5,148 /dev/console apcupsd 28655 root0u CHR5,148 /dev/console apcupsd 28655 root1u CHR5,148 /dev/console apcupsd 28655 root2u CHR5,148 /dev/console --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
[Cooker] [Bug 1661] [apcupsd] apcupsd holds on to /dev/console
https://qa.mandrakesoft.com/show_bug.cgi?id=1661 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|13 |[EMAIL PROTECTED] Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2003-02-15 20:20 --- I don't see this. lsof /dev/console shows only gpm and crond have it open. The apcupsd startup script in this RPM doesn't use the daemon command, but directly executes /sbin/apcupsd, which must detach from stdin on startup. I've not checked the source to confirm this. Another user on the apcupsd mailing lists reports the same on RedHat. __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: please see bug report #1489 same problem. resolution should be the same as well.
