Is there any reason I should not apply this patch to Samba HEAD?
The current locking scheme in winbind is a complete mess - indeed, the
next step should be to push the locking into cli_full_connection(), but
I'll leave it for now.
This patch works on the noted behaviour that 2 parts of the
On Sat, Mar 08, 2003 at 09:10:23PM +1100, Andrew Bartlett wrote:
Is there any reason I should not apply this patch to Samba HEAD?
I think the patch was eaten by Mailman. Please re-send as text/plain.
Without even seeing the patch (-: it's definitely a good idea.
Tim.
On Sat, 2003-03-08 at 21:20, Tim Potter wrote:
On Sat, Mar 08, 2003 at 09:10:23PM +1100, Andrew Bartlett wrote:
Is there any reason I should not apply this patch to Samba HEAD?
I think the patch was eaten by Mailman. Please re-send as text/plain.
Without even seeing the patch (-: it's
On Sat, 2003-03-08 at 06:51, Andrew Bartlett wrote:
On Sat, 2003-03-08 at 04:12, Wolfgang Ratzka wrote:
-BEGIN PGP SIGNED MESSAGE-
Im currently running some tests for a samba/CUPS based print server.
The print server is a member of an NT domain and uses winbind to import
NT
Hi there,
I regret putting the wrong smb.conf in my mail. It is a UNIX path (path =
/home/%u/profile.%m). However, it does not matter, it doesn't work. It would
be nice to create batch files at logon time. Perhaps it is related to the
location of the user's profile. Whether roaming profile is
On Sun, 2003-03-09 at 02:39, John Newhouse wrote:
Hi,
I have samba 3.0a21 running and NT 4.0 WS clients.
All workstations were previously in Samba 2.2 domain , so now I upgraded to samba
3.0a22 and
just changed domain name (workstation = XXX) and rejoined workstations by changing
domain
Hi,
I have samba 3.0a21 running and NT 4.0 WS clients.
All workstations were previously in Samba 2.2 domain , so now I upgraded to samba
3.0a22 and
just changed domain name (workstation = XXX) and rejoined workstations by changing
domain name
in every WS.
To look at the log it seems like NT WS
