Tuxstat sometimes tries to use scanf for "\0" string (that is: string with no body at all). Previous versions of glibc cleared all variables in such situations. Glibc 2.3.x correctly keep old value. Unfortunatelly this breaks tuxstst (old char* value is undefined at this point so it tries to scan random region of memeory). Patch is attached (I've sent it few times upstream and was ignored).
Created attachment 40405 [details, diff] Simple fix for glibc 2.3.x Patch is for tux 3.2.14 but can be applied to 3.2.16 as well...
added to 3.2.16-r1, thanks
Oops. Now I've tried to upgrade and got stuck with try to put files outside of sandbox. Investigation showed that .ebuild removes /var/tux directory: -- cut -- rm -rf ${D}/etc/{rc.d,sysconfig} ${D}/var/tux -- cut -- But since this directory is needed for tux I've restored it (mkdir /var/tux) - after that "emerge tux" tries to create some files there while doing make. I've found that change from -- cut -- emake || die -- cut -- to -- cut -- emake TOPDIR=${D} -- cut -- will fix this behaviour. And of course I'd like to have -- cut -- rm -rf ${D}/etc/{rc.d,sysconfig} ${D}/var/tux -- cut -- replaced with -- cut -- rm -rf ${D}/etc/{rc.d,sysconfig} -- cut -- This way you can use tux after first "emerge tux" without manual creation of /var/tux ! P.S. /var/tux should be empty after installation - it's Ok: tux daemon will create files in there but it WILL NOT create directory inself.
Huh. I've mistyped. I've mean -- cut -- emake TOPDIR=${D} || die -- cut -- of course.
