Hi Praedor, On Wed, 30 Jan, at 16:36:14 -0700, Praedor Tempus <[EMAIL PROTECTED]> done said: > > supervise: fatal: unable to start env/run: file does not exist > supervise: fatal: unable to start env/run: file does not exist > supervise: fatal: unable to start env/run: file does not exist > supervise: fatal: unable to start root/run: file does not exist > supervise: fatal: unable to start root/run: file does not exist > supervise: fatal: unable to start root/run: file does not exist
So do a ls on /service/tinydns/run and /service/tinydns/root/run Do those files *really* exist? I've experienced this same problem when my init script calls for something that isn't actually there. If you've got an init script, you might want to review it and make sure it's calling the right things. > This is inspite of following the directions and building and installing > tinydns without problem. I have tried adding: > > search <my domainname> > nameserver 127.0.0.1 > nameserver 155.101.152.159 You're not using that just with tinydns are you? If so, that's not what tinydns's purpose in life is. Hope that helps, -Charlie -- GPG Key fingerprint = 4F36 EC4F 2F2C 5F59 9690 09E5 4C0F 9DB0 8623 53CE
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
