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.
Description of problem:
irqbalance ignores --pid/-s command line argument.
Steps to Reproduce:
1. run irqbalance --pid=/some/path/to/file.pid
2. test -e /some/path/to/file.pid
(In reply to Andrej Manduch from comment #0)
> Description of problem:
>
> irqbalance ignores --pid/-s command line argument.
>
> Steps to Reproduce:
> 1. run irqbalance --pid=/some/path/to/file.pid
> 2. test -e /some/path/to/file.pid
I just reallize I forgot to mention this bug appear only when --debug or --foreground switch is used.
Hi,
using of --debug implies --foreground mode. Pidfile creating is explicitly omitted in foreground codepath since this mode is used for debuging or analyzing purposes and there is no forked daemon in background which should need pidfile lock.
IMHO, this is not bug at all and if you don't have any objections I tend to close this as NOTABUG.
(In reply to Petr Holasek from comment #2)
> Hi,
>
> using of --debug implies --foreground mode. Pidfile creating is explicitly
> omitted in foreground codepath since this mode is used for debuging or
> analyzing purposes and there is no forked daemon in background which should
> need pidfile lock.
>
> IMHO, this is not bug at all and if you don't have any objections I tend to
> close this as NOTABUG.
Hi,
I understand there is not much sence to use --foreground with --pid however I still believe there should at least be mention about it in man page.
(In reply to Andrej Manduch from comment #3)
> (In reply to Petr Holasek from comment #2)
> > Hi,
> >
> > using of --debug implies --foreground mode. Pidfile creating is explicitly
> > omitted in foreground codepath since this mode is used for debuging or
> > analyzing purposes and there is no forked daemon in background which should
> > need pidfile lock.
> >
> > IMHO, this is not bug at all and if you don't have any objections I tend to
> > close this as NOTABUG.
>
> Hi,
>
> I understand there is not much sence to use --foreground with --pid however
> I still believe there should at least be mention about it in man page.
Ok, agreed.
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.
https://rhn.redhat.com/errata/RHBA-2015-2207.html