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
[–] 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.

  • 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.

  • 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.

  • 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

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 1 week ago (3 children)
  • [–] [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

  • source
  • parent
  • hideshow 2 child comments