From: SysAdmin (postlistsofti.com)
Date: Thu Oct 02 2003 - 01:55:45 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

At 06:03 PM 10/1/2003, William Kimball Jr. wrote:
>Popauth started utilizing about 4% CPU, but jumped quickly to 99.2%. As I
>write this
>message (a few minutes later), the popauth CPU consumption has not
>reduced. It looks like it hangs on activity.

This is a problem. I've never seen this behavior out of popauth...

>On boot, syslogd reported the
>same error message, STILL unable to find the fifo file that is clearly
>available (I double checked again). I believe it
>is important to figure out why syslog can't find a file that does indeed
>exist where specified. I don't know if it's
>important, but the man page on chmod has no documentation for the -p mode
>(it covers u, g, o coupled only with d, r, w,
>and/or x) being put on the fifo file. Even though I can successfully set
>the p mode on the fifo file (0600), it is
>undocumented as far as I can tell.

"p" means it's a pipe, you can't set the "d" on a directory either. It's
part of how it's created.

syslogd not recognizing your fifo is another problem - probably the
biggest... I don't know why...

>Also,
>popauth never opens the log file unless I kickstart it with the force
>feed. All I ever get is one line (with varying
>pids):
>
>Oct 01 18:52:10 Starting log for popauth.watcher at pid 1288
>
>Based on the perl source, it looks like this log file should be opened and
>initialized with this line automatically every time popauth is started,
>then updated for every action taken, successful or not. Things aren't
>adding up. Any ideas?

Well, it should put out an authorization and removed entry each time it
does each...

Unless there was something funky that happened to popauth as a result of
going through html, I have no ideas...

>| What Linux version are you running?
>
>RedHat 7.2 (Linux 2.4.7-10).

This EXACT setup (as described in the writeup) was run under 7.2 for
months. In fact, I went over to that system (it's still in the back of the
lab) and verified all the version numbers... syslogd 1.4.1, perl 5.6... it
doesn't really depend on anything else...

Regards,

Mac

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]