I tried to understand why two dbus processes are started.
First, I replaced /usr/lib/cups/notifier/dbus with this program:
#include
int main(void)
{
char buf[8192];
while (read(STDIN_FILENO, buf, sizeof buf) > 0) ;
return 0;
}
Then I printed a file, after which
The dbus notifier process stays opened and on subsequent notifications cups-exec
is not done for it. Now it's clear to me that this is done for efficiency.
One thing that still troubles me, though, is that sometimes there are
two and sometimes even three dbus notifier processes in "systemctl
statu
> Most probably the reason is that the process which calls
> the notifier does not close the pipe and the dbus notifier process
> keeps waiting for data to be read instead of getting EOF.
Indeed, strace shows that the dbus notifier process is blocked while
waiting for input from cupsd on stdin:
$
If I copy testnotify (testnotify.c in cups source) over
/usr/lib/cups/notifier/dbus the result is the same.
Package: cups-daemon
Version: 2.3.3op2-3
Severity: normal
X-Debbugs-Cc: igor.lifere...@gmail.com
Dear Maintainer,
After printing a file I get notification that document is sent to printer
and then that printing is finished.
The problem is that dbus notifier process stays alive after having done
5 matches
Mail list logo
