Timeline for How to clone a read-only portion of /proc file system
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2024 at 2:20 | answer | added | Jack G | timeline score: 0 | |
| Apr 30, 2013 at 6:50 | comment | added | Nils |
So you should catch the exception. I looked into some mount-options (mount --make-private) that looked as if you could do a snapshot of a FS-mount, but this does not seem to work.
|
|
| Apr 29, 2013 at 17:04 | comment | added | Leonid |
@Nils, A) Because I want to minimize the window during which I interact with the /proc file system, B) Initially I was using a nice high-level library for Python called procfs. I would prefer to use that library, except hack it to point to a new root.
|
|
| Apr 29, 2013 at 13:45 | comment | added | Nils | I understand the problem. But why can't you catch the exception where the file being read is gone (and terminate whatever you wanted to do there)? | |
| Apr 28, 2013 at 16:41 | comment | added | Leonid |
@vonbrand, I believe I stated what I want to do. Say I want to copy reliably and fast all of the /proc/*/cmdline and all of the /proc/*/statm and /proc/*/status files. Can you suggest a tool/script that can do that for me?
|
|
| Apr 27, 2013 at 1:07 | answer | added | Runium | timeline score: 4 | |
| Apr 27, 2013 at 0:08 | history | tweeted | twitter.com/#!/StackUnix/status/327937336027512833 | ||
| Apr 26, 2013 at 23:57 | comment | added | vonbrand | What exactly do you want to do? Copying a complete process will take a lot of time... | |
| Apr 26, 2013 at 23:29 | history | asked | Leonid | CC BY-SA 3.0 |