I've disable ipv6 for sshd daemon.
Each ssh login has triggered an modprobe and generates a WARNING in syslog
--
--- sshd_config.ori 2007-04-16 16:42:10.000000000 +0200
+++ sshd_config 2007-04-16 16:42:21.000000000 +0200
@@ -1,6 +1,7 @@
# Package generated configuration file
# See the sshd(8) manpage for details
+AddressFamily inet
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
--
I monitored module loads with this little shell script ...
/sbin/modprobe.my:
--
#!/bin/sh
{
echo
echo -n "==>"; date
echo
echo params: $@
echo
ps xaufwwww
echo
env
} >>/tmp/modprobe.log
exec modprobe.bin $@
--
mv /sbin/modprobe /sbin/modprobe.real; mv /sbin/modprobe.my /sbin/modprobe
=> and look processtree in /tmp/modprobe.log
=> when finished, do not forget to switsch /sbin/modprobe back ;-)
I've disable ipv6 for sshd daemon.
Each ssh login has triggered an modprobe and generates a WARNING in syslog
--
--- sshd_config.ori 2007-04-16 16:42:10.000000000 +0200
+++ sshd_config 2007-04-16 16:42:21.000000000 +0200
@@ -1,6 +1,7 @@
# Package generated configuration file
# See the sshd(8) manpage for details
+AddressFamily inet protocols sshd will bind to
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/
--
I monitored module loads with this little shell script ... real; mv /sbin/modprobe.my /sbin/modprobe
/sbin/modprobe.my:
--
#!/bin/sh
{
echo
echo -n "==>"; date
echo
echo params: $@
echo
ps xaufwwww
echo
env
} >>/tmp/modprobe.log
exec modprobe.bin $@
--
mv /sbin/modprobe /sbin/modprobe.
=> and look processtree in /tmp/modprobe.log
=> when finished, do not forget to switsch /sbin/modprobe back ;-)
King Regards,
Roland