[EMAIL PROTECTED] wrote: > Hi all, > > In trunk all the init scripts are included into Debian packages with the > --no-start option. I agree that it fixes few issues but do we really want > users > to manually start the daemons (because i guess that at the end they will have > to > do so)? > > Just a question i asked to myself comparing Debian stuff in trunk and in > systemimager-debian...
I would say ok to automatically start systemimager-server-monitord, systemimager-server-rsyncd and maybe systemimager-server-netbootmond (even if NET_BOOT_DEFAULT=net by default in systemimager.conf), but I'm a bit dubious about systemimager-server-flamethrowerd and in particular about systemimager-server-bittorrent: special transports should be enabled only on a explicit request by the user. And, in general, starting systemimager-server-bittorrent at the boot is *bad* idea. BT_UPDATE=y by default in /etc/systemimager/bittorrent.conf; this means that *all* the tarballs and the torrents will be re-created at every reboot of the machine and this is a very time consuming operation. -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
