[BlueOnyx:25912] Re: odd service names

[Michael Stauber]

Hi Ed,

> Getting the list from systemctl this morning, these two entries look odd:
> 
> *run-r8231c29cfedb4aa6984d35c5d73c52ad.service* loaded failed failed 
>   /usr/bin/systemctl start man-db-cache-update
> *run-r8bd46e5235f941b9af4fa4d7edfc682c.service* loaded failed failed 
>   /usr/bin/systemctl start man-db-cache-update
> 
> Are they the sign of something ominous?


While it looks odd, it appears to be legit. The update service for the 
Linux manpages uses the machine UUID in the name of its "run-" directory:

[root at 5211r ~]# systemctl |grep man
   crond.service                                  loaded  active running 
   Command Scheduler
● run-r3bc0da8cbac9435595ebdb1702e6eab2.service  loaded  failed failed 
  /usr/bin/systemctl start man-db-cache-update
● run-rcf0f1181f7e64973a713722b3406773b.service  loaded  failed failed 
  /usr/bin/systemctl start man-db-cache-update
   systemd-network-generator.service              loaded  active exited 
   Generate network units from Kernel command line
   virtlockd.socket                               loaded  active 
listening Virtual machine lock manager socket
   virtlogd.socket                                loaded  active 
listening Virtual machine log manager socket


> Also, firewalld was not running this morning, yet I know of no reason 
> why it should have been stopped. And ideas?

I've noticed the same on two of my own 5210R and am digging into it now. 
So far I don't have a solid answer to that yet.

-- 
With best regards

Michael Stauber