Please make iperf3(Synocli ) start as service like iperf2 at DSM boot-up
Although I wrote a schedule task to make it run at boot-up, please make it run as default.
Many thanks!
We created to synocli-* packages to provide command line utilities. It is not intended that such packages run any service.
As IMHO iperf* services must run as root, it is not an option to create dedicated packages for iperf2 and iperf3, as DSM >= 7 avoids to run services from thirdpary packages as root,
So the start of such services by a custom task is the only solution anyway
probably we could enhance the diyspk/iperf2/3 packages to run as service, but this would be limited to DSM 6.x, And we do not publish such packages, you woutld have to built it by yourself.
Thanks for you explanation! I am not an IT man. That means I donn't know Synology(DSM) developing policy well.
I also noticed that after the installation of Synocli Monitor Tools, iperf2 is running in background without any manual startup.
I wondering if iperf2 works that way, why can't iperf3.
This moment, I am trying to compile a dedicated iperf3 with the function of "On/Off" under this instruction. Unfortunately, this instruction does not work for iperf3 after appling the codes to iperf3.
Have to turn back to my "schedule task" solution...
@once375ml if iperf2 is running, this is not the one of the synocli-monitor package, as no synocli package starts any service.
Please regard that the synogear package of synology contains iperf and iperf3 for DSM 6 and iperf3 for DSM 7. see our wiki on synogear. Maybe that synogear runs iperf2 upon installation.
@hgy59 I am confused. I newly installed DSM 7.1 on DS118. The synocli-monitor tools is the first and only 3rd party package I installed. Then iperf2 is running in background. I swear I didn't run iperf2 in command line manually and I even don't know Synogear until you told me 10 mins ago
By the way, I checked the process with command Top and Htop, but I couldn't find any iperf2 process. I could only find a process named "iperf3", which was manually started by me. Weird!