internetarchive / internetarchive/heritrix3
Support for silent option when running a job
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 793
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 8
Description
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.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the `heritrix/bin/heritrix` entry point and the documented command in the operating guide. Reproduce a successful start and a start with a nonexistent job name, then trace where normal output and errors are written. Done means a quiet option suppresses normal output while startup failures remain visible on stderr.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100