On Fri, Dec 18, 2020 at 07:27:08PM -0300, Marco Calistri wrote:
Il 18/12/20 16:40, Brian Reichert ha scritto:
Below is the signature generated by script I add into the cron job: Try running your script with s cleared environment and a new non-login shell:
env - /bin/sh /etc/cron.hourly/myjob
Marco@linux-turion64:~> env - /bin/sh /etc/cron.hourly/sig-os-release
Unable to init server: Could not connect: Connection refused
I did not retain a copy of your original script. Clearly, though, your script relies on some pre-established aspect of your environment. Cron's default path is, I think, '/usr/bin:/bin'. You can test-fire a script with a similar environment, e.g.: $ env - PATH=/usr/bin:/bin /usr/bin/printenv PATH=/usr/bin:/bin So, instead try your script like this: env - PATH=/usr/bin:/bin /bin/sh /etc/cron.hourly/sig-os-release
-- Marco Calistri Build: openSUSE Tumbleweed 20201216 Kernel: 5.9.14-1-default Desktop:
-- Brian Reichert <reichert@numachi.com> BSD admin/developer at large