Hi John and Will,
Thanks for the responses and help troubleshooting!
It was super simple to specify this to be run as my user account in the service
file. The technique is to add a "User=" line. In case anyone else is
interested, here's what worked. Change the path and username to suit.
Usually jobs that work for some types of logins and fail for others are either
due to differences in file access permission or differences in environment
variables. Maybe when it runs as root, the $PATH variable is different and it
is not finding something. Or some other environment variable is
No, but using flatpak (or any other container system) adds constraints on what
you can do because of the sandbox. Surely you can get systemd to run the job as
you instead of as root.
Regards,
John Ralls
> On Dec 13, 2020, at 10:28 AM, Colin Arndt wrote:
>
> Hi John,
>
> Flatpak access makes
Hi John,
Flatpak access makes sense as the culprit.
The .gnucash file is in my home folder.
The command completes when I run it as my user. Run as root, it fails.
Perhaps I'm trying to do something in a way it's not designed to be used?
Thanks again,
Colin
On Dec 13 2020, at 10:10 am, John Ralls
On Sun, Dec 13, 2020 at 09:57:46AM -0800, Colin Arndt wrote:
> Hi all,
>
> On Fedora Linux here, and I am trying to set up a systemd timer to pull
> price quotes once a week using gnucash-cli. Previously I was using cron
> to accomplish this, but would like to migrate to a systemd timer because
> On Dec 13, 2020, at 9:57 AM, Colin Arndt wrote:
>
> Hi all,
>
> On Fedora Linux here, and I am trying to set up a systemd timer to pull price
> quotes once a week using gnucash-cli. Previously I was using cron to
> accomplish this, but would like to migrate to a systemd timer because
Hi all,
On Fedora Linux here, and I am trying to set up a systemd timer to pull price
quotes once a week using gnucash-cli. Previously I was using cron to accomplish
this, but would like to migrate to a systemd timer because this is on a laptop
and I never know when it will be on or off.
