"So this means that the original cupsd process misses the signal sent by the daemon process, but the daemon process works correctly." Yes it's so. I forgot to mention that I attached gdb to both running processes (after changing the default cupsd with another one compiled with the debugging switch), and I saw the child (daemon) process sending the SIGUSR1 signal to the correct PID of the parent and then going along normally. The problem is in the parent process that doesn't catch the signal.
-- Cupsys hangs on restart and stop-start https://launchpad.net/bugs/55295 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
