Hello,
This is expected behavior. When an upstart job exists for a service,
which is the case for kdump-tools, the $ service command will execute
(see /usr/sbin/service) :
$ status kdump-tools
On a systemd enabled system (Wily) you would get :
$ service kdump-tools status
● kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor
preset: enabled)
Active: active (exited) since mar. 2016-01-05 09:22:24 CET; 5h 41min ago
Process: 3489 ExecStart=/etc/init.d/kdump-tools start (code=exited,
status=0/SUCCESS)
Main PID: 3489 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 512)
Memory: 0B
CPU: 0
CGroup: /system.slice/kdump-tools.service
So I agree with the last comment : using kdump-config status is the way
to go.
** Changed in: makedumpfile (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528759
Title:
ISST-LTE: kdump service fails to start on Ubuntu14.04.4 lpar.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1528759/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
