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.
Cause: missing support for commas in lexical analyser
Consequence: cgconfig failed to parse commas in the cgconfig.conf file
Fix: add support for commas in lexical analyser
Result: cgconfig can parse commas in the cgconfig.conf file
+++ This bug was initially created as a clone of Bug #683541 +++
Description of problem:
cgconfig fails to parse due to commas in the conf file
Version-Release number of selected component (if applicable):
Problem seen in both: libcgroup-0.35.1-3.fc13, libcgroup-0.36.2-5.fc14 and probably other versions as well.
How reproducible:
Always
Steps to Reproduce:
1. Add a line to the config file that uses a comma for the mask.
For example: cpuset.cpus = 1-3,11;
2. Attempt to start cgconfig
3. Fails due to parse error.
Actual results:
cgconfig fails to start
Expected results:
cgconfig starts successfully
Additional info:
adding a \, to the regular expression on line 35 of lex.l in the libcgroup source fixes it.
--- Additional comment from dhaval.bugzilla on 2011-05-24 08:18:41 EDT ---
I believe this was fixed in the upstream sources, and probably an update has been delivered. Can you please confirm if it still exists for you?
--- Additional comment from updates on 2011-05-26 10:04:28 EDT ---
libcgroup-0.36.2-7.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/libcgroup-0.36.2-7.fc14
--- Additional comment from varekova on 2011-05-26 10:06:14 EDT ---
The problem was not fixed in libcgroup-0.36.2-6.fc14 now libcgroup-0.36.2-7.fc14 should fix it.
--- Additional comment from updates on 2011-05-26 17:53:22 EDT ---
Package libcgroup-0.36.2-7.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libcgroup-0.36.2-7.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/libcgroup-0.36.2-7.fc14
then log in and leave karma (feedback).
--- Additional comment from updates on 2011-06-21 13:08:26 EDT ---
libcgroup-0.36.2-7.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
Comment 2RHEL Program Management
2011-11-11 22:28:54 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1685.html