How can I write two separate outputs from one command?

IRJ

Service is failing, but timer is not?

stacksofplates

@IRJ said in How can I write two separate outputs from one command?:

@stacksofplates said in How can I write two separate outputs from one command?:
A timer would just be this:
[Unit]
Description=Run Clam Scan

[Timer]
OnCalendar=*-*-* 00:00:00
Unit=scan.service

[Install]
WantedBy=default.target
Do you run systemctl enable clamav.timer and systemclt start clamav.timer instead of doing it with service?

Sorry was in the car, yeah you can do systemctl enable --now clamav.timer and it will do both.

stacksofplates

@IRJ said in How can I write two separate outputs from one command?:

Service is failing, but timer is not?

What's the output of journalctl -u clamav?

IRJ

@stacksofplates said in How can I write two separate outputs from one command?:

@IRJ said in How can I write two separate outputs from one command?:

Service is failing, but timer is not?

What's the output of journalctl -u clamav?

IRJ

What permission is needed on that script @stacksofplates ?

stacksofplates

What's your script look like?

stacksofplates

Oooh are you running from /tmp? Did you mount /tmp with noexec like the stigs want?

IRJ

I ended up moving out of /tmp and the permission issue was fixed. It still failed because I wasnt specifying /bin/bash before script file. Once I changed that it worked.

stacksofplates

@IRJ said in How can I write two separate outputs from one command?:

I ended up moving out of /tmp and the permission issue was fixed. It still failed because I wasnt specifying /bin/bash before script file. Once I changed that it worked.

Ah ok. Did you have #!/bin/bash in the script? I've never had it complain about that before?

IRJ

@stacksofplates said in How can I write two separate outputs from one command?:

@IRJ said in How can I write two separate outputs from one command?:

I ended up moving out of /tmp and the permission issue was fixed. It still failed because I wasnt specifying /bin/bash before script file. Once I changed that it worked.

Ah ok. Did you have #!/bin/bash in the script? I've never had it complain about that before?

Nope lol.