daemontools tak otomatis start di fedora 12

April 12, 2010 by gregor · Leave a Comment
Filed under: Qmail, djbdns 

Biasanya setelah selesai instal daemontools, svscan akan segera aktif dan ditambahkan baris berikut pada /etc/inittab:

SV:123456:respawn:/command/svscanboot

sehingga setiap kali server reboot, daemontools langsung aktif untuk menjalankan program-program di direktori /service. Cara sederhana untuk mengetahui apakah daemontools sudah terinstal dengan baik adalah dengan memberikan perintah

$ ps aux

jika terlihat baris seperti berikut berarti daemontools sudah terinstal dengan baik dan aktif:

root 1075  0.0  0.0 1896 360 ? S 14:10 0:00 svscan /service
root 1076  0.0  0.0 1724 280 ? S 14:10 0:00 readproctitle service errors: ..

Namun ternyata pada fedora core 12 hal ini tidak berlaku. karena sejak fedora core 9 sudah tidak lagi digunakan init namun upstart. sebelum fc 9, untuk menjalankan program secara otomatis pada saat komputer booting digunakan konfigurasi pada /etc/inittab namun sekarang menjadi /etc/event.d. Agar daemontools dapat aktif pada saat komputer booting di fc 12 buatlah file /etc/event.d/daemontools dengan editor vi yang berisi :

# daemontools
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on shutdown
respawn
exec /command/svscanboot

simpan dan keluar dari vi lalu berikan perintah :

$ initctl start daemontools

Tags: , ,

djbdns:put tinydns and dnscache on the same ip

August 1, 2008 by gregorgede · Leave a Comment
Filed under: djbdns 

one good thing that makes djbdns secure is the separation of dns-resolver (dnscache) and dns-server (tinydns).
but sometimes we want them to run on the same ip, for example when we set it up for internal use in our LAN.

a few tips to do so:

1. when configuring tinydns, make it listens on 127.0.0.1

$ tinydns-conf tinydns dnslog /etc/tinydns 127.0.0.1
$ ln -s /etc/tinydns /service

2. when configuring dnscache, make it listens on ip that you will tell all computers in your LAN to use it as the DNS server (eg. 192.168.10.2)

$ dnscache-conf dnscache dnslog /etc/dnscachex 192.168.10.2
$ ln -s /etc/dncachex /service

3. all computers in your LAN will ask dnscache on 192.168.10.2 to resolve a domain name. dnscache will then figure it out.
supposed that your tinydns is serving any domain ended with intra.net and all servers are in 192.168.1.* then you need to tell dnscache to ask tinydns for it:

$ echo “127.0.0.1″ > /etc/dnscachex/root/servers/intra.net
$ echo “127.0.0.1″ > /etc/dnscachex/root/servers/1.168.192.in-addr.arpa
$ svc -t /service/dnscachex

now dnscache will ask tinydns for any domain that ended with intra.net

Tags:

tinydns: fatal: unable to bind UDP socket: address not available

February 26, 2008 by gregorgede · 1 Comment
Filed under: djbdns 

if your tinydns service stop working and you find ” tinydns: fatal: unable to bind UDP socket: address not available” line in the log file, you will probably should do this :

1. $ /sbin/ifconfig or $ /sbin/ip addr
2. $ cat /service/tinydns/env/IP

make sure that result from number 2 is the same as the result from number 1.

Tags: