Setting service to start on bootup

[n3r0]

Hello

I have recently moved from debian to FC3 because it had support for my wireless card. Anyways, I am by no means an advanced linux user but I was just wondering if someone could help me.

Im trying to get named to start on boot (at the least) and also preferably be able to be sent commands with the 'service' command (service named start)

I uninstalled the built in named that came with my FC3 because my config files are all written for bind 9.3.1 and did not work with that weird DNS chroot business that was on the default install. so i rpm -e 'd all that and compiled named from source.

anyone know how i can get something to automatically generate init.d scripts for this program? can someone post a normal named init script along with the K or S rc.d entries? I never did this manually before but i tried using chkconfig --add /usr/sbin/named on and that didnt work.

The named server runs fine, all i really need to do is pass it

/usr/sbin/named start

when the machine starts. it doesnt need to be more complicated than that but if anyone know where i should put this line ( should i mess with init.d or jsut skip it?? ) let me know please.

[n3r0]

i guess what im looking for is some sort of easy ( little coding if possible ) autoexec.bat

[fsck]

A quick hack would be to stick that start command in /etc/rc.d/rc.local. I've attached /etc/init.d/named (renamed to .txt because this bloody board needs an extension. wtf??) in case you want to do it that way..

[n3r0]

Well thanks i put that in init.d and chmod 755 and now it works sort of.

the thing is it belches out



[root@northstar init.d]# /etc/init.d/named start
Starting named: /bin/chown: `named:named': invalid user
named: user 'named' unknown
[FAILED]
[root@northstar init.d]#


now i dont like creating user accounts willy nilly but if i were to create this account what kind of access should it have? can i just useradd named passwd named?

to me thats a big security risk. maybe ill put it in /etc/rc.d/rc.local then.

[pembo13]

Run the following commands as root:

# cd /etc/init.d
# wget http://pembo13.dalive.com/linux/named.init
# mv named.init named
# chmod +x named
# chkconfig --add named
# chkconfig --level 2345 named on

This assumed that you installed the binaries to the same locations as FC3's package does.

On a side note, chrooting bind seems ot be a highly recommended practice.

[n3r0]

hmm yes it might be better to run in chroot jail. i just want to get everything working right now. will probably set it up there later from

http://www.faqs.org/docs/Linux-HOWTO...IND-HOWTO.html

it doesnt look to hard, but i dont think bind is going to have some crazy security hole in it for a bit

[fsck]

Originally Posted by n3r0

[root@northstar init.d]# /etc/init.d/named start
Starting named: /bin/chown: `named:named': invalid user
named: user 'named' unknown

now i dont like creating user accounts willy nilly but if i were to create this account what kind of access should it have? can i just useradd named passwd named?

It wants to run as user 'named' instead of as root, which is a good thing. create the user/group and lock it. Try and do this even if you use chroot.
There are no known massive holes in bind right now, but not so long ago the thing was swiss cheese. I mean a serious liability. It's much more secure now, though.