NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
what is leafp2p?
what is leafp2p running on my system? I understand its somehow related to readynas remote or readynas replicate, neither of which I will ever use. Is leafp2p used for anything else? It ends up cre...
I can report that his problem has been solved in 6.5.0 RC3, leafp2p should not be left running anymore unless Netgear cloud services are being used. That is my experience with RC3 so far.
If you don't use any of the cloud services you could try doing e.g.
# systemctl stop leafp2p
# systemctl disable leafp2p
So that would include ReadyCloud, ReadynasRemote, ReadynasReplicate? Anything else that requires this service running?
I am thinking about messing around with ReadyCloud at some point, but I'm not sure I really need it. I'm assumign that if I decide I want to use those again I would just do the following to renable it again later:
systemctl enable leafp2p systemctl start leafp2p
Yes? where does the actual .service file for leafp2p get stashed?
Yes.
/etc/systemd/system/multi-user.target.wants/leafp2p.service is a symlink back to the service file. When you enable it you will see the location of the service file.
Where /etc/systemd/system/multi-user.target.wants/leafp2p.service does not exist the service won't be automatically started on boot.
The disable/enable commands are for whether to start the service on boot
The stop/start commands are to take actions on the service now, to stop/start it right now.hmm, interesting. I did not disable leafp2p yet or so anything related to it. I can see with ps that its running. However, there is no symlink to it under /etc/systemd/system/multi-user.target.wants. The service file does exist under /lib/systemd/system/, which I have been learning is where those others under multi-user.target.wants are usually sym linked to. I don't know anything about the target.wants thing, what it does or how it works, but as of now, I haven't actually disabled it and its running, but its not sym linked there either.
going to attempt to disable and stop it now. I'll worry about this later if ever need to do cloud stuff
So I used systemctl to stop and disable leafp2p. It did indeed stop the process. However on the next reboot, there it was again, and reenabled in systemctl somehow.
readynasd must be forcing it back in?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
