Back In Time

serviceHelper.py running after cronjob backup finishes

Asked by graysky

Is it normal for the root user to have /usr/bin/python /usr/share/backintime/qt4/serviceHelper.py running after a my non-privileged user runs a backup job from the crontab? This is the case on several systems.

% ps aux | grep python
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 768 0.0 0.3 113912 15772 ? S Feb16 0:00 /usr/bin/python /usr/share/backintime/qt4/serviceHelper.py

Question information

Language:
English Edit question
Status:
Solved
For:
Back In Time Edit question
Assignee:
No assignee Edit question
Solved by:
graysky
Solved:
Last query:
Last reply:
Revision history for this message
Germar (germar) said : 		#1

serviceHelper.py is registered as a DBus SystemBus service. It does get started as soon as DBus is initialised or if it get requested by a DBus sender. For now it's only used to install Udev rules (to start BIT as soon as a drive get connected) on behalf of non-privileged users (after authentication).

I'm already thinking about some kind of timeout so it will close after a while. But I'd rather like to close it as soon as all DBus senders disconnected from this service but didn't find a signal for this yet (http://stackoverflow.com/questions/28238808/dbus-sender-disconnect-signal). I'm still new to the DBus concept.

Revision history for this message
graysky (graysky) said : 		#2

Thanks for the reply. Nothing sinister implied; just curious if you were aware of it. I like your disconnect idea and also the timeout idea.