Ixnay. Don't do this. In general, changing config files either requires a reboot (brute force... or I should say "boot force" :-) ) or else knowledge of which subsystem to stop and restart (though usually via the "init" command, not the "restart" or "start" command).
If after modifying the config files and rebooting the problem *still* isn't solved, then start scratching your heads. In general, rebooting at least once is a *good* thing to do because it ensures that you made your changes *persistent*, i.e. you didn't modify the ephemeral/temporary copy of some file, only to have it get zapped at the next reboot. -Philip Justin Coffi wrote: > Try creating a symbolic link from /etc/zaptel.conf to > /mnt/kd/zaptel.conf and leave your zaptel.conf on the keydisk. This > should fix things. > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
