@kyonshi In my experience it's actually the other way 'round. cron's environment can be terribly undefined or implementation defined. I've debugged things that ran fine when run manually but not at all under cron. systemd timers give you a nice way to run a service and a service has a pretty well-defined execution environment.
@kyonshi That being said, I don't know what specifically it is you want to run, but the dbus session bus is not a systemd concept, that comes from dbus and the XDG runtime dir isn't a systemd concept either, though it does get set by the pam_systemd module on most systems.
Judging from the environment variables, you probably want to run some desktop thing. In that case you will probably want to run this in the systemd user session (via systemctl --user) and, depending on what it is, you might
@lbky that's the problem, it isn't a desktop thing, so I don't know how this even shows up. anyway, I got it to run by installing some package, but now it claims it has permission issues.
so right now I just started it as a daemon and hope I don't forget it the next time I restart the machine
@Theriac well, yeah, that's most likely what I am going to do. it's just frustrating because I already managed to get it running in systemd beforehand.
@kyonshi Then I'm not quite sure I understand why you were asking about timers earlier, since just a service should suffice. Looking at their readme they even have a command to generate a service file
Add comment