Newish to Linux and slowly learning lol. I recently got a podcast downloader working through rss with castget, works great. The command to get new eps that haven’t been downloaded is castget -c.

Is there a way to automate this, so the command runs say every day at a set time?

    • wiener234@feddit.orgEnglish
      9·
      15 hours ago

      Also because I just remembered and it might be relevant to you. If you shut your system down and it is not running at 6am the cron job will not run that day. With systemd-timer it would check if it missed it’s run because the system was powered off and the run after boot the same day.

    • vole@lemmy.worldEnglish
      2·
      15 hours ago

      In line with the advice that running as root would likely not run with the correct file permissions (and would not read the correct config files), you probably want to run castget as your desktop user. Something like sudo -u mydesktopuser -n -- castget -c

      • imminent_nebula@lemmy.caOP
        2·
        14 hours ago

        I see. I’m the only user and the .castgetrc file that I edit for the RSS feeds is located in home. The castget command works in terminal when I type it, but it may not if cron does it? Would that be because cron installs as root? I’m on Cachyos and had to install cronie as cron wasn’t preinstalled. If it doesn’t work I’ll try your suggestion.

        I know -u is for user, what is -n – in this case?

        • vole@lemmy.worldEnglish
          2·
          12 hours ago

          It would be because cron runs as the root user.

          Castget probably looks at the file path $HOME/.castgetrc. For your regular user, $HOME is probably /home/myamazingusername. For the root user, $HOME is probably /root .

          You can get a root terminal session by running sudo -i in a terminal console window. You can try running castget there to see what happens.

          Sudo -n:

          -n, --non-interactive
  Avoid prompting the user for input of any kind.  If a
  password is required for the command to run, sudo, will
  display an error message and exit.

          It’s just a nice thing to put in non-interactive scripts that use sudo. Sometimes you can end up with scripts that just wait endlessly for a password that will never be input because the script is being run non-interactively. The flag probably isn’t needed for a cron job, because root probably can sudo as any user without a password, but it doesn’t hurt either.

          EDIT: I didn’t know that there are user crontab entries as well. If you just used crontab -e without using sudo, then you don’t need to worry about the job being run as root.

          • imminent_nebula@lemmy.caOP
            1·
            6 hours ago

            This was really interesting, thanks. Something I’ll keep in mind for sure, but I did set it up with crontab -e so maybe I’m all good. Gonna play around with it some more over the next few days, there’s so much to learn. Linux is amazing

        • Sophienomenal@lemmy.blahaj.zoneEnglish
          1·
          12 hours ago

          If you ever have a question about what a specific flag does for a command, type man [insert command here] and RTFM (respectfully, of course). If you need a shorthand that’s less verbose, most commands have a --help or -h flag that prints out a quick overview of how to use the command and what the flags do.

    • GooeyGlob@lemmy.worldEnglish
      1·
      15 hours ago

      One thing is you should not make assumptions about the path in cron. If it’s in anywhere than /usr/bin, I would specify the path of the script/binary. Otherwise it looks great.

      • imminent_nebula@lemmy.caOP
        2·
        15 hours ago

        I’ll keep that in mind thanks. Haven’t dipped my toes into scripts and things yet but this just opened up a world of possibilities lol