Attached is my patch for adding ez-ipupdate. I have not tested it on a real
box with a public IP, but I have run it in my chroot environment on my
laptop with an internal IP, and it was successfully running as a daemon and
updating DynDNS. I did have a little worry because rc-status is indicating
that it is crashed, but I think this is because within the chroot
environment it can't tell the process is still running. I'll have to test
that part on a real box later.
Let me know if you have any feedback on this.
Jeremy Thomerson
On Sat, Aug 22, 2009 at 5:05 AM, Jeremy Thomerson <
jeremy@thomersonfamily.com> wrote:
> Attached is my patch for adding ez-ipupdate. I have not tested it on a
> real box with a public IP, but I have run it in my chroot environment on my
> laptop with an internal IP, and it was successfully running as a daemon and
> updating DynDNS. I did have a little worry because rc-status is indicating
> that it is crashed, but I think this is because within the chroot
> environment it can't tell the process is still running. I'll have to test
> that part on a real box later.
>
> Let me know if you have any feedback on this.
I think the crash report problem comes from that the init.d script tried to
stor the pidfile in /var/run rather than /var/run/ez-ipupdate. It didnt have
permissions to write there and the pidfile was missing. With no pidfile it
reported it as crashed.
I commited the patch and fixed that issue. I have not been able to test it
though.
A tip, I normally just rip the init.d scripts from gentoo. They also use
openrc. But in this case i'm not sure if i prefer your way to do it than
gentoo version of init.d script.
Thanks!
-nc
> Jeremy Thomerson
>
--
Natanael Copa