On Sun, 2007-06-03 at 21:48 +0200, Jürgen Hötzel wrote: > On Sun, Jun 03, 2007 at 10:10:38PM +0300, Hussam Al-Tayeb wrote: > > On Sun, 2007-06-03 at 17:08 +0200, Jürgen Hötzel wrote: > > > On Sun, Jun 03, 2007 at 04:40:33PM +0200, Kevin Bader wrote: > > > > Nice script, but I don't think such a script is very useful since the > > > > order of > > > > the daemons array is important. So it's better to use an editor I guess > > > > ;-) > > > > > > > > > > Yes, this script is just appending, which is OK for most services you > > > add. > > > > > > Implementing order should be easy -> this is left to the reader ;) > > > > > > Jürgen > > > > > > _______________________________________________ > > > arch mailing list > > > [email protected] > > > http://archlinux.org/mailman/listinfo/arch > > > > I can do the reordering thing. It's not hard. But I would require a > > default list of how the ordering should be. If anyone can provide a list > > of all the daemons that Archlinux ships and their correct order, I would > > much appreciate this. > > Unlike other distros, Arch Linux doesn't have dependency information > encoded in init scripts. > > I couldn't resist. So I extended my script (inspired by 'chkconfig') do > enable/disable > services and allow ordering: > > Usage: daemons.sh [-b daemon] add|remove|enable|disable daemon [daemon]... > > If you want to add iptables before network: > > daemons.sh -b network add iptables > > If you want to disable iptables > > daemons.sh disable iptables > > Jürgen >
could you do a:
elif cat /etc/rc.conf | grep DAEMONS | grep ${member}
then echo ${member} is already in startup service list.
to check if a daemon is already in rc.conf?
Otherwise it can add a daemon more than once.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
