any advantage of "invoke-rc.d" over "service"??

[Marius Gedminas]

On Thu, Jul 29, 2010 at 02:27:30PM -0400, Robert P. J. Day wrote:
> 
>   i'm reading some new install instructions for a newly-released and
> it suggests to use:
> 
>   $ sudo invoke-rc.d <service name>  ... etc etc ...
> 
>   normally, i'd use the "service" command instead, and i understand
> that "invoke-rc.d" is used *during* the install process when, for some
> reason i don't understand, "service" isn't fully available(?)
> 
>   are those two commands entirely equivalent?  is there any reason
> that normal operation *should* use "service" over "invoke-rc.d"?  just
> curious.

invoke-rc.d is for maintainer scripts; service is for sysadmins.

invoke-rc.d will not start services if they're disabled for a particular
runlevel.  service will always start services.

invoke-rc.d doesn't know anything about upstart jobs.  service handles
both init.d scripts and upstart jobs.

Marius Gedminas
-- 
If "con" is the opposite of "pro", then what is the opposite of progress?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20100729/a807d315/attachment.sig>