Hi Mathieu,
Following my comment #36, now we have finished the work items of dark
blue in the schedule: PMUbuntu starts to be installed with an init
Service/Job script of sysV, upstart, or systemd. As a service/job, the
PM Data Collector daemon will be started from system boot of runlevel
2-5. Please review at your convenience.
# tar tvf ibmpmlinux_3.2.1-1_20160122.tar
-rw-r--r-- root/root 19468 2016-01-22 19:32 ibmpmlinux_3.2.1-1.debian.tar.xz
-rw-r--r-- root/root 536035 2016-01-22 19:32 ibmpmlinux_3.2.1.orig.tar.gz
-rw-r--r-- root/root 401598 2016-01-22 19:32 ibmpmlinux_3.2.1-1_ppc64el.deb
Here I just quote the description regarding this feature from
/opt/ibm/pm/README:
PMLinux SERVICE/JOB
PMLinux started to be installed as a service/job since version 3.2.0-1.
This is to support manipulating PMLinux process with the
common Linux service/job management interface, such as "service PMLinux
{start|stop|status}" etc. Meanwhile, PMLinux process will
be started from the init-rc.d sequence in system booting for every
multi-user run-level, and PMLinux's cron frequency is properly
adjusted from "hourly" to "daily" with this startup method.
New command "initservice.PMLnx" was initiated into PMLinux package for this
purpose. By default, the program probes what methods
(of sysV, systemd or upstart) are available on the system, and follows the
best one to define/enable the service/job control code
for PMLinux application accordingly in one of the following files:
/etc/init.d/PMLinux # sysV varieties
{LSBbase|rc_d|init_d}, all obsolete
/etc/init/PMLinux.conf # upstart, popular for
earlier Debian/Ubuntu releases
/lib/systemd/system/PMLinux.service # systemd, the latest trend
for all recent Linux releases
In general, it is not supposed to run this program manually, unless you
have to select a non-default method, or destruct PMLinux
service/job encapsulation. Moreover, it is not blessed to handle PMLinux
daemon with non-service/PMLinux tools, because that may
mess up the process status inside the service/job utilities. Anyway,
PMLinux certainly remains robust as before no matter how the
control interface is configured and utilized.
Here are some command examples under this topic:
(A) Construct PMLinux service/job # on the check list of
verify.PMLnx (run by command line or installation scripts)
# initservice.PMLnx # create PMLinux init
script with current method, or the best if missing/OFF
Constructing PMLinux service on [IBMpKVM3.1.0.45.0::LSBbase,rc_d,systemd*]
...
Created symlink from
/etc/systemd/system/multi-user.target.wants/PMLinux.service to
/usr/lib/systemd/system/PMLinux.service.
Register PMLinux service/job ... done
SUCCESS! (at /lib/systemd/system/PMLinux.service)
Redirecting to /bin/systemctl start PMLinux.service
(B) Change PMLinux service/job with another method
# initservice.PMLnx -J rc_d # Do (A) with an
old/obsolete method "rc_d" ("systemd" seems better)
Reset PM_INIT_SERVICEJOB=rc_d in /var/perf/pm/config/PMLinux.cfg ... done!
Constructing PMLinux service on [IBMpKVM3.1.0.45.0::LSBbase,rc_d*,systemd]
...
Register PMLinux service/job ... done
SUCCESS! (at /etc/init.d/PMLinux) # rc_d script is based on
the profile /etc/init.d/functions, while
# LSBbase's on
/lib/lsb/init-functions, and so on for init_d ...
Starting PMLinux (via systemctl): [ OK ]
(C) Start PMLinux Service Daemon # similarly, you may use
"stop" or "status" to stop or check PMLinux:
# service PMLinux start # "service" command is
generic for all Linux platforms
# start PMLinux # for Ubuntu/Debian only,
where "start" is a "command" if upstart installed!
# systemctl start PMLinux # specific for systemd, or
# be attentional:
serivce/job status integrity might be broken & you have to:
# service PMLinux restart # restart if PMLinux was
stopped by non-service command "kill"
(D) Deregister PMLinux service/job # just in case of
emergency, like system boot hanging at PMLinux service start
# initservice.PMLnx OFF # disable and remove
PMLinux service/job file if existed
# verify.PMLnx # Must repair PMLinux
integrity after you separately run initservice.PMLnx
** Attachment added: "Enhanced PMLinux tar files and their result from
dpkg-buildpackage"
https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4555165/+files/ibmpmlinux_3.2.1-1_20160122.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448092
Title:
[needs-packaging] ibmpmlinux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
