You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I am currently working on freezing a dbus program using CRIU, but I have encountered some issues with restore it.I would like to be able to restore the DBus program without changing the node of the DBus socket, which is still the same as before。
When I open the dbus program to listen, I can get the PID and the socket node as follows:
Steps to reproduce the issue:
1.The command I had to dump the dbus program was:
And when I do the following code, I change fd[3] to fd[2] to be able to restore,Also the content of the log is that the command I executed below. I see socket node 66434 in fd[3] in the log.:
I was able to get fd[3] and it became something like this: It turns out that the socket is overwritten
And when I do the following code, I change fd[3] to fd[2] to be able to restore and change socket node66434 to 66436:
but a new node was generated, which caused the message to not be able to send information to this dbus program, and the connection could not be generated:
Describe the results you received:
Unable to restore fd[3] with socket[node] stored.
Describe the results you expected:
What I want is to be able to restore the socket node of fd[3] through the following code:sudo criu restore -d -D imgdir -o restore.log -v4 --ext-unix-sk --inherit-fd fd[3]:socket:[44341] , instead of generating a new node for communication connection.
I would appreciate it if you could get back to my question as soon as possible Thanks again!
Description
I am currently working on freezing a dbus program using CRIU, but I have encountered some issues with restore it.I would like to be able to restore the DBus program without changing the node of the DBus socket, which is still the same as before。
When I open the dbus program to listen, I can get the PID and the socket node as follows:
Steps to reproduce the issue:
1.The command I had to dump the dbus program was:
2.After dumping the program was successfully dump, but I had a problem trying to restore,At first I wanted to use this code for restore:
.
But it had an error as shown in the picture:
And when I do the following code, I change fd[3] to fd[2] to be able to restore,Also the content of the log is that the command I executed below. I see socket node 66434 in fd[3] in the log.:
I was able to get fd[3] and it became something like this: It turns out that the socket is overwritten
And when I do the following code, I change fd[3] to fd[2] to be able to restore and change socket node 66434 to 66436:
It produces a new socket node, but that's not the result I wanted.
3.Besides, I used the following code to successfully restore too:
but a new node was generated, which caused the message to not be able to send information to this dbus program, and the connection could not be generated:
Describe the results you received:
Unable to restore fd[3] with socket[node] stored.
Describe the results you expected:
What I want is to be able to restore the socket node of fd[3] through the following code:
sudo criu restore -d -D imgdir -o restore.log -v4 --ext-unix-sk --inherit-fd fd[3]:socket:[44341]
, instead of generating a new node for communication connection.I would appreciate it if you could get back to my question as soon as possible Thanks again!
CRIU logs and information:
CRIU full restore logs:
Output of `criu --version`:
Output of `criu check --all`:
Additional environment details:
The text was updated successfully, but these errors were encountered: