Console output for emerge ppp: >>> Emerging (1 of 1) net-dialup/ppp-2.4.4-r24 * ppp-2.4.4.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * ppp-2.4.4-gentoo-20090816.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * ppp-dhcpc.tgz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * CPV: net-dialup/ppp-2.4.4-r24 * REPO: gentoo * USE: amd64 atm dhcp eap-tls elibc_glibc gtk ipv6 kernel_linux mppe-mppc multilib pam radius userland_GNU * The mppe-mppc flag overwrites the pppd native MPPE support with MPPE-MPPC * patch developed by Jan Dubiec. * The resulted pppd will work only with patched kernels with version <= 2.6.14. * You could obtain the kernel patch from MPPE-MPPC homepage: * http://mppe-mppc.alphacron.de/ * CAUTION: MPPC is a U.S. patented algorithm! * Ask yourself if you really need it and, if you do, consult your lawyer first. The end of message is a yellow warnning, with beeps and so one. I had it once in elogv, then, removed it from elogv, and from enotice (I know, it's not supported any more, but, it *works* !!! ). I remerged ppp 4 times; I had 4 times the message in enotice, but, elogv only reported the harmless and useless xLOG: postinst x xPon, poff and plog scripts have been supplied for experienced users. x xUsers needing particular scripts (ssh,rsh,etc.) should check out the x x/usr/share/doc/ppp-2.4.4-r24/scripts directory. I remerged ppp the second time because i had forgotten which symbole was missing to my kernel; enotice told me which symbole i needed to add, elogv does not mind about ewarns. Even if i run elogv BEFORE enotice (to make sure enotice won't cut the grass under elogv). It's because of this kind of bugs i am still using enotice, and refuse moving to elogv. This new attempt is a new proof. To get the ppp message, emerge it with flag mppe-mppc
Created attachment 236963 [details] /tmp/emerge--info
Hi! Is a fix still needed? Please try again with the latest 0.7.6.5, share your PORT_LOG* configuration and a case to reproduce. Right now, I don't really see how to help. Thanks!
