Hi Saul, Yes, I can create a Storyboard for that. -Matt On 2019-06-19, 5:02 PM, "Saul Wold" <sgw@linux.intel.com> wrote: On 6/19/19 1:26 PM, Peters, Matt wrote: > +1 > > Maybe this is out of scope, but I nice stretch objective would to also move away from having Service Management (SM) use OCF scripts for some of these services. We currently have 2 methods of launching services, one during the bootstrap that uses systemd, and then another that is managed by SM that invokes OCF scripts. SM is fully capable of managing services through systemd (and does for some), so converting these remaining ones would also cleanup the process management. > Matt, Would you be willing to create a Storyboard and tasks for the scripts / packages that need to be converted from OCF to systemd units? Thanks Sau! > -Matt > > > On 2019-06-19, 1:30 PM, "Saul Wold" <sgw@linux.intel.com> wrote: > > > Hi Folks, > > One of the things that the Multi-OS work has shown is that a number of > the flock packages that use a hybrid of systemd and sysvinit. This means > that the sysvini scripts are called by systemd unit files. OBS and > rpmlint called out these as warnings. We will be creating a storyboard > that will list the services that need to be fully converted to systemd > unit files > > This would be a good set of tasks for community members since it will > provide good interactions with the flock source and testing to ensure > the serivces start up correctly. The work is also independent enough > that multiple people or teams can work on each package. There are a > number of resources on the web with information about converting from > sysvinit scripts to systemd unit files. > > This can be a low priority ongoing clean-up type of activity. > > Sau! > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss@lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > >