Skip to content

Commit

Permalink
[dist] update informations about running services
Browse files Browse the repository at this point in the history
  • Loading branch information
adrianschroeter committed Mar 20, 2012
1 parent 5c94cf7 commit 471c186
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 3 deletions.
5 changes: 4 additions & 1 deletion dist/README.SETUP
Expand Up @@ -244,7 +244,8 @@ as well here.


Afterwards you can start the OBS web api via Afterwards you can start the OBS web api via


rcapache2 start # use "insserv apache2" for permanent start rcapache2 start # use "insserv apache2" for permanent start
rcobsapidelayed start # use "insserv obsapidelayed" for permanent start




4. Setup initial distributions 4. Setup initial distributions
Expand Down Expand Up @@ -391,8 +392,10 @@ To start and stop everything you can use the following command sequences:
rcobsdispatcher start rcobsdispatcher start
rcobspublisher start rcobspublisher start
rcapache2 start rcapache2 start
rcobsapidelayed start


rcapache2 stop rcapache2 stop
rcobsapidelayed stop
rcobspublisher stop rcobspublisher stop
rcobsdispatcher stop rcobsdispatcher stop
rcobsworker stop rcobsworker stop
Expand Down
2 changes: 0 additions & 2 deletions dist/README.UPDATERS
Expand Up @@ -153,9 +153,7 @@ For Updaters from OBS 1.6
To update api and webui informations, you need to start the following processes To update api and webui informations, you need to start the following processes


# insserv obsapidelayed # insserv obsapidelayed
# insserv obswebuidelayed
# rcobsapidelayed start # rcobsapidelayed start
# rcobswebuidelayed start


By default, you should *NOT* start the following services. These are intended By default, you should *NOT* start the following services. These are intended
to autoconfigure services on the OBS Appliance image based on existing LVM to autoconfigure services on the OBS Appliance image based on existing LVM
Expand Down

0 comments on commit 471c186

Please sign in to comment.