[EMAIL PROTECTED] wrote: > Hi, > well, why using chkconfig if integrating the mechanism into initctl would > be the cleaner way? chkconfig doesn' t really work clean everytime and > using the necessary headers for it in upstarts service files brings us one > step back to the sysvinit behaviour. > > For me i think, using a clean new way all integrated sounds the best. > > What do the others mean? > >> just add "chkconfig" functionality to upstart, no matter what underlying >> mechanism. > > >
yes, initctl.. and not for the old sysv, but the job files -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
