Is such a think possible under Linux?

Yeah I know I can tmux / nohup, and I know that if I dig deep enough I can manually reattach some of the file descriptors under /proc to get a working terminal for that process again…

… but is there a tool that automatically does this somehow?

e.g.

run -d ./bash long-running.sh  >  proc.file
### later
run -a  proc.file

Edit: Y’all really know how to recreate the feeling of StackOverflow circa 2018

  • just_another_person@lemmy.world
    31·
    3 days ago

    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?

    • tetris11@feddit.ukOPEnglish
      1·
      3 days ago

      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.

        • tetris11@feddit.ukOPEnglish
          12·
          1 day ago

          Log data, current status of a run, timestamp of an error, you name it.

          These are oneshots. Of course you could use a proper workflow system with data provenance and lineage tracking baked in, but during the dev cycle of something new you usually want to play around and gather metrics first without worrying first about the architecture.

          Please don’t X/Y me.