Shell – Does -q definitely turn off wget output logging

linuxshellwget

I currently have a shell script running on a linux server which is using wget in oder to download a remote web page. This in turn is executed by a cron job which is scheduled to run at certain times.

Can someone please confirm that adding in the -q option will not only stop all output being returned to the console, but will also stop all attempts by wget to write to the logs or to try and create a log file?

Best Answer

With -q option, wget itself should not output anything to either console nor the logfile specified by -o option, except for the case described by Michał. The logfile however will be created (if -o was supplied).

This however does not guarantee that no system daemons will notice the fact that wget was run - the network activity can be independently monitored by other tools.

Related Solutions

Bash – wget a file, logging the output and showing the output on prompt

You use the lovely tee command to do this:

wget --no-check-certificate --auth-no-challenge --http-user=$jen_uname --http-password=$jen_psswd 2>&1 | tee -a wget_log

THe 2>&1 means that STDERR goes to the same place as STDOUT, and they're both piped to tee. The -a means append. tee will then send the output both to wget_log and to STDOUT.

Linux – systemd reboot threshold limit

No, systemd doesn't offer a feature to manage a number of reboots and then stop rebooting.

Consider a case where your app fails twice and triggers reboots two via StartActionLimit and remains stable for two weeks, then triggers a third reboot this way much later. Would you expect the theoretical StartLimitReboot=3 to trigger in this case?

If not, there has to be some timeout value to expire the "reboot counter". This is unlike the timer for how fast a service reboots, because the reboot timer would have to factor in how long it takes for the machine to boot before it even tries to start the service again.

Also, if a system is stuck boot-loop due to a critical service failure, does it even make sense to keep machine on if the critical service isn't working, or should it just give up and poweroff after this?

While I can see the interest in having systemd help here, I don't expect this feature to appear to soon.

Best Answer

Related Solutions

Bash – wget a file, logging the output and showing the output on prompt

Linux – systemd reboot threshold limit

Related Question