As I do not have any devices connected yet, I started with some basic things like adding/stopping/starting services. What I noticed when stopping a service ('sv stop xpl-rfxcom' for example), is that it does not stop (See code below). Is this normal behaviour?
Is it by design that a service stop means that the service itself stays in memory, but that it is only put to sleep?
Code: Select all
debian:/# ps -ef | grep xpl
root 2826 2748 0 18:10 ? 00:00:00 runsv xpl-rrd
root 2827 2748 0 18:10 ? 00:00:00 runsv xpl-hub
root 2830 2748 0 18:10 ? 00:00:00 runsv xpl-dawndusk
root 3010 2748 0 18:16 ? 00:00:00 runsv xpl-rfxcom
root 4095 2596 0 18:23 pts/0 00:00:00 grep xpl
debian:/# strace sv down xpl-rfxcom
execve("/usr/bin/sv", ["sv", "down", "xpl-rfxcom"], [/* 17 vars */]) = 0
gettimeofday({1205601894, 435445}, NULL) = 0
open(".", O_RDONLY|O_NONBLOCK) = 3
chdir("/var/service/") = 0
chdir("xpl-rfxcom") = 0
open("supervise/ok", O_WRONLY|O_NONBLOCK) = 4
close(4) = 0
open("supervise/status", O_RDONLY|O_NONBLOCK) = 4
read(4, "@\0\0\0G\334\6o+\361\220\254\216\20\0\0\0u\0\1", 20) = 20
close(4) = 0
open("supervise/control", O_WRONLY|O_NONBLOCK) = 4
write(4, "d", 1) = 1
close(4) = 0
fchdir(3) = 0
_exit(0) = ?
Process 4240 detached
debian:/# ps -ef | grep xpl
root 2826 2748 0 18:10 ? 00:00:00 runsv xpl-rrd
root 2827 2748 0 18:10 ? 00:00:00 runsv xpl-hub
root 2830 2748 0 18:10 ? 00:00:00 runsv xpl-dawndusk
root 3010 2748 0 18:16 ? 00:00:00 runsv xpl-rfxcom
root 4247 2596 0 18:25 pts/0 00:00:00 grep xpl
debian:/#
Als het niet kapot is, niet repareren!