Re: Bug#488578: module-init-tools: modprobe spams syslog heavily
package module-init-tools
reopen 488578
thanks
[Cc: to debian-devel since it seems we could use a third opinion]
Sorry for being an ass and reopening the bug the second time, but I
just think you are wrong about this one.
Some background to d-d:
This bug is about modprobe spamming syslog a hundred times a minute
about a module (ipv6) being not loaded since it's blacklisted. The
warning is actually a Debian-specific modification, in
debian/patches/blacklist-warn.diff. It causes the syslog being spammed
every time an application tries to create an AF_INET6 socket, which
I'd consider quite a valid thing for an application to do.
Of course I might be mistaken and there is a better solution, one that
does not involve modifying or configuring every application,
recompiling the kernel, or doing extreme things like deleting the
module.
Either that or or giving up and de-blacklisting the ipv6 module, which
is big, messy, draws in 10 other modules and does not support
unloading, and modifying a lot of obscure things like
net.ipv6.conf.default.accept_ra just so that I can get to
ftp.fi.debian.org which happens to have an IPv6 address over a network
which doesn't correctly support IPv6 but possibly has some nice rogue
DHCP machine or something that gives me an IPv6 address. And that
can't be done in /etc/sysctl.conf (I tried), my guess is because the
module is not loaded at the time that configuration is applied.
If that is the case, I'd very much like to hear about that solution;
but lacking that solution, getting syslog spammed every time an
application tries to create an inet6 socket just is a bug. I don't
know if it's a bug in modprobe, but I cannot think where it is if not
there.
What's the rationale for warning about trying to load blacklisted
modules anyway? Aren't they blacklisted so they won't load when
something tries to?
On Mon, Jun 30, 2008 at 12:15:15AM +0200, Marco d'Itri wrote:
> On Jun 30, Sami Liedes <sliedes@cc.hut.fi> wrote:
>
> > So the solution you propose is configure every single application (all
> > of which may not be configurable to not open AF_INET6 sockets) because
> > modprobe wants to spam syslog about doing things it's been asked to
> > do?
> Yes. It's not like blacklisting an AFI is a smart idea anyway.
> Since you like stupid workarounds you could as well delete the module.
Perhaps you could tell me why it's so stupid to not want to load that
module.
> > Sorry, I just can't agree with you here, at least not with the
> > rationale you gave.
> Too bad, I am the maintainer.
Perhaps you could reassign it to a more relevant package then?
Sami
Reply to: