[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: modprobe
- From: Michael Fratoni <mfratoni tuxfan homeip net>
- To: redhat-list redhat com
- Subject: Re: modprobe
- Date: Mon Dec 30 07:51:31 2002
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 30 December 2002 07:03 am, Ted Gervais wrote:
> On Monday 30 December 2002 02:23 am, Yoink! wrote:
> Yes. The start up of that application can be anywhere but right now I
> have it set up in a script in /etc/init.d and I am able to start/stop
> it using chkconfig etc.. I would like to keep it that way. But a way
> around the problem would be to stick the 'call' for the application, in
> the bottom of the /etc/rc.d/rc.local file. Not very professional, but
> that will fix my problem. However, I would like to stick with the
> script if I can..
Why not put the modprobe call(s) inside the application startup script in
/etc/init.d? Just add the commands to the start() function of the script
that starts the application. If you wanted to get fancy, you could even
rmmod them in the stop() function section of the script. For example,
here is the start() function of crond, with 3 modprobe calls added:
start() {
echo -n $"Starting $prog: "
# let's load some modules!
/sbin/modprobe foo
/sbin/modprobe bar
/sbin/modprobe foo_bar
# end module loading
daemon crond
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/crond
return $RETVAL
}
- --
- -Michael
pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+EEEan/07WoAb/SsRAm5pAKC7xdLe9ewn5HQJ5NHdri3985kphQCfcK8/
Cd3bbf4ouGDXoiOXRRteL+M=
=wvuX
-----END PGP SIGNATURE-----
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]