22
Delegate a process to a file, for later reattachment? (feddit.uk)
submitted 2 weeks ago by to c/linux@programming.dev
25 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 2 weeks ago* (last edited 2 weeks ago) (9 children)

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?

  • permalink
  • fedilink
  • source
  • hideshow 9 child comments
    •
  • [–] [S] 2 points 2 weeks ago (8 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 2 points 1 week ago* (last edited 1 week ago) (7 children)

    But what's in this file?

    If you're just shuffling data around, use a database.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] [S] -1 points 1 week ago (6 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 1 week ago (5 children)

    You're right. A data ase would be absolutely stupid. Use a log shipping library instead.

    Also, don't A/B me.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 1 point 1 week ago (4 children)

    Don't both require me to know the nature of the data beforehand?

    Please don't B/M on me

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 1 week ago (3 children)
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 1 point 1 week ago (2 children)

    Oh a systemd-logger, I dont have access to the logs, only the admin does. Plus I can't reattach to the process that way

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •