Lionel Elie Mamane wrote:
On Thu, Jan 19, 2006 at 09:45:32PM +0530, Ganesan Rajagopal wrote:
With manually configured racoon.conf (racoon-tool is deprecated
now), there are is no explicit module loading. All required modules
are automatically dynamically when racoon starts up. I am not sure
why a modprobe is required.
So then why does racoon tool try to explicitly load modules if it will
happen when racoon will be started anyway? What happens is that this
explicit loading fails because insmod doesn't follow dependencies, but
modprobe does.
I have no idea why it does explicit loading. May be some older kernels
had problems automatically loading dependent modules when racoon was
started. The tool was written by the previous maintainer to ease moving
from freeswan to racoon. However, I don't have the time to maintain it
up-to-date with upstream changes to racoon.conf. Frankly, I find
racoon.conf syntax easier to parse.
No, that's fine, I can patch locally. It is only that with so much
time elapsed for a rather serious bug (although misfiled at severity
normal) with a patch ready and no comment, I was fearing that maybe
you were MIA.
Are you sure it's serious bug? In other words, do you actually face a
problem with IPSec because of this rather severe looking error message.
Like I said, using /etc/racoon/racoon.conf, no explicit module loading
takes place and racoon starts up fine.
So I sent a probe, you answered, you are not MIA, I go
back to my cave and let you handle your package. The NMU thing was
mostly for if you didn't answer.
Thanks :-).
Ganesan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
