From d55b849d7740aee9795a8ded94d3a2db5b94cc02 Mon Sep 17 00:00:00 2001 From: Tim Potter Date: Fri, 12 May 2000 13:05:26 +0000 Subject: Added signal handling section. (This used to be commit ad5447220032b7f80251e0a5123f7f96b496ffcd) --- docs/htmldocs/winbindd.8.html | 38 +++++++++++++++++++++++++---------- docs/manpages/winbindd.8 | 43 ++++++++++++++++++++++++++++++---------- docs/yodldocs/winbindd.8.yo | 46 +++++++++++++++++++++++++++++++++---------- 3 files changed, 97 insertions(+), 30 deletions(-) (limited to 'docs') diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index 1e6b822d34..d0bdbbfccf 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -169,7 +169,7 @@ the shell for that user.

To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup. This was tested on a RedHat 6.2 Linux box. -

In /etc/nsswitch.conf put the following: +

In /etc/nsswitch.conf put the following: 

 
    passwd:     files winbind
@@ -177,7 +177,7 @@ tested on a RedHat 6.2 Linux box.
-

In /etc/pam.d/* replace the auth lines with something like this: +

In /etc/pam.d/* replace the auth lines with something like this: 

 
 	auth       required	/lib/security/pam_securetty.so
@@ -187,8 +187,8 @@ tested on a RedHat 6.2 Linux box.
-

Note in particular the use of the sufficient keyword and the -use_first_pass keyword. +

Note in particular the use of the sufficient keyword and the +use_first_pass keyword.

Now replace the account lines with this: 

 
@@ -211,10 +211,10 @@ program like this:
-

This assumes your domain is called DOMAIN and your Samba workstation -is called MACHINE. -

Next copy libnss_winbind.so.2 to /lib and pam_winbind.so to -/lib/security. +

This assumes your domain is called DOMAIN and your Samba workstation +is called MACHINE. +

Next copy libnss_winbind.so.2 to /lib and pam_winbind.so to +/lib/security.

Finally, setup a smb.conf containing directives like the following: 

 
@@ -233,11 +233,29 @@ is called MACHINE.
 
 
Now start winbindd and you should find that your user and group
 database is expanded to include your NT users and groups, and that you
-can login to your unix box as a domain user, using the DOMAIN+user
+can login to your unix box as a domain user, using the DOMAIN+user
 syntax for the username. You may wish to use the commands "getent
 passwd" and "getent group" to confirm the correct operation of
 winbindd. 
-
NOTE: nmbd must be running on the local machine for winbindd to work.
+
NOTE: nmbd must be running on the local machine for
+winbindd to work.
+

+
SIGNALS

+    
+
The following signals can be used to manipulate the
+winbindd daemon.
+

+
SIGHUP

+
Reload the smb.conf file and apply any parameter changes to the running
+version of winbindd.  This signal also clears any
+cached user and group information.
+
SIGUSR1

+
The SIGUSR1 signal will cause winbindd to
+write status information to the winbind log file including information
+about the number of user and group ids allocated by
+winbindd.
+
Log files are stored in the filename specified by the log file parameter.
+

 

 
FILES

     
diff --git a/docs/manpages/winbindd.8 b/docs/manpages/winbindd.8
index e35fe0815b..a54f01f781 100644
--- a/docs/manpages/winbindd.8
+++ b/docs/manpages/winbindd.8
@@ -186,7 +186,7 @@ To setup winbindd for user and group lookups plus authentication from
 a domain controller use something like the following setup\&. This was
 tested on a RedHat 6\&.2 Linux box\&.
 .PP 
-In /etc/nsswitch\&.conf put the following:
+In \f(CW/etc/nsswitch\&.conf\fP put the following:
 
 .nf 
  
@@ -198,7 +198,7 @@ In /etc/nsswitch\&.conf put the following:
  
 
 .PP 
-In /etc/pam\&.d/* replace the auth lines with something like this:
+In \f(CW/etc/pam\&.d/*\fP replace the \f(CWauth\fP lines with something like this:
 
 .nf 
  
@@ -212,8 +212,8 @@ In /etc/pam\&.d/* replace the auth lines with something like this:
  
 
 .PP 
-Note in particular the use of the sufficient keyword and the
-use_first_pass keyword\&.
+Note in particular the use of the \f(CWsufficient\fP keyword and the
+\f(CWuse_first_pass\fP keyword\&.
 .PP 
 Now replace the account lines with this:
 
@@ -249,11 +249,11 @@ Then within samedit run the command:
  
 
 .PP 
-This assumes your domain is called DOMAIN and your Samba workstation
-is called MACHINE\&.
+This assumes your domain is called \f(CWDOMAIN\fP and your Samba workstation
+is called \f(CWMACHINE\fP\&.
 .PP 
-Next copy libnss_winbind\&.so\&.2 to /lib and pam_winbind\&.so to
-/lib/security\&.
+Next copy \f(CWlibnss_winbind\&.so\&.2\fP to \f(CW/lib\fP and \f(CWpam_winbind\&.so\fP to
+\f(CW/lib/security\fP\&.
 .PP 
 Finally, setup a smb\&.conf containing directives like the following:
 
@@ -277,12 +277,35 @@ Finally, setup a smb\&.conf containing directives like the following:
 .PP 
 Now start winbindd and you should find that your user and group
 database is expanded to include your NT users and groups, and that you
-can login to your unix box as a domain user, using the DOMAIN+user
+can login to your unix box as a domain user, using the \f(CWDOMAIN+user\fP
 syntax for the username\&. You may wish to use the commands "getent
 passwd" and "getent group" to confirm the correct operation of
 winbindd\&. 
 .PP 
-NOTE: nmbd must be running on the local machine for winbindd to work\&.
+NOTE: \fBnmbd\fP must be running on the local machine for
+\fBwinbindd\fP to work\&.
+.PP 
+.SH "SIGNALS" 
+.PP 
+The following signals can be used to manipulate the
+\fBwinbindd\fP daemon\&.
+.PP 
+.IP 
+.IP "\f(CWSIGHUP\fP" 
+.IP 
+Reload the \f(CWsmb\&.conf\fP file and apply any parameter changes to the running
+version of \fBwinbindd\fP\&.  This signal also clears any
+cached user and group information\&.
+.IP 
+.IP "\f(CWSIGUSR1\fP" 
+.IP 
+The \f(CWSIGUSR1\fP signal will cause \fBwinbindd\fP to
+write status information to the winbind log file including information
+about the number of user and group ids allocated by
+\fBwinbindd\fP\&.
+.IP 
+Log files are stored in the filename specified by the \fBlog file\fP parameter\&.
+.IP 
 .PP 
 .SH "FILES" 
 .PP 
diff --git a/docs/yodldocs/winbindd.8.yo b/docs/yodldocs/winbindd.8.yo
index ce32565755..0e0477c84e 100644
--- a/docs/yodldocs/winbindd.8.yo
+++ b/docs/yodldocs/winbindd.8.yo
@@ -196,13 +196,13 @@ To setup winbindd for user and group lookups plus authentication from
 a domain controller use something like the following setup. This was
 tested on a RedHat 6.2 Linux box.
 
-In /etc/nsswitch.conf put the following:
+In tt(/etc/nsswitch.conf) put the following:
 verb(
    passwd:     files winbind
    group:      files winbind
 )
 
-In /etc/pam.d/* replace the auth lines with something like this:
+In tt(/etc/pam.d/*) replace the tt(auth) lines with something like this:
 verb(
 	auth       required	/lib/security/pam_securetty.so
 	auth       required	/lib/security/pam_nologin.so
@@ -210,8 +210,8 @@ verb(
 	auth       required     /lib/security/pam_pwdb.so use_first_pass shadow nullok
 )
 
-Note in particular the use of the sufficient keyword and the
-use_first_pass keyword.
+Note in particular the use of the tt(sufficient) keyword and the
+tt(use_first_pass) keyword.
 
 Now replace the account lines with this:
 verb(
@@ -229,11 +229,11 @@ verb(
 	createuser MACHINE$ -j DOMAIN -L
 )
 
-This assumes your domain is called DOMAIN and your Samba workstation
-is called MACHINE.
+This assumes your domain is called tt(DOMAIN) and your Samba workstation
+is called tt(MACHINE).
 
-Next copy libnss_winbind.so.2 to /lib and pam_winbind.so to
-/lib/security.
+Next copy tt(libnss_winbind.so.2) to tt(/lib) and tt(pam_winbind.so) to
+tt(/lib/security).
 
 Finally, setup a smb.conf containing directives like the following:
 verb(
@@ -251,12 +251,38 @@ verb(
 
 Now start winbindd and you should find that your user and group
 database is expanded to include your NT users and groups, and that you
-can login to your unix box as a domain user, using the DOMAIN+user
+can login to your unix box as a domain user, using the tt(DOMAIN+user)
 syntax for the username. You may wish to use the commands "getent
 passwd" and "getent group" to confirm the correct operation of
 winbindd. 
 
-NOTE: nmbd must be running on the local machine for winbindd to work.
+NOTE: url(bf(nmbd))(nmbd.8.html) must be running on the local machine for
+url(bf(winbindd))(winbindd.8.html) to work.
+
+label(SIGNALS)
+manpagesection(SIGNALS)
+
+The following signals can be used to manipulate the
+url(bf(winbindd))(winbindd.8.html) daemon.
+
+startdit()
+
+dit(tt(SIGHUP))
+
+Reload the tt(smb.conf) file and apply any parameter changes to the running
+version of url(bf(winbindd))(winbindd.8.html).  This signal also clears any
+cached user and group information.
+
+dit(tt(SIGUSR1))
+
+The tt(SIGUSR1) signal will cause url(bf(winbindd))(winbindd.8.html) to
+write status information to the winbind log file including information
+about the number of user and group ids allocated by
+url(bf(winbindd))(winbindd.8.html).
+
+Log files are stored in the filename specified by the bf(log file) parameter.
+
+enddit()
 
 label(FILES)
 manpagefiles()
-- 
cgit