Repository navigation
--silent should suppress 'THREAD [...] added to queue' #28
Description
Activity
- Hi Sebastian, Completely agreed. That is a good feature request. Happy to tey and incorporate it soon. Sajeeb…On Tue, 5 Feb. 2019, 8:58 pm Sebastian Neef ***@***.*** wrote: Hi, I run interlace on quite a long list of domains and even with --silent set, interlace will output the following message: [09:53:28] [THREAD] [*REDACTED*] Added to Queue This simply brings the shell's/tmux's load up and wastes CPU cycles, because it has to print this unnecessary information A LOT of times. I believe that interlace would also perform better if those CPU cycles would not be wasted on those print statements. Therefore, I'd suggest to make interlace completely silent if that option is set. Output from the called programs should still be printed, though. Best, Sebastian — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#28>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQNZ0wvK4RU18ai8IoJac-hG25_FqkjKks5vKVW8gaJpZM4ai3cz> .
Metadata
Metadata
Assignees
Labels
No labels
Hi,
I run interlace on quite a long list of domains and even with
--silentset, interlace will output the following message:This simply brings the shell's/tmux's load up and wastes CPU cycles, because it has to print this unnecessary information A LOT of times. I believe that interlace would also perform better if those CPU cycles would not be wasted on those
printstatements.Therefore, I'd suggest to make interlace completely silent if that option is set. Output from the called programs should still be printed, though.
Best,
Sebastian