On Wed, 14 Aug 2019 at 11:01:13 +0200, Simon Becherer wrote:
[...] ok, with systemctl enable nfs_wolfgang.service you should get a output like: Created symlink /etc/systemd/system/multi-user.target.wants/nfs_wolfgang.service â /etc/systemd/system/nfs_wolfgang.service.
if you prefer yast, go to yast and "dienste verwaltung" you should see your service there. and you could show details, switching on and off also possible from there.
or from the commandline: systemctl start nfs_wolfgang systemctl stop nfs_wolfgang systemctl status nfs_wolfgang you say its not working, i am not sure what is not working. try to start and stop manually, and look if working.
here some further hints what i would do if not working: first check if the exec start line will be executed, for this i would do somthing simple: your progam (shellscript?) /home/wolfgang/bin.BGR/nfsclient let it do something you could easily check if its done: (renanme your original file first)
content of "nfsclient": #! /bin/bash cp /home/wolfgang/bin.BGR/nfsclient /home/wolfgang/nfsclient-copy
make it executable (i like to use midnight commander for this)
start it an take a look if this copy was done. if yes, delete the nfsclient-copy
try to start with "systemctl start nfs_wolfgang" take a look if the copy was done. (delte the copyed file after)
now you boot your system and if then the nfsclient-copy was done, you are sure, the problem is not the .service file. then you have to check why your (original) command "/home/wolfgang/bin.BGR/nfsclient" will not work.
if not, the service file has a problem. then i would try to change the line: After=xdm.service to something else (i do not know if xdm.service will work at all), check inside /etc/systemd/ and subdirs the files, what they have inside . if you have firewalld running (you could check inside yast dienstewerwaltung) try like my example. if working then your xdm.service will here not be accepted or will never be started at yours hope this help you. if you (because of my english) not understand me, could mail private in german.
Dear Simon, don't worry about your English. Mine is not better, and that's the reason why we understand each other perfectly. Thanks a lot for all your hints. I don't remember which of them contributed in a crucial way to resolving my problem, but the important thing is that it works now. As you remember, nfs_wolfgang.service starts a script called nfsclient. And this script starts another script. Now I know that this nested start is not allowed for scripts started by a /etc/systemd/system/*.service. So, I changed the structure of my scripts a little bit to avoid the nested start described above, and now IT WORKS! Thanks a lot to you and all others who helped me. Best regards, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org