>> If the primary goal is to just emit events for other upstart jobs, >> then it would be nice if there is some sort of >> integration between the upstart job and /etc/init.d/openvswitch-switch. >> (I do not know how upstart jobs work very well, so I may need more >> details while you respond.) > > > I included the events because to enable other upstart jobs to be triggered > by/wait for them. They don't seem to have any downside. > > I've looked at the upstart-sysv compatibility guidelines in Debian Policy > 9.11.1 (https://www.debian.org/doc/debian-policy/ch-opersys.html#s-upstart) > and > https://wiki.ubuntu.com/UpstartCompatibleInitScripts. Unfortunately, these > only apply to Saucy, Jessie or later. Following the guidelines with earlier > releases (due to versions of debhelper) produces the issues you noted > previously (/etc/init.d/openvswitch-switch becoming a link, etc). > > Since those releases aren't very old, I'd imagine adding an upstart job file > isn't worth losing compatibility. If someone on-list knows of a workaround, > please let me know. I'll continue to look for one in the mean time.
I haven't read the guidelines yet. If the use case is to emit events, why not add "initctl emit ovs-up" in /etc/init.d/openvswitch-switch ? > > Following the guidelines also involves short-circuiting the sysv init script > with upstart_is_init. This makes it difficult or impossible to use the sysv > init script from the upstart job. Given that, would a v2 patch be welcome > that does duplicate the start function from the sysv init script? > > > Thanks, > -- > Andrew James _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
