----- Original Message -----
From: "Angus Lees" <[EMAIL PROTECTED]>
To: "slug" <[EMAIL PROTECTED]>
Sent: Tuesday, April 10, 2001 10:29 AM
Subject: [SLUG] Re: Preventing module from being cleaned
> \begin{Ian Ward}
> > I have VTUN operating between three servers, it works great.
> >
> > It needs the tun.o module loaded. Unfortunately, it does not do this
> > itself.
> >
> > This is fine, as I load the module and kick off vtund in rc.local
> >
> > If there is a prelonged time when there is no tunnel up, the tun.o
module is
> > cleaned out of the kernel.
>
> best is to fix it so it autoloads properly.
>
> if you run vtund without the tun.o module loaded, are there any
> "can't find module xxx" modprobe/kerneld messages in the logs?
Yep your right. This would seem the best approach. I get the following in
the log:
Apr 8 23:01:33 mail vtund[17395]: VTUN server ver 2.4 04/08/2001 (stand)
Apr 8 23:02:11 mail vtund[17397]: Session m2s[61.9.136.175:1129] opened
Apr 8 23:02:11 mail modprobe: modprobe: Can't locate module char-major-90
Apr 8 23:02:11 mail last message repeated 2 times
Apr 8 23:02:11 mail vtund[17397]: Can't allocate tun device. No such file
or directory(2)
Apr 8 23:02:11 mail vtund[17397]: Session m2s closed
So I presume I need to add char-major-90 in with depmod ????? could it be
that I just need to do a depmod -a and reboot (the system has not been
rebooted since compiling and installing the tun package?
Ian
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug