------- Comment From michael.holz...@de.ibm.com 2016-04-14 10:34 EDT------- (In reply to comment #14) > @michael > Functionally I don't see how one name would have been better than the other. > Original request was very thin on details, yet set at high priority.
I have to apologize for this if we (IBM) did not provide enough information here. > I have no idea why this is called mon_statd =) especially when (a) mon_statd > does not exist (b) is not provided =) There are two reasons: - We have two daemons in the subpackage that write (stat)istics to the "z/VM (mon_)itor stream" - Historically: For the other distribution we have one System 5 init script that is called "mon_statd". > I can include mon_statd in the description on next package upload, such that > it is searchable by mon_statd term too. At the moment, one can discover this > package with e.g.: > > $ apt-cache search procd > 390-tools-statd - statd monitoring daemons for Linux on z Systems > > $ apt-cache search fsstatd > 390-tools-statd - statd monitoring daemons for Linux on z Systems So "apt-cach search mon_statd" can find the package, sounds good to me. > I don't feel like renaming a package with a -mon- in the name, given that > I've already spend development time to provide systemd units which should > have been shipped by upstream. I have no (real) problem if you want to keep the name. Packaging is your responsibility. My intention is to keep some consistency between the distributions. > Please open a bug report upstream to provide upstream systemd units. Yes, this is our plan :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569454 Title: Provide daemon support via systemd for mon_fsstatd, mon_procd, mon_statd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1569454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
