Init d updating

During upgrades, if there are no loops in the dependencies declared by LSB headers of all installed init.d scripts and no obsolete init.d scripts, the boot system is converted to dependency based boot sequencing.

The conversion to dependency based boot sequencing is one-way.

This manpage documents only the usage and behaviour of update-rc.d.

From the Jenkins UI console, if we look at the bottom right corner, we’ll see the current version of the Jenkins that we are running: Or, login to the Jenkins server, and use the and execute the following to get the current version from the command line.

The main thing I gleaned from that page was the tone of "If you removed the symlinks in rc?

.d manually, you will have to recreate them manually," and "What went wrong is that you were doing things in there without a sufficient understanding of what should be done." Well, I most definitely didn't remove any symlinks manually.

When we login to Jenkins UI console, and click on “Manage Jenkins” menu item, if we need an upgrade, it will display the following message at the top saying that a new version of Jenkins is available for download: which will upgrade the war file accordingly.

Also, if one has previously installed Jenkins using yum, but yum repository still doesn’t have the latest version of Jenkins, he/she can still go ahead, download the war file and upgrade it manually as explained in this blog post.

Leave a Reply