Service Restart after Upgrades - Revision history

320x200: /* Find software that needs to be restarted */

2019-01-23T11:57:42Z

Find software that needs to be restarted

← Older revision		Revision as of 11:57, 23 January 2019
Line 3:		Line 3:
	=== Find software that needs to be restarted ===		=== Find software that needs to be restarted ===

	You can do that with <code>lsof</code> and looking for process that have opened files that are now gone (DEL). They are still in memory (otherwise said process would be quite unhappy), but they changed on disk since the process first opened them. That's a sign ~~it has~~ been most likely updated.		You can do that with <code>lsof</code> and looking for process that have opened files that are now gone (DEL). They are still in memory (otherwise said process would be quite unhappy), but they changed on disk since the process first opened them. That's a sign these files have been most likely updated, and the processes who need them should be restarted to benefit from their latest versions.

	sudo lsof \| grep lib \| grep DEL # verbosy		sudo lsof \| grep lib \| grep DEL # verbosy

320x200: /* Find software that needs to be restarted */

2019-01-23T11:56:43Z

Find software that needs to be restarted

← Older revision		Revision as of 11:56, 23 January 2019
Line 3:		Line 3:
	=== Find software that needs to be restarted ===		=== Find software that needs to be restarted ===

	You can do that with <code>lsof</code> and looking for process that have opened files that are now gone. They are still in memory (otherwise said process would be quite unhappy), but they ~~are not the same as they were~~ on disk since the process first opened. That's a sign it has been most likely updated.		You can do that with <code>lsof</code> and looking for process that have opened files that are now gone (DEL). They are still in memory (otherwise said process would be quite unhappy), but they changed on disk since the process first opened them. That's a sign it has been most likely updated.

	sudo lsof \| grep lib \| grep DEL \| awk '{print $1}' \| sort \| uniq		sudo lsof \| grep lib \| grep DEL # verbosy
			sudo lsof \| grep lib \| grep DEL \| awk '{print $1}' \| sort \| uniq # less verbosy

	=== Restart service ===		=== Restart service ===

320x200: /* Notes */

2019-01-23T11:51:09Z

Notes

← Older revision		Revision as of 11:51, 23 January 2019
Line 15:		Line 15:
	=== Notes ===		=== Notes ===
	* Most things can be restarted without creating havoc, in doubt, RTFM.		* Most things can be restarted without creating havoc, in doubt, RTFM.
	* If needed <code>systemd</code> itself will have been most likely restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>. However whether or not the daemon was restarted does not mean that <code>systemd</code> related processes do not need to be restarted as well (for instance <code>journald</code>) but these are best restarted via <code>systemctl</code>.		* If needed <code>systemd</code> itself will have been most likely restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>. However whether or not the daemon was restarted does not mean that <code>systemd</code> related processes do not need to be restarted as well (for instance <code>journald</code>) but these are best restarted via <code>systemctl</code>. Just check the output of <code>lsof</code> to see if any of this applies to your situation.


	[[Category: System]]		[[Category: System]]

320x200: /* Notes */

2019-01-23T11:49:28Z

Notes

← Older revision		Revision as of 11:49, 23 January 2019
Line 15:		Line 15:
	=== Notes ===		=== Notes ===
	* Most things can be restarted without creating havoc, in doubt, RTFM.		* Most things can be restarted without creating havoc, in doubt, RTFM.
	* If needed <code>systemd</code> itself will have been most likely restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>. However whether or not the daemon was restarted does not mean that <code>systemd</code> related processes do not need to be restarted as well (for instance <code>journald<code>) but these are best restarted via <code>systemctl</code>.		* If needed <code>systemd</code> itself will have been most likely restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>. However whether or not the daemon was restarted does not mean that <code>systemd</code> related processes do not need to be restarted as well (for instance <code>journald</code>) but these are best restarted via <code>systemctl</code>.


	[[Category: System]]		[[Category: System]]

320x200: /* Notes */

2019-01-23T11:49:18Z

Notes

← Older revision		Revision as of 11:49, 23 January 2019
Line 15:		Line 15:
	=== Notes ===		=== Notes ===
	* Most things can be restarted without creating havoc, in doubt, RTFM.		* Most things can be restarted without creating havoc, in doubt, RTFM.
	* ~~<code>systemd</code> related processes are best restarted via <code>systemctl</code> and~~ <code>systemd</code> itself will have been restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>		* If needed <code>systemd</code> itself will have been most likely restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>. However whether or not the daemon was restarted does not mean that <code>systemd</code> related processes do not need to be restarted as well (for instance <code>journald<code>) but these are best restarted via <code>systemctl</code>.


	[[Category: System]]		[[Category: System]]

320x200: /* Notes */

2019-01-23T11:47:04Z

Notes

← Older revision		Revision as of 11:47, 23 January 2019
Line 15:		Line 15:
	=== Notes ===		=== Notes ===
	* Most things can be restarted without creating havoc, in doubt, RTFM.		* Most things can be restarted without creating havoc, in doubt, RTFM.
	* <code>systemd<code> related processes are best restarted via <code>systemctl<code> and <code>systemd</code> itself will have been restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>		* <code>systemd</code> related processes are best restarted via <code>systemctl</code> and <code>systemd</code> itself will have been restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>


	[[Category: System]]		[[Category: System]]

320x200: /* Restart service */

2019-01-23T11:46:51Z

Restart service

← Older revision		Revision as of 11:46, 23 January 2019
Line 12:		Line 12:

	sudo service whatever restart		sudo service whatever restart

			=== Notes ===
			* Most things can be restarted without creating havoc, in doubt, RTFM.
			* <code>systemd<code> related processes are best restarted via <code>systemctl<code> and <code>systemd</code> itself will have been restarted by post-install package manager hooks/scripts. If you want to force restart the daemon, use <code>sudo systemctl daemon-reexec</code>


	[[Category: System]]		[[Category: System]]

320x200 at 11:38, 23 January 2019

2019-01-23T11:38:34Z

← Older revision		Revision as of 11:38, 23 January 2019
Line 12:		Line 12:

	sudo service whatever restart		sudo service whatever restart

			[[Category: System]]

320x200: Created page with "After updating some software on a '''Linux''' machine, some services making use of this software will be restarted to make use of the new version. But most of the time, no. On..."

2019-01-23T11:37:43Z

Created page with "After updating some software on a '''Linux''' machine, some services making use of this software will be restarted to make use of the new version. But most of the time, no. On..."

New page

After updating some software on a '''Linux''' machine, some services making use of this software will be restarted to make use of the new version. But most of the time, no. One way to refresh it all is to reboot, but unless there is a kernel update you should not need to do such thing.

=== Find software that needs to be restarted ===

You can do that with <code>lsof</code> and looking for process that have opened files that are now gone. They are still in memory (otherwise said process would be quite unhappy), but they are not the same as they were on disk since the process first opened. That's a sign it has been most likely updated.

sudo lsof | grep lib | grep DEL | awk '{print $1}' | sort | uniq

=== Restart service ===

Well, you know... Once you have your list of processes who could do with some refreshing, their name should easily hint at the service you need to restart :)

sudo service whatever restart