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:
The sanlock init script allows use of a /etc/sysconfig/sanlock file to customize startup options. The RPM does not, however, include any such file. It should be installed, showing example config options that can be used, but commented out.

Version-Release number of selected component (if applicable):
sanlock-1.8-2.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. yum install sanlock
2. cat /etc/sysconfig/sanlock
3.
  
Actual results:
No such file

Expected results:
# Add any command line options for the sanlock daemon
# For example, to disable use of the watchdog use '-w 0'
#SANLOCK_OPTS="-w 0"


Additional info:

> #SANLOCK_OPTS="-w 0"

Hah, I even typod in my example - which just goes to demonstrate the value of having an example. The env var name should of course be "SANLOCKOPTS"

Thanks Dan, I pushed out a sample, and will include it in the next build.
I include the "-w 0" example, but refer people to the sanlock man page
for the full list of command line options.

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

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.

This will be fixed in the final 6.3 sanlock rebase.

*** This bug has been marked as a duplicate of bug 782600 ***