There seam to be a problem with current version of mon-0.38.20-r6.ebuild, after merging it don't want to start because it can't find the Period.pm lib. I tried to remerged it with "# emerge -e mon" but still get same failure on start. ns1 portage # /etc/init.d/mon start * Starting mon... Can't locate Time/Period.pm in @INC (@INC contains: /usr/lib/perl5/5.6.1/i586- linux /usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1/i586- linux /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl .) at /usr/sbin/mon line 50. [ !! ]iled--compilation aborted at /usr/sbin/mon line 50. Btw, current stable version of mon is 0.99.2 and this one from the begining of the centry - time for an update? Unfortunate I (still) lack the competence to ebuild it.
There is an ebuild for mon-0.99.2 in the portage tree now. It's just masked out for testing. Could you please try unmasking it and telling me if it works for you or not? I'll see if I can figure out what's going on, but I may have to recruit someone who actually has a clue about this sort of thing. Taking the bug for the time being.
Looks like mon is missing a dependency on dev-perl/Period. I'll see about fixing it up.
Okay. There are two new ebuilds--mon-0.38.20-r7 and 0.99.2-r1. Both of them add the missing dependency on dev-perl/Period. 0.99.2-r1 is masked out for testing, but you are encouraged to test it out. I tested it with dev-perl/Period installed (which I had to fix, because the current ebuild was incorrect) and it errored out, but it was after the 'Can't locate Time/Period.pm' file, and it was asking for some configuration file that I didn't have. I'm thinking that it'll work okay now. If it doesn't, let me know. I'll keep the bug open for a few days; if I get no reports of nonworkingness, I'll close it out.
I touched /etc/mon/auth.cf and mon started up just fine. That's 0.99.2 instead of the older version, but I have a hunch that they'll both work. Let me know, though.
The new version of mon is unmasked. Please let me know if it works for you. I'll close this bug as RESOLVED FIXED in a few days.
Marking RESOLVED FIXED, as no one seems to be having problems.