Sync approach similar to iproute2.

[marek141017]

Hello

This is not an issue, as long as there is not a discussion here I would like to ask my question in issues thread.

If I understood correctly this crate creates a thread with connection.
I do not understand and was not able to find any explanation - is it really necessary to run a thread?
iproute2 doesn't run in any threads, it pretty great works in "question-answer" mode.

Is there any way to use rtnetlink without threading.
In my application I do not want to have any unnecessary background processes.

Thank you in advance.

[cathay4t]

The connection represent a unix socket to netlink. With connection, you don't need to create new unix socket for follow up communications for performance concern.

The rtnetlink has no threading code, it is up to tokio runtime to choose between single thread or multiple https://docs.rs/tokio/latest/tokio/attr.main.html

If you change the tokio::main to #[tokio::main(flavor = "current_thread")] in examples/get_links.rs, you get single thread rtnetlink. So it is up to user of rtnetlink to decide whether mulit-thread or not.

[cathay4t]

And there is not background threading of rtnetlink unless you spawn, as crate, we do not interference how user run the async code.

[marek141017]

Hello
Thank you for your answer and suggestions.
Currently I use iproute2 directly to get network and routing details and I thought to implement netlink api from rust.
But I check dependencies list and right now I am not ready to compile unnecessary functionality to application with root privileges.
I may dig dipper in netlink-sys sources to extract code which my app will use, but I am not sure will it be better than use iproute2.

Regards.