On 12/13/16 15:49, Stephen Davies wrote: > On 13/12/16 16:30, Ed Greshko wrote: >> >> >> On 12/13/16 13:48, Ed Greshko wrote: >>> When you make changes to a file I believe you need to issue the "systemctl >>> daemon-reload". >> >> OK.... Here is the warning I recall reading.... >> >> WARNING >> Always run the systemctl daemon-reload command after creating new unit files or modifying >> existing unit files. Otherwise, the systemctl start or systemctl enable commands could >> fail due to a mismatch between states of systemd and actual service unit files on disk. >> >> See.... >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Managing_Services_with_systemd-Unit_Files.html >> >> >> >> > > > Sorry, but I did that (as I always do; plus it warns you if you don't) but it makes no > difference. > > I have no idea where the reference to /var/spool/clientmqueue/sm-client.pid comes from. > > At one stage I suspected that it might be hard coded somewhere but I can't find that > anywhere. > > Neither can I find where the check for the PID file resides. Well, all I can tell you is that I used the default settings and this is what I get.... [root@meimei run]# pwd /run [root@meimei run]# ls sm* sm-client.pid [root@meimei run]# cd /var/spool/clientmqueue/ [root@meimei clientmqueue]# ll total 0 [root@meimei ~]# uname -r 4.8.13-300.fc25.x86_64 So, something seems very odd about your system when compared to what I'm seeing in my F25 system. -- You're Welcome Zachary Quinto _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
