I’m on EndeavourOs, hyprland wm, cronie as the cron daemon and swww as the wallpaper changer, I’m trying to make a crontab that runs a script to change my wallpaper, if I run it directly on the console or with a python script it works, also it works as a custom module on waybar when clicked, but when I use it as a crontab, it fails to execute, the cronie.service is running, I made some tests with echo into a text file to verify the cron daemon is running and it is, but when I try the script it fails to execute, the output I get from doing a systemctl status cronie.service is:
Oct 16 22:04:01 0bsy crond[76709]: pam_unix(crond:session): session opened for user root(uid=0) by (uid=0)
Oct 16 22:04:01 0bsy crond[76708]: pam_unix(crond:session): session opened for user obsy(uid=1000) by (uid=0)
Oct 16 22:04:01 0bsy CROND[76710]: (root) CMD (python /home/obsy/wall.py)
Oct 16 22:04:01 0bsy CROND[76711]: (obsy) CMD (python ~/wall.py >> /dev/null)
Oct 16 22:04:02 0bsy CROND[76709]: (root) CMDOUT (Error: “Socket file not found. Are you sure the daemon is running?”)
Oct 16 22:04:02 0bsy CROND[76709]: (root) CMDEND (python /home/obsy/wall.py)
Oct 16 22:04:02 0bsy CROND[76709]: pam_unix(crond:session): session closed for user root
Oct 16 22:04:02 0bsy CROND[76708]: (obsy) CMDOUT (Error: “Socket file not found. Are you sure the daemon is running?”)
Oct 16 22:04:02 0bsy CROND[76708]: (obsy) CMDEND (python ~/wall.py >> /dev/null)
Oct 16 22:04:02 0bsy CROND[76708]: pam_unix(crond:session): session closed for user obsy
“The socket file not found” error happens when I try to execute the command swww img /pathtoimage without first initializing the daemon with swww init, but the daemon IS running, cron somehow just doesn’t know about it and when it tries to run my script it fails. I could add a line in my script to initialize the daemon again but I fear that may lead to memory leaks. Is there a way cron can tell the daemons currently running in my machine so I don’t get this error? Thanks!