SAMBA digest 2141
Rich Hailstone
richard at insyst.com.au
Fri Jun 25 04:52:25 GMT 1999
digest samba richard at insyst.com.au richard
On 24 Jun 99, at 15:03, samba at samba.org wrote:
> SAMBA Digest 2141
>
> For information on unsubscribing see http://samba.org/listproc/
> Topics covered in this issue include:
>
> 1) %U variable
> by "Michel Peyron" <michel.peyron at accim.com>
> 2) A problem sharing printer with win
> by Hector Garcia <hecgarpe at inf.upv.es>
> 3) STATUS..LCK
> by Jason Pickering <jpickeri at utct2166.ct.utwente.nl>
> 4) problems with a WinNT SMB server
> by Massimo Pinto <pinto at graylab.ac.uk>
> 5) ERROR: Failed to initialize share modes!
> by "Matt Magoffin (Borders Online)" <mmagoffi at borders.com>
> 6) RE: No network neighborhood
> by Dave Lawson <DAVELA at menasco.com>
> 7) Re: STATUS..LCK
> by giulioo at tiscalinet.it (Giulio Orsero)
> 8) Re: v1.9.18p10 much more robust with security=server than v2.04
> by "Emrich Michael (QI/LBS3-RT) *" <Michael.Emrich at de.bosch.com>
> 9) Re: WinNT to Unix
> by Michal Jezierski <heja at xox.pl>
> 10) Big problems
> by Jason Pickering <jpickeri at utct2166.ct.utwente.nl>
> 11) Re: Samba vs. NetAppliance
> by Jeremy Allison <jallison at cthulhu.engr.sgi.com>
> 12) RE: STATUS..LCK
> by Heinz Christian <Christian.Heinz at nbg9.siemens.de>
> 13) Re: problems with a WinNT SMB server
> by "Kevin A. Pieckiel" <kapieckiel at harding.edu>
> 14) Authenticating Windows95 with Samba.
> by Ed Johns <ejohns at zoo.uvm.edu>
> 15) Re: Authenticating Windows95 with Samba.
> by Gerald Carter <cartegw at Eng.Auburn.EDU>
> 16) BSDI 4.0.1 Samba 2.0.4b Performance Problems???
> by "Sean Rolinson" <snowdog at bigfoot.com>
> 17) No automatic refresh?
> by Charles fake email address <cuser at fire.ibigroup.bc.ca>
>
> ----------------------------------------------------------------------
>
> Date: Wed, 23 Jun 1999 15:50:27 +0200
> From: "Michel Peyron" <michel.peyron at accim.com>
> To: <samba at samba.org>
> Subject: %U variable
> Message-ID: <002801bebd7f$5e586460$870aa8c0 at acc.fr>
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0023_01BEBD90.1D1183E0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Hello,
>
> I have created a share using the %U variable :
>
> [Doc]
> comment =3D Documents de %U
> path =3D /part2/%U
> valid users =3D %U
>
> With Windows 9x, I can connect to this resource, but
> with NT I can't.
>
> Hope someone could help me.
>
> TIA.
>
> PS : I'm using Samba 1.9.18p5. I've modified the
> registry to enable plain text passwords.
>
> ------=_NextPart_000_0023_01BEBD90.1D1183E0
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content=3D"text/html; charset=3Diso-8859-1" =
> http-equiv=3DContent-Type>
> <META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
> <DIV> </DIV>
> <DIV><FONT face=3DArial size=3D2>I have created a share using the =
> %U variable=20
> :</FONT></DIV>
> <DIV> </DIV>
> <DIV><FONT face=3DArial size=3D2>
> <DIV><FONT face=3DArial size=3D2>[Doc]</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> comment =3D Documents de =
> %U</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> path =3D =
> /part2/%U</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> valid users =3D =
> %U</FONT></DIV>
> <DIV> </DIV>
> <DIV>With Windows 9x, I can connect to this resource, but</DIV>
> <DIV>with NT I can't.</DIV>
> <DIV> </DIV>
> <DIV>Hope someone could help me.</DIV>
> <DIV> </DIV>
> <DIV>TIA.</DIV>
> <DIV> </DIV>
> <DIV>PS : I'm using </FONT><FONT face=3DArial size=3D2>Samba =
> 1.9.18p5. I've=20
> modified the</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>registry to enable plain text=20
> passwords.</FONT></DIV></DIV></BODY></HTML>
>
> ------=_NextPart_000_0023_01BEBD90.1D1183E0--
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 15:52:20 +0200
> From: Hector Garcia <hecgarpe at inf.upv.es>
> To: samba at samba.org
> Subject: A problem sharing printer with win
> Message-ID: <199906231649.PAA17740 at ivie.es>
>
> Hello:
>
> Somebody can solve me this problem?:
>
> 1- I have been installed the RedHat 6.0. I have an HP 670C printer
> configured like an HP 560C and works well in Linux. The problem appears
> when I want to share to print in other computer since Win95. I have
> installed Samba 2.0.3, and I see the printer since the computer Win95. I
>
> configure the printer with the driver of the HP 560C that has Win95. The
>
> proble is that when I try to print a page win gives me an error:
>
> A problem occurrs when print in \\PC2\HP_LINUX with the printer
> (HP_DESKJET 560C PRINTER)
> A problem occurrs when print because an unknown error of the system.
>
> I try to configure the queue with the RAW option, but I have the same
> problem. What can I do?
>
> My /etc/printcap is the following:
>
> #
> # Please don't edit this file directly unless you know what you are
> doing!
> # Be warned that the control-panel printtool requires a very strict
> format!
> # Look at the printcap(5) man page for more info.
> #
> # This file can be edited with the printtool in the control-panel.
>
>
> ##PRINTTOOL3## LOCAL cdj550 300x300 a4 {} DeskJet550 24 1
> lp:\
> :sd=/var/spool/lpd/lp:\
> :mx#0:\
> :sh:\
> :lp=/dev/lp0:\
> :if=/var/spool/lpd/lp/filter:
>
> My /etc/smb.conf is the following:
>
> ; /etc/smb.conf
> ;
> ; Reinicia el servidor cada vez que hagas cambios a este fichero, ej:
> ; /etc/rc.d/init.d/smb restart
>
> [global]
> printing = bsd
> printcap name = /etc/printcap
> load printers = yes
> log file = /var/log/samba-log.%m
> lock directory = /var/lock/samba
> share modes = yes
> workgroup = casa
> guest ok = yes
> guest account = hector
>
> [PUBLICO]
> path=/tmp
> browseable = yes
> writable = yes
>
> [HP_LINUX]
> #security = server
> path = /var/spool/lpd/lp
> postscript = yes
> printer name = lp
> browseable = yes
> writable = yes
> printable = yes
> print command = lpr -r -h %s
>
> #[homes]
> #comment = Directorios principales
> #browseable = no
> #read only = no
> #create mode = 0750
>
> #[tmp]
> #comment = Espacio de ficheros temporales
> #path = /tmp
> #read only = no
> #public = yes
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 16:37:57 +0200 (CEST)
> From: Jason Pickering <jpickeri at utct2166.ct.utwente.nl>
> To: samba at samba.org
> Subject: STATUS..LCK
> Message-ID: <199906231437.QAA01518 at utct2166.ct.utwente.nl>
>
> Hello,
> I have just installed the following system and am having trouble accessing the SAMBA server. I posted a message the other
> day, but I haven't received a response so, i thought thought I would try again.
>
> Machine = StarMax 3000/603e
> System= Linux 2.2.6
> Distribution = LinuxPPC R5
>
> Here is the problem. The machine is apparently visible on the network. I can see it from the other Win95 machines.
> "testparm" gives no errors. However, "smbstatus" results in the following message:
>
> Couldn't open status file /var/lock/samba/STATUS..LCK
>
> I have followed the "Diagnosing Samba FAQ" but didn't get very far. Can someone help this newbie out please?
>
> Thanks,
> Jason Pickering
> jpickeri at utct2166.ct.utwente.nl
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 15:53:08 +0100
> From: Massimo Pinto <pinto at graylab.ac.uk>
> To: samba at anu.edu.au
> Subject: problems with a WinNT SMB server
> Message-ID: <3770F4D4.A15CB68F at graylab.ac.uk>
>
> Hello,
>
> as a new Linux user (Red Hat6.0) I am trying to mount hard drives from a
> local network which is managed by a windows NTServer. When I try to
> launch from the command line:
>
> smbclient -L servername
>
> I am prompted for a password, which I presume is the same password that
> I use when I login from a Windows environemt. Given the pasword I get
> the message:
>
> session setup failed: ERRDOS - ERRnoaccess (Access denied. )
>
> My question is wheter the server is denying entrance or I am doing
> something wrong, and if so, which man pages to look into.
>
> I understand this may sound stupid to you experts and I apologise.
>
> P.S. I tried to login the SMB server on a unix machine in Italy and the
> same command, with my local password, worked fine. This would say that
> the problem is in my server here in the UK. But how do I overcome this?
>
> Best regards
>
> Massimo Pinto
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 11:36:42 -0400
> From: "Matt Magoffin (Borders Online)" <mmagoffi at borders.com>
> To: "'samba at samba.org'" <samba at samba.org>
> Subject: ERROR: Failed to initialize share modes!
> Message-ID: <69D22D320BA4D211BA5300805F9F4249017FE7FB at EXCHANGE02_PH>
>
> I've been getting this error when clients attempt to connect. testparm
> passes OK, and smbd and nmbd launch OK, but when a client attempts to
> connect I get the following error messages (in the log):
>
> locking/shmem.c:smb_shm_open(930)
> ERROR smb_shm_open : mmap failed with code Invalid argument
>
> locking/locking.c:locking_init(169)
> ERROR: Failed to initialize share modes!
>
> I've been trying to get this working for a couple of days now, anybody have
> any suggestions?
>
> Thanks... -- M@
>
> < < < senor mateo
> borders.com jefe interactivo
> (0.11) 734.477.1130
>
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 11:58:54 -0400
> From: Dave Lawson <DAVELA at menasco.com>
> To: "'samba at samba.org'" <samba at samba.org>
> Subject: RE: No network neighborhood
> Message-ID: <5423E9E4E7B9D011B6A2080009DB786E01467B7E at COMMUNICATION>
>
> > However, now we can't see systems in a standalone
> > workgroup (WORKGROUP, security = SHARE) from our regular
> > domain (DOMAINA, security = SERVER; or Windows systems in the
> > domain),
> > which is on the same subnet.
>
> Les, There are many of us sorry souls out here with the same problem.
> Does the samba team want to bite on this one?
>
> Regards,
> Dave Lawson
> CAD Coordinator
> Menasco Aerospace
> Oakville, Ontario
> (905) - 827-7777 ext. 398
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 18:43:48 +0200
> From: giulioo at tiscalinet.it (Giulio Orsero)
> To: jpickeri at utct2166.ct.utwente.nl
> Cc: Multiple recipients of list <samba at samba.org>
> Subject: Re: STATUS..LCK
> Message-ID: <19990623164528.A28F026EA8 at i3.golden.dom>
>
> On Thu, 24 Jun 1999 00:51:20 +1000, hai scritto:
>
>
> >"testparm" gives no errors. However, "smbstatus" results in the following message:
> >
> >Couldn't open status file /var/lock/samba/STATUS..LCK
>
> touch /var/lock/samba/STATUS..LCK
>
> or
>
> open a file from a win machine in order to make samba create it for you.
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 15:26:23 +0200
> From: "Emrich Michael (QI/LBS3-RT) *" <Michael.Emrich at de.bosch.com>
> To: "'samba at samba.org'" <samba at samba.org>
> Cc: "'cad at nbgm.siemens.de'" <cad at nbgm.siemens.de>
> Subject: Re: v1.9.18p10 much more robust with security=server than v2.04
> Message-ID: <C9DB0669A294D111BF8700005A40EA3202E15199 at rtmail2.rt.bosch.de>
>
> > 'password server NTPDC rejected the password'
> > That appears a few times in the logfile. That is not always a problem,
> > but in about 10% of all cases.
> > Very ugly is the fact, that iif this happened after a few password-tries
> > the NT-useraccount is locked out.
> > With samba v1.9.18p10 that was never a problem. I switched the
> samba-versions
> > between the two servers, but nothing changed (no hardware-dependencies).
> > The server with v2.0x has always the problem.
> > Question : Are there some smb.conf-parameters or timeout-constants in the
> C-sources
>
> Hello samba-list-reader,
>
> I have the same Problems (Version 2.0.3) does anybody know a solution.
> Thanks a lot in advance to all who will answer, please email me.
>
> Regards
> M. Emrich
>
> Robert Bosch GmbH ; QI/LBS3-Rt; Postfach 1342; 72703 Reutlingen
> Tel: (07121)/35-4018; Fax: -2687; Internet: Michael.Emrich at de.bosch.com
>
>
>
>
>
>
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 14:54:24 +0000
> From: Michal Jezierski <heja at xox.pl>
> To: Multiple recipients of list <samba at samba.org>
> Subject: Re: WinNT to Unix
> Message-ID: <3770F520.5B371B71 at xox.pl>
>
> Levent Gündogdu wrote:
>
> > BTW: I`m using smbmount myself with one little problem: when shutting down
> > the machine, all network devices go down first. After that, all file systems are
> >
> > unmounted. My system hangs there, when I leave smb-mounts mounted, because
> > they cannot be unmounted anymore (no NET-IFs left). Does anybody know how
> > to solve this little ugly problem?
>
> Just check out shutdown scripts. If you are using RedHat (I do, so the
> examples come from this system) first check the numbers in the names of
> symlinks in /etc/rc.d/rc.0 and /etc/rc.d/rc.6.
>
> You can also write a short shutdown script which unmounts samba shares
> before other actions are taken (e.g. /etc/rc.d/rc.0/K01smbumount symlink
> that points to the /etc/rc.d/init.d/smbumount script written by you)
>
> Hope this helps.
>
> Michal
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 21:09:05 +0200 (CEST)
> From: Jason Pickering <jpickeri at utct2166.ct.utwente.nl>
> To: samba at samba.org
> Subject: Big problems
> Message-ID: <199906231909.VAA11538 at utct2166.ct.utwente.nl>
>
> I have posted a few messages earlier redgarding the lack of a STATUS..LCK file. I have
> progressed a bit further on the advice of some nice people on this list serve. Now, I seem to
> have the follwing problem with samba 2.0.4b on Linux 2.2.6 runnning on a Motorola StarMax 3000.
>
> after executing smbstatus, i get this message:
>
> Samba version 2.0.4b
> Service uid gid pid machine
> _______________________________________________
> WARNING smb_shm_open : filsize (0) !=expected size (1048576), using filesize
> ERROR smb_shm_vaildate_header : shmem not mapped
> ERROR smb_shm_open : corrupt shared mem file, remove it manually
> ERROR smb_shm_unregister : couldn't find pid 11530 in file
> /usr/local/samba/var/locks/SHARE_MEM_FILE.processes
> ERROR; Failed to initialise share modes!
> Can't initalise shared memory exiting
>
> Way over my head... any clue for the gurus out there?
>
> Thanks,
> Jason Pickering
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 13:18:37 -0700
> From: Jeremy Allison <jallison at cthulhu.engr.sgi.com>
> To: samba at samba.org, paul at netapp.com, jallison at cthulhu.engr.sgi.com
> Subject: Re: Samba vs. NetAppliance
> Message-ID: <3771411D.320B0F2F at engr.sgi.com>
>
> Paul Benn wrote :
>
> > > Much better control over who accesses what filesystems.
> >
> > Sorry if I seem ignorant of a particular Samba or UNIX functionality but I'm not
> > sure what you mean here. It might be argued that the reverse is true since
> > NetApp natively supports both UNIX style file permissions and NTFS style
> > permissions (ACLs).
>
> This is true. But it doesn't provide a very understandable
> mapping from a complex ACL when accessed from an NT client
> to a UNIX permission when accessed from an NFS client. My
> problem with your design (which I know quite a bit about,
> funnily enough :-), is that it violates the principle of
> least suprises for the nfs user. ie. They may get access
> denied when the UNIX perms say they should be granted access.
>
> > Based on my limited experience, the new ACL functionality
> > introduced with Samba 2.0.4 (which BTW I think is a very nifty addition)is
> > merely a way for an NT savvy admin to manipulate the underlying UNIX file
> > permissions via Windows Explorer.
>
> No arguement there, as this is exactly what it is designed to do.
> I'm still awaiting judgement on the user requests for true ACLs
> (which we can do by mapping into POSIX ACLs, when enough UNIX's
> support them). Most NT software simply doesn't use the NT ACL
> design. Nice though it is from a security point of view, for
> most users it is just unimaginably complex.
>
> There's something to be said for just providing UNIX permissions :-).
>
> > Oh and don't forget that DOS attributes, such
> > as the "archive bit," are mapped to the UNIX "x" bits which may present problems
> > in multiprotocol environments. Here's a quote from John D. Blair's book "Samba
> > Integrating UNIX and Windows" copyright 1998, page 239: "The unusual changes in
> > execute permissions may disrupt use of files from UNIX users.
>
> Yep, very true and without kernel access not something
> that's easy to fix.
>
> > > Thousands of people using/testing/beating on/improving the software
> >
> > NetApp also has many thousands of people using/testing/beating on filers (the
> > next web site you hit may have a filer back ending it).
>
> Not on the same order of magnitude though. Trust me on this (by
> the volume of email I get :-).
>
> > > Quite slow tech support response time
> >
> > Perhaps when compared to the
> > always-someone-reading-it-around-the-world-at-any-given-time Samba digest. But
> > then again, you seem not to be counting the "toasters" mailing list which can
> > provide equally fast response times. You only have to wait on your internet
> > connection and query speed when using the NetApp knowledge base. I know things
> > are changing but who are you going to _call_ when you have a Samba issue and you
> > don't own an SGI box (and even then how long will the response times be)?
>
> This is a straw man. Have you looked at the Samba consultants list ?
> This is also not even mentioning such companies as IBM & HP who are now
> supporting Linux (all versions of which include Samba), LinuxCare,
> RedHat, Caldera and a host of other companies (I can't even remember
> them all). Remember - every "Linux Certified Engineer" will also be
> able to support Samba :-).
>
> I recently came back from Linux Expo Paris where there were many
> consulting companies exhibiting on the show floor who were offering
> commercial Samba and Linux support. Contrast this with NetApp where
> support is only available from one company.
>
> > Sure the CIFS license is more expensive than $FREE but we feel that NetApp
> > offers a better CIFS implementation as well as better Windows/UNIX integration.
>
> Well this is one of those "the market will decide" things :-) :-).
> And the customers always win those :-).
>
> Cheers,
>
> Jeremy Allison,
> Samba Team.
>
> --
> --------------------------------------------------------
> Buying an operating system without source is like buying
> a self-assembly Space Shuttle with no instructions.
> --------------------------------------------------------
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 22:37:14 +0200
> From: Heinz Christian <Christian.Heinz at nbg9.siemens.de>
> To: Multiple recipients of list <samba at samba.org>
> Cc: "'giulioo at tiscalinet.it'" <giulioo at tiscalinet.it>,
> Subject: RE: STATUS..LCK
> Message-ID: <31F0B2A5DF38D111AFD800805F0D61D08733F2 at NBGV101A>
>
> > ----------
> > From: giulioo at tiscalinet.it[SMTP:giulioo at tiscalinet.it]
> > Reply To: giulioo at tiscalinet.it
> > Sent: Mittwoch, 23. Juni 1999 18:45
> > To: Multiple recipients of list
> > Subject: Re: STATUS..LCK
> >
> > On Thu, 24 Jun 1999 00:51:20 +1000, hai scritto:
> >
> >
> > >"testparm" gives no errors. However, "smbstatus" results in the following message:
> > >
> > >Couldn't open status file /var/lock/samba/STATUS..LCK
> >
> > touch /var/lock/samba/STATUS..LCK
> >
> > or
> >
> > open a file from a win machine in order to make samba create it for you.
> >
> Maybe there´s another reason for the mentioned "error".
> Locking and locking-reporting via smbstatus worked fine on all but a few machine here.
> After some investigation we found that on the faulty machines, samba used /var/lock and not /var/lock/samba as on the other machines.
> I put "error" in quotes above because samba itself worked always fine - only smbstatus didn´t report anything.
>
> Now we have a "lock directory = /var/lock/samba" statement in all of our smb.conf´s ;-)
>
>
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 14:06:43 -0500 (CDT)
> From: "Kevin A. Pieckiel" <kapieckiel at harding.edu>
> To: Massimo Pinto <pinto at graylab.ac.uk>
> Cc: Multiple recipients of list <samba at samba.org>
> Subject: Re: problems with a WinNT SMB server
> Message-ID: <Pine.GSO.4.10.9906231404110.8366-100000 at taz.harding.edu>
>
> On Thu, 24 Jun 1999, Massimo Pinto wrote:
>
> -> as a new Linux user (Red Hat6.0) I am trying to mount hard drives from a
> -> local network which is managed by a windows NTServer. When I try to
> -> launch from the command line:
> ->
> -> smbclient -L servername
>
> The username being passed is that which you are using on the Linux box. If
> your user names don't match, use the -U switch and specify the NT username
> with which you want to connect. Also, make sure your Linux box is using
> the right domain. The -W switch may be useful. And, of course, make sure
> your caps lock key isn't on. 8-) It wouldn't hurt to make sure you have
> permissions on the NT box for the share you're trying to access.
>
> Hope that helps.
>
> Kevin
>
> ---
> |\ _,,,---,,_
> ZZZzz /,`.-'`' -. ;-;;,_
> |,4- ) )-,_. ,\ ( `'-' Kevin Alan Pieckiel
> '---''(_/--' `-'_) kapieckiel at harding.edu
>
> (This message was written with vi)
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 17:10:14 -0400 (EDT)
> From: Ed Johns <ejohns at zoo.uvm.edu>
> To: samba at samba.org
> Subject: Authenticating Windows95 with Samba.
> Message-ID: <Pine.A41.4.05.9906231702470.36342-100000 at gnu1.uvm.edu>
>
> I recently compiled smbd 2.0.4b under AIX 4.3.2 with DCE/DFS support. I
> am able to map my home directory on a Windows95 PC on the subnet. Now, I
> am wondering if there are any references on how to set up smbd as an
> authentication server. I was a nice guy and bought the book, but it only
> hinted (or so I thought). :)
>
> Thanks a lot.
>
> -egj
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 16:17:33 -0500
> From: Gerald Carter <cartegw at Eng.Auburn.EDU>
> To: ejohns at zoo.uvm.edu
> Subject: Re: Authenticating Windows95 with Samba.
> Message-ID: <37714EED.7B37E513 at eng.auburn.edu>
>
> Ed Johns wrote:
> >
> > am wondering if there are any references on how to set
> > up smbd as an authentication server. I was a nice guy
> > and bought the book, but it only hinted (or so I thought). :)
>
> Which book? If you the Teach Yourself Samba book, what you
> need should be in the chapter on Windows 9x domain control.
>
>
>
>
>
> Cheers,
> jerry
> ________________________________________________________________________
> Gerald ( Jerry ) Carter
> Engineering Network Services Auburn University
> jerry at eng.auburn.edu http://www.eng.auburn.edu/users/cartegw
>
> "...a hundred billion castaways looking for a home."
> - Sting "Message in a Bottle" ( 1979 )
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 18:27:21 -0400
> From: "Sean Rolinson" <snowdog at bigfoot.com>
> To: <samba at samba.org>
> Subject: BSDI 4.0.1 Samba 2.0.4b Performance Problems???
> Message-ID: <028601bebdc7$94d2b110$0ca586d0 at bigfoot.com>
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0282_01BEBDA6.08D63770
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> Hello group,
>
> I have a BSDI 4.0.1 box running Samba 2.0.4b. The box is a dual 350mhz,
> 256MB RAM, 2 36Gig Shares, 1 18Gig Share,1 9Gig root, Intel onboard SCSI
> controller (Symbios?) and is on a fully switched full duplex 100MB fast
> ethernet network.
>
> The NT box is running 4.0 SP3, dual 400mhz, 256MB RAM, 2 4Gig Seagate SCSI
> Drives, Adaptec 2940UW and is on the same network as above. (full duplex
> switched)
>
> We have an NT Server copying >200,000 tiny files (4GB total) to one of the
> 36 Gig shares. Its been running for 22 hours now and has copied about
> 80,000 of the files (1.4GBish). I am not sure where the bottleneck is.
> Before this operation we were able to copy a 200MB file from the NT Server
> to the same share on the Samba box and this took less than a minute.
>
> I've read through the performance suggestions and none seemed to address
> this issue. Performance seems great for large files or small numbers of
> files per directory, but lots of tiny files seems to be a problem. My
> uneducated guess would be that it is somewhere in the read or write
> operations of Samba. Or possibly locking (although I did check this in the
> performance doc and we have default locking).
>
> During the operation we tried to copy a 3.5MB file from the NT Server to the
> Samba/Unix box. It took about 20 seconds.
>
> During the operation we tried to copy a 3.5MB file from a different NT
> Server on the same network to the Samba/Unix box, same share, and it took
> less 2 seconds.
>
> It could be NT trying to read a very large directory and taking its sweet
> time. Or it could be the Samba/Unix server trying to write to an
> increasingly larger directory and taking its sweet time?
>
> Has anyone heard of this before and what suggestions, if any, can you
> make???
> (Besides not putting 200k files in a directory!) :)
>
> Thanks in advance...
>
> Sean
> snowdog at bigfoot.com
>
> ------=_NextPart_000_0282_01BEBDA6.08D63770
> Content-Type: application/x-pkcs7-signature;
> name="smime.p7s"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;
> filename="smime.p7s"
>
> MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKbjCCAjww
> ggGlAhAyUDPPUNFW81yBrWVcT8glMA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYD
> VQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0
> aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05NjAxMjkwMDAwMDBaFw0yMDAxMDcyMzU5NTlaMF8xCzAJ
> BgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJs
> aWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTCBnzANBgkqhkiG9w0BAQEFAAOBjQAw
> gYkCgYEA5Rm/baNWYS2ZSHH2Z965jeu3noaACpEO+jglr0aIguVzqKCbJF0NH8xlbgyw0FaEGIea
> BpsQoXPftFg5a27B9hXVqKg/qhIGjTGsf7A01480Z4gJzRQR4k5FVmkfeAKA2txHkSm7NsljXMXg
> 1y2He6G3MrB7MLoqLzGq7qNn2tsCAwEAATANBgkqhkiG9w0BAQIFAAOBgQBLRGZgaGTkmBvzsHLm
> lYl83XuzlcAdLtjYGdAtND3GUJoQhoyqPzuoBPw3UpXD2cnbzfKGBsSxG/CCiDBCjhdQHGR6uD6Z
> SXSX/KwCQ/uWDFYEJQx8fIedJKfY8DIptaTfXaJMxRYyqEL2Raa2Nrngv2U2k8LS12vc3lnWojX4
> RTCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNV
> BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg
> UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIy
> MzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
> c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv
> cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJ
> bmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEB
> AQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZMUFweoFL
> uUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+HSr8Z2vkV6A+Hthzj
> zMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMCAQYw
> RwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29t
> L3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEB
> AgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/
> LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDl
> X4KmsaiSxVhqwY0DPOvDzQWikK5uMIIE+DCCBGGgAwIBAgIQGXUwWg49Ie3WhZk9xr5SzDANBgkq
> hkiG9w0BAQQFADCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWdu
> IFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEg
> SW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
> Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZDAeFw05OTAzMjkw
> MDAwMDBaFw0wMDAzMjgyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
> BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVw
> b3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNv
> bmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUg
> RnVsbCBTZXJ2aWNlMRYwFAYDVQQDFA1TZWFuIFJvbGluc29uMSIwIAYJKoZIhvcNAQkBFhNzbm93
> ZG9nQGJpZ2Zvb3QuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDWNn1Wvkjec9UCzkf8
> QJC5wiUWEbHekWR/xYd0Q8pD6Ozc9KUoy5ZoZKGtxzBo8kUKQOWSimqR7h7H+g564W1b0H32ckRN
> l+ouDwj6Ke40X4rLU2N2PJ9i0sel5yWe4saItclSVcE1BMoNyN+xxMbZrONOpJ6hPFyO+tsNs0R3
> GQIDAQABo4IBjzCCAYswCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCB
> jjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBW
> MBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJl
> bmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMIGGBgpghkgB
> hvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5Mjk4NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5
> ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjIxNDFiZWFkYjJiZDJlODkyMTdhZDZiZjNkNDExNDg5ZWEz
> YjM0NWZlZjNlYTQ1MGMwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20v
> Y2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQBA8aFHcoFqn0gue5lkHVQnaRpr/TITIdZaA3gc
> 1dsxCQS+QAKEui8G9M5Gpy8PkHs5LHof3quLKoEimFZk6P2Aj8UxVS+3a3L2bqi8oIGtF5DGNMdD
> dMoo/O/BOGr3iwhRfukiskckKQ/UWRQT2Bg408K2xSK38DqFyV5wSz3nhjGCAkUwggJBAgEBMIHh
> MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0
> d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5
> IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlk
> dWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhAZdTBaDj0h7daFmT3GvlLMMAkG
> BSsOAwIaBQCggbowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNOTkw
> NjIzMTgyNzIxWjAjBgkqhkiG9w0BCQQxFgQUT4/H1TBTBnizvNscae04ysX6OPwwWwYJKoZIhvcN
> AQkPMU4wTDAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4D
> AgcwDQYIKoZIhvcNAwICASgwBwYFKw4DAh0wDQYJKoZIhvcNAQEBBQAEgYAf/4pmnhDNVeJse190
> Z59wN+nKf46rbRZnkQdiBtqDc3TJsBcPs/JMJVQaN3Tx9yWFHAAgpG0rNcRtdCJoApPL622wjbAz
> fwniEViGnB2YphJqm/mtwu7MXcK63m9HNE1zGEYI4v4J2e6oUrs6s/RSMPnqe78WMKmWV3F15muK
> LQAAAAAAAA==
>
> ------=_NextPart_000_0282_01BEBDA6.08D63770--
>
>
> ------------------------------
>
> Date: Wed, 23 Jun 1999 20:57:40 -0700
> From: Charles fake email address <cuser at fire.ibigroup.bc.ca>
> To: samba at samba.org
> Subject: No automatic refresh?
> Message-ID: <199906240357.UAA08088 at fire.ibigroup.bc.ca>
>
> Hi!
>
> I've been struggling with this install of Samba 2.0.4b on Linux/x86 2.0.36.
> All of the client machines run Windows NT 4, SP 3.
>
> I'm exporting /tmp as pub, and if I right click in the folder and create
> a new folder, it doesn't show up until I go to 'view' and 'refresh'.
> If I delete something, it doesn't go away until I refresh.
>
> Why?
>
>
> Output of testparm:
> -------------------
> Load smb config files from /usr/local/lib/smb.conf
> Loaded services file OK.
> Press enter to see a dump of your service definitions
> # Global parameters
> [global]
> workgroup = JBI
> netbios name =
> netbios aliases =
> server string = Samba file/print server
> interfaces = 10.10.10.254/24
> bind interfaces only = No
> security = SHARE
> encrypt passwords = No
> update encrypted = No
> allow trusted domains = Yes
> hosts equiv =
> min passwd length = 5
> map to guest = Never
> null passwords = No
> password server =
> smb passwd file = /usr/local/private/smbpasswd
> root directory = /
> passwd program = /bin/passwd
> passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed*
> passwd chat debug = No
> username map =
> password level = 0
> username level = 0
> unix password sync = No
> restrict anonymous = No
> use rhosts = No
> log level = 1
> syslog = 1
> syslog only = No
> log file =
> max log size = 512
> timestamp logs = Yes
> protocol = NT1
> read bmpx = No
> read raw = Yes
> write raw = Yes
> nt smb support = Yes
> nt pipe support = Yes
> nt acl support = Yes
> announce version = 4.2
> announce as = NT
> max mux = 50
> max xmit = 65535
> name resolve order = lmhosts host wins bcast
> max packet = 65535
> max ttl = 259200
> max wins ttl = 518400
> min wins ttl = 21600
> time server = No
> change notify timeout = 60
> deadtime = 0
> getwd cache = Yes
> keepalive = 300
> lpq cache time = 10
> max disk size = 0
> max open files = 10000
> read prediction = No
> read size = 16384
> shared mem size = 1048576
> socket options = IPTOS_LOWDELAY TCP_NODELAY
> stat cache size = 50
> load printers = Yes
> printcap name = /etc/printcap
> printer driver file = /usr/local/lib/printers.def
> strip dot = No
> character set =
> mangled stack = 50
> coding system =
> client code page = 850
> stat cache = Yes
> domain groups =
> domain admin group =
> domain guest group =
> domain admin users =
> domain guest users =
> machine password timeout = 604800
> add user script =
> delete user script =
> logon script =
> logon path = \\%N\%U\profile
> logon drive =
> logon home = \\%N\%U
> domain logons = No
> os level = 92
> lm announce = Auto
> lm interval = 60
> preferred master = Yes
> local master = Yes
> domain master = Yes
> browse list = Yes
> dns proxy = No
> wins proxy = No
> wins server =
> wins support = Yes
> kernel oplocks = Yes
> ole locking compatibility = Yes
> oplock break wait time = 10
> smbrun = /usr/local/bin/smbrun
> config file =
> preload =
> lock dir = /var/locks
> default service =
> message command =
> dfree command =
> valid chars =
> remote announce =
> remote browse sync =
> socket address = 0.0.0.0
> homedir map = auto.home
> time offset = 0
> unix realname = No
> NIS homedir = No
> panic action =
> comment =
> path =
> alternate permissions = No
> revalidate = No
> username =
> guest account = guest
> invalid users =
> valid users =
> admin users =
> read list =
> write list =
> force user =
> force group =
> read only = Yes
> create mask = 0744
> force create mode = 00
> directory mask = 0755
> force directory mode = 00
> guest only = No
> guest ok = No
> only user = No
> hosts allow =
> hosts deny =
> status = Yes
> max connections = 0
> min print space = 0
> strict sync = No
> sync always = No
> print ok = No
> postscript = No
> printing = bsd
> print command = lpr -r -P%p %s
> lpq command = lpq -P%p
> lprm command = lprm -P%p %j
> lppause command =
> lpresume command =
> queuepause command =
> queueresume command =
> printer name =
> printer driver = HP Designjet 755
> printer driver location =
> default case = lower
> case sensitive = No
> preserve case = Yes
> short preserve case = Yes
> mangle case = No
> mangling char = ~
> hide dot files = Yes
> delete veto files = No
> veto files =
> hide files =
> veto oplock files =
> map system = No
> map hidden = No
> map archive = Yes
> mangled names = Yes
> mangled map =
> browseable = Yes
> blocking locks = Yes
> fake oplocks = No
> locking = Yes
> mangle locks = Yes
> oplocks = Yes
> oplock contention limit = 2
> strict locking = No
> share modes = Yes
> copy =
> include =
> exec =
> postexec =
> root preexec =
> root postexec =
> available = Yes
> volume =
> fstype = NTFS
> set directory = No
> wide links = Yes
> follow symlinks = Yes
> dont descend =
> magic script =
> magic output =
> delete readonly = No
> dos filetimes = No
> dos filetime resolution = No
> fake directory create times = No
>
> [printers]
> comment = All Printers
> path = /usr/spool/public
> create mask = 0700
> guest ok = Yes
> print ok = Yes
>
> [pub]
> comment = Public files
> path = /tmp
> read only = No
> guest ok = Yes
> --------------
>
> ------------------------------
>
> End of SAMBA Digest 2141
> ************************
More information about the samba
mailing list