> That particular item I can't help with, Rick, sorry. I don't have enough > years left in my allotted time here (I'm already 72) to fight with selinux, > so its turned off with the grub option in everything I own. And, while I do > use apcupsd over a usb cable, the cable is plugged into a belkin ups, so > other than querying it for status, its not working that well. Belkins own > nvidia style software (a binary blob) quit working at about 2.6.20-rc2 or so, > becoming a cpu hog I had to kill. I believe, but cannot prove, that some > change to hiddev or to the serial protocol at about that time broke it. Both > serial and usb setups now eat 90+% of the cpu the minute I attempt to extract > any data to the rest of the system, either with their bulldog monitor, or > with the gkrellmBups plugin. > > Now I have a request into Bill to see if he can interface gkrellm with apcupsd > such that I once again have a realtime monitor, but that was a couple of > months ago and I've seen no mention of it via his mailing list. > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > Blessed are the forgetful: for they get the better even of their blunders. > -- Nietzsche > I don't believe it is a problem with SELinux. (In fact, I'm almost 100% certain it is not an SELinux conflict. SEtroubleshoot does not report any problem.) apcuspd works quite well with SELinux on the other system. I'm almost certain the problem is with portsentry - apcuspd works fine under F7 currently without portsentry (it would not work under FC6 with portsentry). I have to tell portsentry to allow the connection with the ups but I could not get it to work under FC6. I haven't started portsentry yet under F7 (given I'm accessing the system remotely). When I get to the system, I will start portsentry (it is set up to allow 127.0.0.1 and 0.0.0.0 which I also tried under FC6 but did not fix the problem) and see what happens. Rick B.
