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:
From winbindd(8) manual page:
NAME
winbindd - Name Service Switch daemon for resolving names from NT
servers
SYNOPSIS
winbindd [-D] [-F] [-S] [-i] [-Y] [-d <debug level>]
[-s <smb config file>] [-n]
...
OPTIONS
...
-Y
Single daemon mode. This means winbindd will run as a single
process (the mode of operation in Samba 2.2). Winbindd´s default
behavior is to launch a child process that is responsible for
updating expired cache entries.
root@localhost:~# winbindd -Y
Invalid option -Y: unknown option
Usage: winbindd [-?SFDinV] [-?|--help] [--usage] [-S|--stdout]
[-F|--foreground] [--no-process-group] [-D|--daemon] [-i|--interactive]
[-n|--no-caching] [-d|--debuglevel DEBUGLEVEL]
[-s|--configfile CONFIGFILE] [-l|--log-basename LOGFILEBASE]
[-V|--version]
root@localhost:~#
Version-Release number of selected component (if applicable):
samba-winbind-3.5.6-86.el6_1.4
Comment 6Guenther Deschner
2011-11-25 15:01:30 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No description necessary
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-2011-1519.html
Description of problem: From winbindd(8) manual page: NAME winbindd - Name Service Switch daemon for resolving names from NT servers SYNOPSIS winbindd [-D] [-F] [-S] [-i] [-Y] [-d <debug level>] [-s <smb config file>] [-n] ... OPTIONS ... -Y Single daemon mode. This means winbindd will run as a single process (the mode of operation in Samba 2.2). Winbindd´s default behavior is to launch a child process that is responsible for updating expired cache entries. root@localhost:~# winbindd -Y Invalid option -Y: unknown option Usage: winbindd [-?SFDinV] [-?|--help] [--usage] [-S|--stdout] [-F|--foreground] [--no-process-group] [-D|--daemon] [-i|--interactive] [-n|--no-caching] [-d|--debuglevel DEBUGLEVEL] [-s|--configfile CONFIGFILE] [-l|--log-basename LOGFILEBASE] [-V|--version] root@localhost:~# Version-Release number of selected component (if applicable): samba-winbind-3.5.6-86.el6_1.4