bug#63717: [Shepherd] Replaced services remain active in the shadows

2023-05-29 Thread Ludovic Courtès
Ludovic Courtès skribis: > Ludovic Courtès skribis: > >> What seems to happen is that, in both cases, the registry points to the >> new service; ‘herd status’ & co. look up the service by name in the >> registry, find the new service, and rightfully show that it’s stopped. >> But the old

bug#63717: [Shepherd] Replaced services remain active in the shadows

2023-05-25 Thread Ludovic Courtès
Ludovic Courtès skribis: > What seems to happen is that, in both cases, the registry points to the > new service; ‘herd status’ & co. look up the service by name in the > registry, find the new service, and rightfully show that it’s stopped. > But the old service still exists: it’s no longer in

bug#63717: [Shepherd] Replaced services remain active in the shadows

2023-05-25 Thread Ludovic Courtès
Hello! A bug we noticed with the Shepherd 0.10.0 on berlin: after reconfiguring, which registers a “replacement” for services currently running, restarting said services (with ‘herd restart’ or similar, which is supposed to instate the replacement) happens to leave the old service behind.