Imagine you want to launch 1000 long standing processes as oneshots.

Nohup to a file would be a better usage than a screen multiplixier

Why:

• Because you can do a for loop over the nohup files to grep status and collate stats for the 1000 processes.
• Because tmux/screen is easy to mentally manage but near impossible to navigate in list view or other

"But you can extract a snapshot of your 1000 tmux windows to file and grep that for status!"

Yes, great, but it's not a neat solution, and tmux/screen snapshots might not capture everything due to window rendering artefacts.

"We should improve safe coding standards somewhat." - "And yet you participate in software engineering..."

Screen should work with no problem. You just start the screen session, detatch when you want, reattach later. No problem.

How dare people post facts about modern tools in a tech oriented community!? So sick of it!

Cool, that's fine. I think it was clear I didn't mean literally everyone. At least for me the boosterism has been pretty relentless for many years, taking over from the Python dogmatism before that.

The languages are cool and have many nice aspects, the volunteer advertising is tiresome though.

Like many have already said, your probably just looking for a terminal multiplexer. Things like screen or zellij, which to my knowledge also don't require any kind of "server". You start a process and the tool provides means to reattach to the still running sessions.

Any session gets a name, which is what you can use to reattach to a specific one, or you can just "attach" if there isb only one available.

Idk, I find it pretty informative.

Is that postmarket OS?

I’m sorry, I must have not said this loud enough. JUST KEEP USING COREUTILS.

hassle of needing a tmux server running

What do you mean? What hassle??

I'm not. Keep going @TheTechnician27@lemmy.world

Unless I'm an ubuntu user?

This is a very confusing question. What is the concern about this file, and what do you mean about "reattach"? Is it a long running process? Why would locking thw file, or working in memory of tmp not work? Why is screen not an option?

I think the tool "dtach" might fit the bill.

It's supposed to be a lightweight replacement for tmux/screen that only does the detach/reattach parts, and none of the terminal emulation stuff or windowing or any of that.

As for the 25% slop figure, it is an estimate from 111 respondents, not a measured count.

Important detail... The headline is borderline misleading, that's not what en estimation is, that's an anecdote at best.

https://github.com/nelhage/reptyr

https://github.com/jerome-pouiller/reredirect

https://github.com/trishume/telefork

https://pasky.or.cz/dev/retty/

I googled it for you and found this: https://serverfault.com/questions/24425/can-i-nohup-screen-an-already-started-process

It doesn't create a file, but you don't need one. Read all the answers for options on reattaching. I haven't used it, so I can't vouch for any of them. (Personally I just use byobu and have it start with each shell, so I'm always running tmux.)

I don't think there's any system that can reliably freeze a single process to disk. Usually that's implemented by the program itself.

I use "screen" which i guess is similar to tmux, if that's of any help.

Not sure about downclocking. The battery is only 1 year old FWIW, I got a replacement from HP for a faulty battery last year.

the use-case is to simply re-attach to a long-running process, I'm not too concerned about a session persisting across reboots, though that would clearly be amazing

I essentially want tmux, without the hassle of needing a tmux server running in the background.

I want the convenience of nohup, with the ability to attach to the nohup file of a running process and recover the running session.

Not sure what you want. You're trying to monitor that process so you can tell when it finishes? You want to know when the file is closed? You can do that with inotify(2).

The tool is "screen" but it isn't going to a file per se, just a session name. Edit: I guess tmux does the same. What do you see as the difference? Are you trying to also suspend execution so you can reboot?

Is it supported on that system? Would downclocking the CPU be a useful alternative?

Is replacing the battery cost-prohibitive?

Makes me wonder what brings a guy doing AI codereviews for free... in this economy