Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJan Pokorný [poki]
2016-03-07 14:24:22 UTC
# systemctl status pcsd.service
> ● pcsd.service - PCS GUI and remote configuration interface
> Loaded: loaded (/usr/lib/systemd/system/pcsd.service; enabled; vendor preset: disabled)
> Active: active (running) since Mon 2016-03-07 15:02:27 CET; 9min ago
> Main PID: 15743 (pcsd)
> CGroup: /system.slice/pcsd.service
> ├─15743 /bin/sh /usr/lib/pcsd/pcsd start
> ├─15747 /bin/bash -c ulimit -S -c 0 >/dev/null 2>&1 ; /usr/bin/ruby -I/usr/lib/pcsd /usr/lib/pcsd/ssl.rb
> └─15748 /usr/bin/ruby -I/usr/lib/pcsd /usr/lib/pcsd/ssl.rb
> [...]
From the administrator perspective, it's unclear why core dumps are
being disabled without using a native interface of systemctl.exec(5),
notably "LimitCORE=" option. This makes unified management of the system
services harder (or "schizophrenic", if you want, cf. "LimitCORE=" in
service file vs. DAEMON_COREFILE_LIMIT variable in /etc/sysconfig/pcsd).
This is likely just a tip of the iceberg.
# systemctl status pcsd.service > ● pcsd.service - PCS GUI and remote configuration interface > Loaded: loaded (/usr/lib/systemd/system/pcsd.service; enabled; vendor preset: disabled) > Active: active (running) since Mon 2016-03-07 15:02:27 CET; 9min ago > Main PID: 15743 (pcsd) > CGroup: /system.slice/pcsd.service > ├─15743 /bin/sh /usr/lib/pcsd/pcsd start > ├─15747 /bin/bash -c ulimit -S -c 0 >/dev/null 2>&1 ; /usr/bin/ruby -I/usr/lib/pcsd /usr/lib/pcsd/ssl.rb > └─15748 /usr/bin/ruby -I/usr/lib/pcsd /usr/lib/pcsd/ssl.rb > [...] From the administrator perspective, it's unclear why core dumps are being disabled without using a native interface of systemctl.exec(5), notably "LimitCORE=" option. This makes unified management of the system services harder (or "schizophrenic", if you want, cf. "LimitCORE=" in service file vs. DAEMON_COREFILE_LIMIT variable in /etc/sysconfig/pcsd). This is likely just a tip of the iceberg.