Ubuntu

Question after enabling concurrent booting

Asked by plutino

After I enable concurrent booting by setting "CONCURRENCY= shell" in /etc/init.d/rc, most services starting messages are printed twice during booting. Does this mean those services are started twice? or are tried twice?

Many thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
plutino
Solved:
Last query:
Last reply:
Revision history for this message
mak (iammak) said : 		#1

what you did will increase the speed of ubuntu
try startpar instead of shell
or try none to be safe.

Revision history for this message
plutino (plutino) said : 		#2

Thanks mak. I'm just wondering if the double message normal or not? Only one of the message showing "OK" at the end, though.

Revision history for this message
mak (iammak) said : 		#3

its not normal but will not penalize you either way
i dont see a reason to set concurrency =shell
anyways its fine as long as it doesnt slow your pc down.
you can check, if double processes are not running, in menu>accessories>system>administration>system monitor
you will find all the processes there.
inspect for duplicacy.

Revision history for this message
plutino (plutino) said : 		#4

Only single instances of the service scripts are running. What's the different between "shell" and "startpar"? All the online information I found leads to setting "CONCURRENCY=shell" and nobody mentioned about "startpar".

Revision history for this message
mak (iammak) said : 		#5

alright
if you dont hav ne prob wid shell thn u cn use it.
wht was originally written in place of shell?

Revision history for this message
plutino (plutino) said : 		#6

the default is none.

I tried to time the startup with bootchart after a fresh installation of Intrepid last night. It seems that in my system, either "shell" or "startpar" shortens the booting time by less than half minutes (within statistical error). So I just changed it back to not using.