-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command capture bug in linux_procfs save strategy #449
Comments
Try using set @resurrect-save-command-strategy "linux_procfs" All the available strategies are in I just realized we don't have any docs for this... if you have some time to briefly explain the steps you did to try this, a PR would be welcome. |
I saved again and see now it's the command without args
With that "linux_procfs" outputs, isn't quite right it seems. Can you test what I have below? Would you accept a PR? upsteam:
Proposed:
This 100% did the trick for me locally:
The original command doesn't save the full args. When I did a restore after Note that this will not work:
Some reasoning for this subshell usage can be found here: https://unix.stackexchange.com/a/567021 |
Hi, I'm not on Linux so I can't test this easily. Yes, a PR for this is welcome. |
Just please document why |
submitted #450 |
We just merged #450, so I think this one can be closed. |
For example, run:
Then check ps:
They ideally need to use /proc//cmdline:
Or just one PID:
Output:
This is a valid command:
The text was updated successfully, but these errors were encountered: