buildapache.sea HELP!!

[TioChaharbaghi]

Hey all,

currently its running buildapache.sea but it keeps doing this :

Scanning suexec_log.Done
Scanning suexec_log...Done
Scanning suexec_log.Done
Scanning suexec_log...Done
Scanning suexec_log.Done
Scanning suexec_log.Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done
Scanning suexec_log...Done

why does it keep repeatin gitself?

thanks

 

[UpsideOut]

I would also like to know why it repeats this way. Anbody know?

 

[zenpig66]

I don't know exactly why but just offering that I've seen the same and that it will end, from my own experience mind you, after 24 hours or so. This is something new. It appears to be a process called postsuexecinstall that runs for a day after using buildapache.sea(maybe introduced on the April 15 one) to check for suexec problems. If you go to your WHM and check for CPU useage, or, however you like to do it, you should see the command for it listed as well as how many more minutes it has to run. It's ok to cntrl+c the Scanning suexec_log.Done if you are seeing that in a ssh environment but the command will more the likely keep popping back up until your create another ssh session...the command does still run, though, so you aren't killing something that should(?) be continuing. I am curious about the nature of this beast, too