Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for silent option when running a job #563

Open
melker opened this issue Aug 11, 2023 · 0 comments
Open

Support for silent option when running a job #563

melker opened this issue Aug 11, 2023 · 0 comments

Comments

@melker
Copy link

melker commented Aug 11, 2023

When starting a heritrix job automatically I want it to be silent when everything works and only output something if it fails.

I start a job (from a cron-job) as specified on https://heritrix.readthedocs.io/en/latest/operating.html#running-heritrix
.../heritrix/bin/heritrix -a someuser:somepassword -p portnumber -r jobname

It outputs the stuff below:
tue jul 4 04:01:01 CEST 2023 Heritrix starting (pid 46328).......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
...
and maybe some more line at the end

I would like a "-q" option or something to NOT get the output at all when it works

PS:
I checked at logging options but I did not find anything useful for this.

PPS:
I tried using "> /dev/null" (or to some file) but it is not that good as error messages are hidden too. For example if starting with a non existing job name. I think the error should have been written to stderr instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants