This looks very handy to have around!
Thank you.
Show HN: Witr – Explain why a process is running on your Linux system
71–80 of 108 posts
Re: Show HN: Witr – Explain why a process is running on your Linux system
#72Nice and installed then starred.
Thank you, please feel free to share any feedback/ideas.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#73Great idea!
Thank you.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#74seems handy but mostly the ppid is outputted as the reason for starting. its 'who dun it', not really _why_ it was started. (service file, autorun, execve etc.) i see you support multiple output format including json thats nice. id recommend to assume automation (ssh script/commands) and make the default output really easily greppable , or json (jq) since itll be more appealing to parse (shouldnt reduce readability,…
Thanks for the feedback! I’ll look into showing who and why in a more distinct way.
The default output is human-first, hence some extra line breaks, but the JSON flag is already there for automation. We can also see if it can be made more easily greppable.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#75i definitely see the use for it, lots of moments where i wonder how or why something was started.
Thank you, please feel free to share any feedback/ideas.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#76This is extremely useful, will be added to the toolbox. Thanks for sharing.
Thank you, please feel free to share any feedback/ideas.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#77Earlier quoted context omitted.
> Procfs parsing trivialities are the kind of thing LLMs are good at Have you tried it? Procfs trivialities is exactly the kind of thing where an LLM will hallucinate something plausible-looking. Fixing LLM hallucinations takes more work and time than just reading manpages and writing code yourself.
Claude code can read manpages too
If I'd ever feel the urge to misengineer a rube goldberg contraption to manage my vibe coder LLM output I'll get back to you.
But at the moment I feel like all that sounds suspiciously like actual work.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#78I really like this. Something like this should already exist, stock.
Thanks! Funny enough, that was my thought too when creating it.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#79Earlier quoted context omitted.
If you're capable of auditing the LLM’s outputs and doing a decent code review then you don't need an LLM.
Neither do you need and IDE, syntax highlighting or third party libraries, yet you use all of them. There's nothing wrong for a software engineer about using LLMs as an additional tool in his toolbox. The problem arises when people stops doing software engineering because they believe the LLM is doing the engineering for them.
I don't use IDEs that require more time and effort investment than they save.
You mileage may vary, though. Lots of software engineers love those time and effort tarpits.
Re: Show HN: Witr – Explain why a process is running on your Linux system
#80Earlier quoted context omitted.
The last bit > supervised by a human who occasionally knew what he was doing. seems in jest but I could be wrong. If omitted or flagged as actual sarcasm I would feel a lot better about the project overall. As long as you’re auditing the LLM’s outputs and doing a decent code review I think it’s reasonable to trust this tool during incidents. I’ll admit I did go straight to the end of the readme to look for this exact…
If you're capable of auditing the LLM’s outputs and doing a decent code review then you don't need an LLM.
need and can use are different things.