Bug 704960 - init scripts of obsworker and obsscheduler use killall causing nasty side effects
Summary: init scripts of obsworker and obsscheduler use killall causing nasty side eff...
Status: CONFIRMED
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Adrian Schröter
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-11 16:13 UTC by Justus Winter
Modified: 2011-07-14 08:31 UTC (History)
0 users

See Also:
Found By: Third Party Developer/Partner
Services Priority:
Business Priority:
Blocker: No
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justus Winter 2011-07-11 16:13:15 UTC
The init scripts of both obsworker and obsscheduler use killall to kill any worker and scheduler processes. This prevents our build server (which uses chroots instead of a vm) from building the obsworker image using kiwi since all bs_worker processes are killed as soon as the obsworkers postinstallation script calls /etc/init.d/obsworker try-restart.

Looking at egrep '(pkill|killall|pidof|pgrep)' /etc/init.d/* suggests that most init scripts use other means to identify old processes (like pid files).

Justus