------- Comment From [email protected] 2016-04-13 12:26 EDT------- (In reply to comment #8) > added mon_fsstatd and mon_procd as separate systemd units in a > s390-tools-statd package, one should have an appropriately configured z/VM, > as otherwise the daemons will run, but will fail to write out any monitoring > data.
These services should not be started by default. They serve a very specific scenario, and apart from the correct z/VM guest setup (which you cannot query from inside the guest), you also need someone who will actually read the data that gets written by those service. AFAIR, this was a very specific scenario from one customer, who also had a custom solution for reading/evaluating the data, so it would be useless overhead if enabled by default. For the sake of completeness, here are the setup requirements from http://public.dhe.ibm.com/software/dw/linux390/docu/l4n2dd28.pdf (Chapter 33. Writing z/VM monitor records / Chapter 52. Commands for Linux on z Systems): Setting up the user z/VM guest virtual machine You must enable your z/VM guest virtual machine to write monitor records and configure the z/VM system to collect these records. Procedure Perform these steps: 1. Set this option in the z/VM user directory entry of the virtual machine in which the application that uses this device driver is to run: - OPTION APPLMON 2. Issue the following CP commands to have CP collect the respective types of monitor data: - MONITOR SAMPLE ENABLE APPLDATA ALL - MONITOR EVENT ENABLE APPLDATA ALL You can log in to the z/VM console to issue the CP commands. These commands must be preceded with #CP. Alternatively, you can use the vmcp command for issuing CP commands from your Linux instance. See z/VM CP Commands and Utilities Reference, SC24-6175 for information about the CP MONITOR command. -- 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/+source/s390-tools/+bug/1569454/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
