Re: dir_check_ftype fixes??

On Mon, Dec 02, 2002 at 07:36:54PM +, [EMAIL PROTECTED] wrote: > Can you send me the details on how to reproduce please ? Install a DOS client and do an xcopy /S from a samba share to a local disk. SMBsearch sends garbage in the attrib field on the findnext, or if status_len!=0. Volker msg

Handling of 8,3 names on a NetApp

Hi, It seems that netapp generates something approaching line noise for 8,3 names after a certain number of names that differ after char 8 have been created: smb: \usr10\home\rsharpe\ntap\> altname thisisalong.fil THISIS~1.FIL smb: \usr10\home\rsharpe\ntap\> altname thisisalona.fil THISIS~2.FIL

Patch for unix extensions

This is a small patch which added a new config option to turn the ensure_link_is_safe check off. This check prevents a client using the unix extensions from creating a symlink which points to a directory outside of the share. Many GUI programs make links from ~ to /tmp which will fail. Gnom

Re: dir_check_ftype fixes??

On Mon, Dec 02, 2002 at 01:02:40PM +0100, [EMAIL PROTECTED] wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, Steve & all! > > In dir.c Jeremy added the following fix: > > revision 1.48.4.21 > date: 2002/09/10 01:58:58; author: jra; state: Exp; lines: +18 -3 > Added final Steve

Non-ASCII characters in share comments

Hi, this is my smb.conf: [global] workgroup = burse server string = "Roland (116)" netbios name = roland interfaces = eth0 bind interfaces only = yes local master = no protocol = NT1 security = share null passwords = yes

cannont change the Workgroup="" setting with swat

I don't know if it is a bug or there is a reason for this, but i can't change the Workgroup="" Parameter using swat in samba 3.0alpha21. I added it manually and it works fine, but i think it would be usefull to be able to change the workgroup using swat... thanks Albert Dengg -- Albert Dengg

Re: dir_check_ftype fixes??

On Mon, Dec 02, 2002 at 01:45:12PM +0100, Simo Sorce wrote: > I also have a bug report about problems with xcopy and 2.2.7 > I think we should really check if it is something we break. All those who have that problem, could you please check the following patch? diff -u -r1.240.2.121 reply.c --- s

Problem with utmp under Solaris

Hi, I found the following problem under Solaris (8) when enabling "utmp = yes". "last" is ok, but not "finger". # last livetan smb/9 10.64.3.241 Mon Dec 2 09:01 still logged in vassile smb/8 10.64.3.84 Mon Dec 2 09:01 still logged in # finger finger: Can't stat /dev/smb/8 ... and "fin

Printer names longer than 24 characters

Hello, I have Samba 2.2.7 installed on a FreeBSD 4.7 system. I noticed today that if I create a printer name with more than 24 characters then I can't set any of the printer settings. Changing the Properties of the printer are ignored and changing the Document Defaults returns the error "Printer

Re: dir_check_ftype fixes??

I also have a bug report about problems with xcopy and 2.2.7 I think we should really check if it is something we break. Simo. On Mon, 2002-12-02 at 13:02, [EMAIL PROTECTED] wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, Steve & all! > > In dir.c Jeremy added the following fix

dir_check_ftype fixes??

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Steve & all! In dir.c Jeremy added the following fix: revision 1.48.4.21 date: 2002/09/10 01:58:58; author: jra; state: Exp; lines: +18 -3 Added final Steve French patch for "required"attributes with old dir listings. Added regression test in

[PATCH] Parametrical options for HEAD/3.0

Andrew, attached is the latest version of parametrical options for HEAD and 3.0 (same patch is applicable for both with little offsets -- tested). This patch brings parametrical options to full power: - Options defined in [global] are inherited to all services and can be overriden in them.

Re: Need clue regarding CAP_NT_FIND.

That helps. Thanks! I wonder why that never made it into the doc... Chris -)- On Sat, Nov 30, 2002 at 07:36:56PM -0500, Green, Paul wrote: > Christopher R. Hertel [mailto:[EMAIL PROTECTED]] asked: > > There doesn't seem to be any documentation regarding the CAP_NT_FIND > > capability bit.

Help Is Here.....317867

Email:[EMAIL PROTECTED] 2-1Customer Service Number310890