I was hit by the same bug after upgrade to Natty - the original poser's
solution worked (configuring "$Conf{Ping6Path} = '/bin/ping6';".
I totally agree that this should be set by default - there's no reason
for others to waste time trying to figure out why backups aren't working
(there's no clear
I think the original post answers all 3 points above... what exactly is
missing or unclear?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in ubuntu.
https://bugs.launchpad.net/bugs/480927
Title:
karmic upgrade resurrected exi
How about 1.6.0?
--
upgrade to Subversion 1.5.5 for jaunty
https://bugs.launchpad.net/bugs/317564
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settin
I've moved since then to a new setup, now I'm with a new Jaunty machine
(upgraded from a fresh Intrepid installation) on the same LAN as the
original winxp box, plus another xp. I can only note what happens out of
the box now - I don't remember if there were any custom configurations
on the old set
In any case, it should either upgrade to 5.1, or leave 5.0, or ask which
to use, or notify that there's a conflict and explain why. A smooth
upgrade (as far as the user can tell) followed by a broken mysql which
fails to start for no obvious reason (it's not apparent from the logs)
is a bug in the
