You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in terminal window, it works fine, with or without the full path to ebusctl.
If I put the same thing in a cronjob, it does't work anymore, with or without full path.
This holds also when this line is used in a script file that is called by cron.
After trying a lot, I found out that the problem is specifically linked to the -f option, and also to the -m option.
Other options like -v or -n are working perfectly, both in cron , script files called by cron, and on command line, even with several options combined.
Apparently, some kind of process that does the forced read from the bus is not starting from within cron.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello all,
I have a weird problem: when I do
in terminal window, it works fine, with or without the full path to ebusctl.
If I put the same thing in a cronjob, it does't work anymore, with or without full path.
This holds also when this line is used in a script file that is called by cron.
After trying a lot, I found out that the problem is specifically linked to the -f option, and also to the -m option.
Other options like -v or -n are working perfectly, both in cron , script files called by cron, and on command line, even with several options combined.
Apparently, some kind of process that does the forced read from the bus is not starting from within cron.
Anybody has an idea for a workaround ?
Beste regards, Marc
Beta Was this translation helpful? Give feedback.
All reactions