From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>The only thing would be to completely disallow
>connection timeouts for Win9x clients - I'm not sure
>this is what we want.
Perhaps timeouts could be prevented for a 9x client when an oplock is
present? Or have two timeouts: a shorter (sof
On Fri, May 31, 2002 at 06:47:00PM -0400, [EMAIL PROTECTED] wrote:
> The attached set of patches cleans up samba-3.0-alpha17 for
> systems such as Stratus VOS that implement POSIX-1996 but do not
> provide full Unix compatibility. I would be most grateful if
> this patch could be applied against
The attached set of patches cleans up samba-3.0-alpha17 for
systems such as Stratus VOS that implement POSIX-1996 but do not
provide full Unix compatibility. I would be most grateful if
this patch could be applied against samba-3.0. I can supply a
version of this patch for samba-2.2 if/when anyo
On Sat, Jun 01, 2002 at 12:17:19AM +0200, Kai Krueger wrote:
> currently, as far as I can see, the access control to the SAM database is
> only based upon file access to the db-files. On normal installations
> therefore only the root user can change, delete or add things instead of the
> entire a
VFS - modlues
I want to check the fd on my first write call to see if it just got opened
by write call or is a susequent write call.
The purpose is to preform a backup only if the user actually write data to
thefile.
I have been study the vfs.h, smb.h, skel.c to figure this out
fsp->prev->fd c
On 30 May 2002, Simo Sorce wrote:
> On Wed, 2002-05-29 at 21:46, David W. Chapman Jr. wrote:
> > I don't think this will be a problem. We currently have a GPL math
> > emulator in our kernel, just not enabled by default
> >
> > options GPL_MATH_EMULATE#Support for x87 emulation v
Hi,
currently, as far as I can see, the access control to the SAM database is
only based upon file access to the db-files. On normal installations
therefore only the root user can change, delete or add things instead of the
entire administrators group. As this is IMHO rather "unhelpfull", es
On Fri, 31 May 2002, Sergey Ivanov wrote:
> Hello
>
>
> There are a couple of problems with smbclient connected with the socket timeout in
> the select operation.
> The default value of the timeout in smblib is about 20 seconds.
> Smbclient does not override this value.
> So, when a file is b
Hello
There are a couple of problems with smbclient connected with the socket timeout in
the select operation.
The default value of the timeout in smblib is about 20 seconds.
Smbclient does not override this value.
So, when a file is big enought, the checking procedure by antivirus can
be mor
>From: Nathaniel N.Petersen (CNS Student Support) <[EMAIL PROTECTED]>
>Date: Fri, 31 May 2002 08:15:07 -0500
>There is nothing wrong with using the homes directories like I do. The
>lines refered to in the man pages simply don't recommend it. Well, if
>you have ever worked for a Universit
If you're talking about Vyacheslav Zavadsky's Linux Trustees patches
(http://trustees.sourceforge.net/), you must write a backend to integrate it
with Samba as the interface is totally different from Linux's Posix ACL.
I looked into this a while ago, but sadly couldn't find the time to work on
it.
On Thu, 30 May 2002, Lapers Stefan wrote:
>
> Due to quite some problems with the RPC printing code in samba
> (landscape, paper size), I would like to disable the spoolss
> functionality and use the old code. However I will probably need Active
> Directory support in the near future, so revert
On Fri, 31 May 2002, Nieminen, Jooel wrote:
> I'm using samba I installed from the RPM package made for RH7.2 on
> fileserver and it works allright. So does winbind. but then I came up
> problems with file security and patched my kernel with trustee 2.8
> package.
>
> well, trustee works fine, b
Can't remember if this tecnique would affect something else, but you may
try this:
delete secrets.tdb set the new SID in MACHINE.SID, start samba.
finding MACHINE:SID samba will think it is a first time you run it and
will "upgrade" the machine.sid file into the secret.tdb database.
Simo.
On Fr
Hi,
I need to change the SID of a Samba server I have running. This used to
be relatively straightforward - one simply shut down Samba, backed up
the MACHINE.SID file, edited it to reflect the new SID for the machine,
and started up again.
However, recent versions of Samba have done away with
After talking this over with a friend, I realize that I have made a
mistake. I should never have responded in the manner that I did. I
was the one who asked for help. You don't know the situation, and you
are correct in that most people who do have problems either didn't read
the existing infor
On Fri, 2002-05-31 at 15:15, Nathaniel N.Petersen wrote:
> Note that from the client's point of view security = domain is the same
> as security = user . It only affects how the server deals with the
> authentication, it does not in any way affect what the client sees.
>
> Since the systems are a
On Fri, May 31, 2002 at 12:09:25PM +0530, Navneet Karnani wrote:
> Should you be deleting the user profile completely from the server, including
> the user credentials. The problem you encounter, looks like, windows is not able
> to find the directory. So, if you want to simulate a new user, do it
On Fri, May 31, 2002 at 10:07:37AM +0200, Stefan (metze) Metzmacher wrote:
> If you want to be a PDC set 'security = User' ,
> this means that samba uses it's own smbpasswd( or tdb or ldap...) as SAM
> Database, read 'man smb.conf' !!!
http://us1.samba.org/samba/ftp/docs/htmldocs/smb.conf.5.html
No, sorry it is not as simple.
When you use mangled names you must assure they will always be mangled
the same way during the same connection.
So if a file gets deleted and then recreated it must be mangled back the
same way!
This will make things overly complex and oblige us to keep 2 separate
ca
on 31-05-2002 12:21, Simo Sorce at [EMAIL PROTECTED] wrote:
>
> I just want to warn people that want to use the new hashing algorithm
> for mangled names.
>
> And that note should also be put in the man page IMO.
>
> You must understand that changing the hashing algorithm on a production
> ser
Title: RE: hash2 mangling alghorithm
Why not just use a different hash character for the new code, and keep the old unhashing code? Old hashed names can still be read, and new hashed names can still be stored and read. No confusion would take place.
-Original Message-
From: Simo Sorce
Hi,
Best you discuss this with your HP support people - cifsmount is a part of
the CIFSCLIENT software (based on Sharity client), NOT samba.
Sorry,
Don
-Original Message-
From: Simo Sorce [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 4:19
To: Manuel Clericuzio
Cc: '[EMAIL PROTECTE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Someone came to me with the following log message. To me it looks like
a corrupt tdb. The system is running Linux 2.2.19 with adaptec RAID
(dpt_io driver), LVM and the tdb's on ext2. The rest of the file
system is reiser. Samba is 2.2.3a. I don't
On Fri, 2002-05-31 at 12:39, Simo Sorce wrote:
> On Fri, 2002-05-31 at 12:20, [EMAIL PROTECTED] wrote:
> the above piece is wrong!
> wrong seem to be the original code. (an unjustified pdb_free_sam ?)
> I'll check it.
Sorry looking at the whole code the free is ok!
>
> Wrong is the patch!
> Why
On Fri, 2002-05-31 at 12:20, [EMAIL PROTECTED] wrote:
> Hi Andrew and Simo,
>
> this patches are only for discussion,( not completely ready)
>
> please take look at it the Patch for Makefile.in should be cleaner but I
> don't know how to do this... So it would be nice if someoneelse could do th
Am Freitag, 31. Mai 2002 11:58 schrieb Andrew Bartlett:
> Juergen Hasch wrote:
> >
> > I will generate a complete patch if the Samba team thinks it's worth
> > considering and I am not completely on the wrong track :-)
>
> What the heck are you trying here?
The problem is like this:
Without patch
I just want to warn people that want to use the new hashing algorithm
for mangled names.
And that note should also be put in the man page IMO.
You must understand that changing the hashing algorithm on a production
server may have unwanted side effects (this is why we maintain by
default hash a
Hi Andrew and Simo,
this patches are only for discussion,( not completely ready)
please take look at it the Patch for Makefile.in should be cleaner but I
don't know how to do this... So it would be nice if someoneelse could do that.
The reason for changing Makefile.in is that the global_sam_sid
Juergen Hasch wrote:
>
> Hi Guenther,
>
> Am Donnerstag, 30. Mai 2002 16:17 schrieb Guenther Deschner:
> > hello,
> >
> > smb.conf-manpage of 2.2.5pre and HEAD states the bug of "multi-byte
> > character sets in usernames":
> >
> > -8<--snip--8<--
> >
I'm new on this list and don't know is this problem too simple to be posted
here but...
I'm using samba I installed from the RPM package made for RH7.2 on
fileserver
and it works allright. So does winbind.
but then I came up problems with file security and patched my kernel with
trustee 2.8 pack
>From samba-technical.
On Fri, 2002-05-31 at 09:58, Manuel Clericuzio wrote:
> Buongiorno,
> mi hanno chiesto di montare un filesystem NT (macchina win2000) su una
> macchina con Unix HP (release 11.11).
> Ho provato a fare dei tentativi con il comando cifsmount ma non riesco.
> Spero che voi mi
Buongiorno,
mi hanno chiesto di montare un filesystem NT (macchina win2000) su una
macchina con Unix HP (release 11.11).
Ho provato a fare dei tentativi con il comando cifsmount ma non riesco.
Spero che voi mi potiate aiutare.
Grazie e buona giornata
Manuel
At 18:26 30.05.2002 -0500, Nathaniel N.Petersen (CNS Student Support) wrote:
>SAMBA VERSION: 2.2.4
>ERROR(S): Profile Creation
>
>I have recently been assigned to create a Samba PDC. Earlier in the
>
>--[smb.conf]--
>
>[global]
> workgroup = CNS_TESTING
> netbios name = TEST_SMB_S
On Fri, 2002-05-31 at 01:26, Nathaniel N.Petersen wrote:
> SAMBA VERSION: 2.2.4
> ERROR(S): Profile Creation
> I reported this to my supervisor, and he asked what version of Samba I
> was using. I told him version 2.2.3a. Well, he says that I shouldn't
> use an "alpha" version of Samba.
the 'a
35 matches
Mail list logo
