There's no point to block these, winbind will ignore them anyway.
Jerry, Jeremy, we definitely need a chance to trigger a reconnection attempt
after a DC has been rebooted. Right now winbind's reaction to a single rebooted
DC is to declare it offline. It will not try before a "winbind cache timeout"
timeout. If the admin sets this to an hour or longer for performance reasons,
we're screwed. Reboot your DC, no logon for an hour.
Volker
(This used to be commit
cb065a8995fa0a18f9124d0bdea70c692d6b5c58)
return False;
}
- if (!lp_winbind_offline_logon()) {
- fprintf(stderr, "The parameter \"winbind offline logon\" must "
- "be set in the [global] section of smb.conf for this "
- "command to be allowed.\n");
- return False;
- }
-
/* Remove the entry in the winbindd_cache tdb to tell a later
starting winbindd that we're online. */
return False;
}
- if (!lp_winbind_offline_logon()) {
- fprintf(stderr, "The parameter \"winbind offline logon\" must "
- "be set in the [global] section of smb.conf for this "
- "command to be allowed.\n");
- return False;
- }
-
/* Create an entry in the winbindd_cache tdb to tell a later
starting winbindd that we're offline. We may actually create
it here... */