FWIW, you can always kill the processes directly ala "kill 4835 4847" if 
you really need to stop it, but typically this is never necessary.


Gary - I would agree that 'stop' does not work on a debian10 system but 
'start' works fine.   Same problem exists regardless of whether you use the 
init.d file directly or if you use systemctl to let systemd control the 
processes.  Start works.  Stop silently does nothing.  Nothing I could see 
in the logs to indicate that it even tried to shut the processes down. 

   - One other tidbit is that you need to be consistent re: which way you 
   try to control the processes.  On a debian10 system using a dpkg install, 
   bootups will use systemd to run the legacy init.d file start sequence.  If 
   you 'also' manually start via init.d commands using the pre-systemd 
   instructions on the wiki you'll get 'two' sets of processes running, 
   neither knowing the other exists.  But regardless, I can't find an 
   incantation of systemctl or the init.d commands that actually tries to stop 
   the processes.


   - Lastly, if you manually kill the processes then use systemctl to try 
   to (re)start them, it reports failure but it actually worked and the 
   multiple weewx processes indeed run.   Same for init.d - if you kill the 
   processes and run the init.d manually to start, it silently returns (having 
   succeeded) but then if you run ./init.d/weewx status it reports the 
   processes are not running (although they 'are').  Speculate that's 
   something to do with the old pid files init.d files typically use, but I 
   didn't dig further into that.

Bottom line - I think the weewx-multi thing needs some refactoring for the 
systemd world.   Uncertain why exactly a debian10 system uses an init.d 
file for weewx anyway (for a dpkg installation) but it might just be a 
timing thing for when systemd started to take over the world.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/51a992c6-e271-41b9-a4c5-c280c9cc7d10n%40googlegroups.com.

Reply via email to