Login script
Bill Shirley
webnut at icx.net
Wed Jun 28 01:47:33 GMT 2000
Couldn't you just use:
\\smbserver\logon\logon.bat
to run the command?
Bill
> ------------------------------
>
> Date: Mon, 26 Jun 2000 19:10:01 -0600 (MDT)
> From: Dan Egli <ninja at enol.com>
> To: Chris Watt <cnww at chebucto.ns.ca>
> Cc: samba at samba.org
> Subject: Re: Login script
> Message-ID: <Pine.LNX.3.96.1000626190939.8811A-100000 at mail.enol.com>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Sounds good. Thanks!
>
> On Sun, 25 Jun 2000, Chris Watt wrote:
>
> > At 03:16 PM 25/06/00 +1000, you wrote:
> >
> > >If there is a script I can place somwehre, please tell me
> what it's name
> > >is and where I can place it!
> >
> > Various Windows flavors have varying degrees of support for
> logon scripts
> > which might sometimes work. . . Personally I find that the
> easiest way to
> > handle things is to reference a batch file from the RUN key
> in the windows
> > registry along the lines of:
> >
> > REGEDIT4
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
> > "Logon"="C:\\windows\\logon.pif"
> >
> > Then logon.pif starts logon.bat with the run-minimized and
> close when done
> > options set. Logon.bat consists of essentially:
> >
> > --- CUT HERE --
> >
> > net time \\smbserver /set /yes
> > if errorlevel 1 goto error
> >
> > net use * \\smbserver\logon /yes | choice
> /C:abcdefghijklmnopqrstuvwxyz >NUL:
> > if errorlevel 0 set mappedrive=ERROR
> > if errorlevel 1 set mappedrive=a
> > if errorlevel 2 set mappedrive=b
> > if errorlevel 3 set mappedrive=c
> > if errorlevel 4 set mappedrive=d
> > if errorlevel 5 set mappedrive=e
> > if errorlevel 6 set mappedrive=f
> > if errorlevel 7 set mappedrive=g
> > if errorlevel 8 set mappedrive=h
> > if errorlevel 9 set mappedrive=i
> > if errorlevel 10 set mappedrive=j
> > if errorlevel 11 set mappedrive=k
> > if errorlevel 12 set mappedrive=l
> > if errorlevel 13 set mappedrive=m
> > if errorlevel 14 set mappedrive=n
> > if errorlevel 15 set mappedrive=o
> > if errorlevel 16 set mappedrive=p
> > if errorlevel 17 set mappedrive=q
> > if errorlevel 18 set mappedrive=r
> > if errorlevel 19 set mappedrive=s
> > if errorlevel 20 set mappedrive=t
> > if errorlevel 21 set mappedrive=u
> > if errorlevel 22 set mappedrive=v
> > if errorlevel 23 set mappedrive=w
> > if errorlevel 24 set mappedrive=x
> > if errorlevel 25 set mappedrive=y
> > if errorlevel 26 set mappedrive=z
> > if errorlevel 27 set mappedrive=ERROR
> >
> > if "%mappedrive%"=="ERROR" goto error
> >
> > call %mappedrive%\logon.bat
> >
> > net delete %mappedrive% /yes
> >
> > goto end
> >
> > :error
> > echo Oops, it looks like your network is broken
> > pause
> >
> > :end
> > --- CUT HERE --
> >
> > The preceding maps a share called "logon" to any available
> drive letter,
> > attempts to run a file called "logon.bat" located in that
> share (may be
> > user/machine/time dependant by using samba's various magic
> file creation
> > abilities) and then disconnects from the logon share. I've
> stripped out a
> > lot of the ugly kludge code for my specific setup, so the
> above may be
> > slightly broken in some way, but it should be possible to
> fix it easily
> > enough if that is the case.
> > The variation on this which I am using works fine in
> Windows9x, not sure
> > about NT but it should work if it has the dos NET command.
> > --
> >
> > Irony: Bill Gates claims to be making a stable Operating System,
> > and Linus Torvalds claims to be taking over the world.
> >
> >
>
>
> ------------------------------
>
> Date: Mon, 26 Jun 2000 21:20:01 -0400
> From: Josh Durham <jmd at aoe.vt.edu>
> To: samba at samba.org
> Subject: smb.log entries
> Message-ID:
> <Pine.SGI.4.21.0006262115310.25909-100000 at orion.aoe.vt.edu>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Sorry if this has been asked before, but I tried searching the mailing
> list, but the search engine seems to be broken.
>
> I'm getting a few interesting smbd.log entries, and wondered
> if anybody
> knew why.
>
> This just happens, sometimes:
> [2000/06/26 21:08:21, 0] lib/util_sec.c:(69)
> Failed to set gid privileges to (-1,-2) now set to (0,0) uid=(0,0)
> [2000/06/26 21:08:21, 0] lib/util.c:(2381)
> PANIC: failed to set gid
>
> And this just happens when I try to use Veritas' BackupExec
> to view the share:
> [2000/06/26 21:07:14, 0] smbd/service.c:(213)
> pluto (192.168.1.2) couldn't find service $
>
> The share is defined as:
> [u1$]
> comment = /u1 Administrative Share
> path = /u1
> valid users = Administrator, Backup
> public = no
> writable = no
> browseable = yes
> printable = no
> level2 oplocks = true
>
> And I get a 'Device Error' when I try to access u1$.
> Although it does see it.
> Any ideas?
>
> Thanks!
> - Josh
>
> * Josh Durham | AOE at Virginia Tech | (540) 231-9061 jdurham at vt.edu *
>
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 10:49:46 +0800
> From: "Ong Mooi Lan" <mlong at biccgeneral.com.my>
> To: <mlong at powercables.com.my>, <abartlet at pcug.org.au>
> Cc: "Aw Kong Koy" <kkaw at multicentric.com>,
> "Sirlena Yap" <sirlena at biccgeneral.com.my>,
> "Mak" <mak at biccgeneral.com.my>,
> "Multiple recipients of list SAMBA" <samba at samba.org>
> Subject: Re: "Root" passwd overwritten by user's passwd
> Message-ID: <000e01bfdfe2$5a93c5a0$be00a8c0 at mlong>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> Thank you very much. My problem resolved.
>
> ----- Original Message -----
> From: Andrew Bartlett <abartlet at pcug.org.au>
> To: <mlong at powercables.com.my>
> Cc: Multiple recipients of list SAMBA <samba at samba.org>
> Sent: Monday, June 26, 2000 9:23 PM
> Subject: Re: "Root" passwd overwritten by user's passwd
>
>
> > My understanding is that passwd program is run as ROOT when encrypt
> > passwords is on (becouse samba does not know the plain text
> password of
> > the user). Use '/usr/bin/passwd %u' to make passwd change the users
> > password.
> >
> >
> > Ong Mooi Lan wrote:
> > >
> > > I've Samba 2.0.6 running as a NT-Server, but there is a problem:
> > >
> > > When user change password at their workstation, the
> "root" password get
> > > overwriten by the new user password as well. Appreciate your
> assistance.
> > > Thank you.
> > >
> > > Below is same setting at the Samba server FYI:
> > > ================================
> > > workgroup = BGCM
> > > encrypt passwords = Yes
> > > update encrypted = Yes
> > > passwd program = /usr/bin/passwd
> > > passwd chat = *New*UNIX*password* %n\n
> *Retype*new*UNIX*password* %n\n
> > > *passwd:*all*authentication*tokens*updated*successfully*
> > > unix password sync = Yes
> > > domain logons = Yes
> > > preferred master = Yes
> > > domain master = Yes
> > >
> > > Ong Mooi Lan
> > > Systems Administrator
> > > BICCGeneral Cables (Malaysia) Sdn Bhd
> > > email: mlong at biccgeneral.com.my
> >
> > --
> > Andrew Bartlett
> > abartlet at pcug.org.au
> >
>
>
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 11:11:48 +0800
> From: "Andrew McRobert" <mcrobert at central.murdoch.edu.au>
> To: <pbzinc at redrose.net>
> Cc: "Samba-List (E-mail)" <samba at samba.org>
> Subject: Re: connecting to network remotely with pppd
> Message-ID: <000d01bfdfe5$6f51f450$27e27386 at murdoch.edu.au>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> hi
>
> I had a similar problem the other night, though not with
> Samba specifically
> (ie. just trying to dial up to a ppp server). The problem was
> in the routing
> tables also, I found that by knocking out the ethernet card
> (ifconfig eth0
> down) ... everything worked fine. You can put the commands to
> bring the eth0
> down and up again into your dialup and logoff scripts ....
>
> this may be the same problem you're having
> tks
>
> -------------------------------------------------
> Andrew McRobert LLB B.Sc(Comp. Sci)
> IT Officer, School of Law
> MURDOCH UNIVERSITY
> Perth, Western Australia
> Ph: [+61 8 9360 6479]
> Fax: [+61 8 9310 6671]
> e-mail: mcrobert at central.murdoch.edu.au
> "The lottery: a tax on people who are bad at math"
>
>
> ------------------------------
>
> Date: Mon, 26 Jun 2000 22:33:53 -0500
> From: "Shawn Barnhart" <swb at grasslake.net>
> To: <samba at samba.org>
> Subject: SWAT and authentication
> Message-ID: <006b01bfdfe8$845430e0$0102a8c0 at k6>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> What's the deal with SWAT authentication? I have a Freebsd
> 4-Stable box
> running SWAT from the Samba 2.0.7 port and I can log into SWAT as a
> regular user (ie, not root but has a smbpasswd entry) and make any
> changes I want to the smb.conf file -- which is 0644 root.wheel. I'm
> presuming this is because my inetd.conf entry for SWAT has it
> running as
> root as per the example.
>
> Is this how SWAT's _really_ supposed to work? Its a useful tool, but
> I'm terrified of any user with an account being able to
> mangle the conf
> file at will, create shares, etc. A [swat] section in the
> smb.cfg file
> would be excellent, or even a seperate swat.users file.
>
> Is there any way to control which users can and can't make changes to
> the server other than packet filtering the SWAT port? This is kind of
> awkward and inconvenient.
>
> If I'm missing something here, please let me know.
>
> --
> swb at grasslake.net
> Hard work often pays off after time, but laziness always pays off now.
>
>
>
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 10:03:11 +0200
> From: "Martin Richtarsky" <Martin.Richtarsky at in.stud.tu-ilmenau.de>
> To: "samba at samba.org" <samba at samba.org>
> Subject: FemFind - search engine for SMB/FTP shares
> Message-ID: <200006270800.KAA17025 at piggy.rz.tu-ilmenau.de>
> MIME-Version: 1.0
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> What is FemFind?
>
> FemFind is a crawler/search engine for SMB shares. FemFind does also
> crawl FTP servers and provides a web interface and a Windows client as
> frontends for searching.
>
>
> What do I need to run it?
>
> The FemFind crawler runs on a Unix platform (currently only Linux has
> been tested). It utilizes a MySQL database. The web interface requires
> a webserver. In addition some Perl modules are required, for details
> check the INSTALLATION part of the README.
>
> The Windows client should work with all versions of Windows.
>
>
> FemFind has been used for nearly a year in a university LAN and has
> evolved quite a bit over time. Although it runs reasonably stable
> I'm sure there are quite a few bugs still there. There are probably
> some bizarre Windows/Linux shares out there which I didn't encounter
> to date which it might not be able to handle.
>
> Please give me feedback if you use FemFind in your network,
> encounter any bugs or if you have problems with installation.
>
>
> Where to get it?
>
> Official Site:
> http://femfind.codefactory.de/
>
> Latest Versions
>
> Crawler/Webinterface
> http://www.codefactory.de/downloads/FemFind-0.68.tar.gz
>
> Windows Client
> http://www.codefactory.de/downloads/FemFind-winclient-0.65.zip
>
>
> Martin Richtarsky
>
> --
> http://www.codefactory.de/
>
> There are two ways to write error-free programs. Only the
> third one works.
>
>
>
>
> --
> http://www.codefactory.de/
>
> There are two ways to write error-free programs. Only the
> third one works.
>
>
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 13:14:48 +0200
> From: klaus-georg.adams at rwg.de
> To: " - *tridge at samba.org" <tridge at samba.org>
> Cc: " - *linux-kernel at vger.rutgers.edu"
> <linux-kernel at vger.rutgers.edu>,
> " - *samba at samba.org" <samba at samba.org>
> Subject: [Patch] for smbfs for reading from OS/2 Server against 2.4.0
> Message-ID: <0056940009889089000002L492*@MHS>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: 8BIT
> Content-Disposition: inline
>
>
> The appended patch against 2.4.0-test2 fixes the problem that
> reading a directory (e.g. with ls) from an OS/2 LAN Server
> was truncated after
> ~240 entries.
>
> Index: fs/smbfs/proc.c
> ===================================================================
> RCS file: /usr/src/cvsroot/linux/fs/smbfs/proc.c,v
> retrieving revision 1.1.5.1
> diff -u -r1.1.5.1 proc.c
> --- fs/smbfs/proc.c 2000/05/29 08:17:30 1.1.5.1
> +++ fs/smbfs/proc.c 2000/06/27 09:38:40
> @@ -7,6 +7,8 @@
> * 28/06/96 - Fixed long file name support
> (smb_proc_readdir_long) by Yuri Per
> * 28/09/97 - Fixed smb_d_path [now smb_build_path()] to be
> non-recursive
> * by Riccardo Facchetti
> + * 27/06/00 - Fixed smb_proc_readdir_long to work against
> an OS/2 server
> + * by Klaus-Georg.Adams at rwg.de
> */
>
> #include <linux/types.h>
> @@ -1554,9 +1556,8 @@
> command = TRANSACT2_FINDFIRST;
> WSET(param, 0, aSYSTEM | aHIDDEN | aDIR);
> WSET(param, 2, max_matches); /*
> max count */
> - WSET(param, 4, 8 + 4 + 2); /*
> resume required +
> -
> close on end +
> - continue */
> + WSET(param, 4, 4 + 2); /* resume
> required +
> +
> close on end */
> WSET(param, 6, info_level);
> DSET(param, 8, 0);
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 07:52:44 -0400
> From: "William R. Knox" <wknox at mitre.org>
> To: Multiple recipients of list SAMBA <samba at samba.org>
> Subject: Re: Odd WINS Problem
> Message-ID: <3958958C.BE95D249 at mitre.org>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Well, I hate to add to the "me, toos" out here, but the same thing has
> been happening to us on an unpredictable schedule for months. Here is
> some more info -
>
> Solaris 2.6 machines running 2.0.4b and 2.0.7.
>
> Multiple Windows NT 4.0 servers running SP 5 acting as WINS servers.
>
> One other odd piece of behavior - when it happens, it seems to affect
> ALL of our samba servers registered with the same WINS server at once
> (or at least within a matter of hours - we know when it happens fairly
> quickly, but not instantly), while the samba servers registered with
> another WINS server are unaffected.
>
> I sent out a note to this list about half a year ago and only heard a
> brief chatter of "me, toos" and then nothing. Has anyone seen any
> similar behavior and come up with a solution, or at least a
> root cause?
> Hell, I'll take even a possible cause. The only solution we've come up
> with is to stop and start the nmbd process every now and
> again in order
> to force it to reregister with the WINS server. But that smacks of the
> maintenance reboots that I hear NT admins have to do ;-)
>
> --
> Bill Knox
> Senior Operating Systems Programmer/Analyst
> The MITRE Corporation
>
> andrew morgan wrote:
> >
> > On Fri, 23 Jun 2000, Vogle, Brian wrote:
> >
> > > I've been having an odd problem with nmbd and WINS. We
> have two WINS
> > > servers running on NT4.0, and eight solaris machines
> running samba (2.0.7).
> > > Every so often, it appears that WINS loses its db entry
> for the samba
> > > machines. If I stop and restart nmbd, the samba machine
> reregisters with
> > > WINS and all is good. The problem is very sporadic, and
> doesn't seem to
> > > affect all of the machines.
> > >
> > > We've seen this problem since around the 2.0.4 days. We
> upgrade with each
> > > release hoping to fix the problem.
> >
> > I'd like to second this report. We had exactly this
> problem happen with a
> > linux server running 2.0.6. We couldn't see anything
> unusual in the logs
> > on either the samba machine or the WINS server. This has
> only happened to
> > us once.
> >
> > Andy
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 08:13:12 -0400
> From: "William R. Knox" <wknox at mitre.org>
> To: Multiple recipients of list SAMBA <samba at samba.org>
> Subject: Re: sending "WinPopup" message to a user
> Message-ID: <39589A58.2B55706B at mitre.org>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Russell,
> Seeing as you have gotten no response yet, I will lend my uneducated
> piece of observational guesswork. The NT machine which I use,
> when I log
> on, registers itself with the WINS server as an 03 resource type (i.e.
> able to receive WinPopUp messages) under both the machine
> name _and_ my
> logon name. This is verified by performing an nmblookup -R -U
> wins-server 'username#03', which returns a value, as does the
> same query
> with the machine name. So you should be able to use smbclient -M
> username and get the message to go to them. Again, this is on my NT
> machine - I have no idea if this is standard or freakish behavior.
>
> Good luck!
>
> Russell Kliese wrote:
> >
> > Just wondering if there is a way to send a WinPopup message
> to a user
> > (using username). I have had a look at smbclient but it
> appears to only
> > allow sending messages to a computer name.
> >
> > Thanks in advance,
> >
> > Russell Kliese
>
> --
> Bill Knox
> Senior Operating Systems Programmer/Analyst
> The MITRE Corporation
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 08:25:45 -0400
> From: "William R. Knox" <wknox at mitre.org>
> To: Multiple recipients of list SAMBA <samba at samba.org>
> Subject: Re: Retrieving browser lists
> Message-ID: <39589D49.A673E396 at mitre.org>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Omer,
> A two step process which will get you what you want. Do the following:
>
> 1. Query your localhost for shares (smbclient -N -L \\hostname). This
> will list the shares you have, your machines browse list, and then the
> workgroup list. In the workgroup list, it will have the local master
> browser for each workgroup, including your own. (if you are the local
> master browser, you can get the full browse list locally, albeit in a
> different format - the default location is, I believe,
> /usr/local/samba/var/locks/browse.dat. This file should always exist
> with the machines own browse list and could also be used to obtain the
> information about who is the local master browser).
>
> 2. Query the local master browser as above. This will spit
> back the same
> sort of list (the -N flag, by the way, prevents it from asking for a
> password, which will assist in automation), which will then contain in
> the second part the browse list for the subnet.
>
> Good luck!
>
> Omer Shenker wrote:
> >
> > I've searched the Samba docs, man pages, Using Samba, and a
> few other
> > places. I've been unable to find a way to retrieve the
> browse list (as in
> > Network Neighborhood or net view on Win32) from Samba. I'm
> using a RH 6.2
> > box running Samba 2.0.7 in a multi-subnet workgroup (which
> is really a
> > domain, but I don't have a machine trust account and I'm
> using security =
> > server). Samba is not involved in providing browsing or
> WINS, though it
> > utilizes both. I don't care if the format I get it in is
> messy like that of
> > nmblookup, because I'm parsing it in Perl anyway.
> >
> > I'd greatly appreciate any enlightenment on this.
> >
> > --
> > Omer Shenker oshenker at iname.com
>
> --
> Bill Knox
> Senior Operating Systems Programmer/Analyst
> The MITRE Corporation
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 10:39:35 -0400
> From: Edward Schernau <ed at schernau.com>
> To: samba at samba.org
> Subject: ACL support? 2.0.8?
> Message-ID: <3958BCA7.737548D at schernau.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Just wondering what the status of ACL support in 2.0.8 is,
> specifically if it will support the ACL patches for Linux 2.2.x
> or 2.4.x
> --
> Edward Schernau, mailto:ed at schernau.com
> Network Architect http://www.schernau.com
> RC5-64#: 243249 e-gold acct #:131897
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 12:40:30 EDT
> From: "Ben Tilly" <ben_tilly at hotmail.com>
> To: samba at samba.org
> Subject: smbmount cannot browse large NT directories
> Message-ID: <20000627164030.24399.qmail at hotmail.com>
> Mime-Version: 1.0
> Content-Type: text/plain; format=flowed
>
> This is a problem I get with various versions of Samba, up to
> and including
> 2.0.7. (The version shipped with Debian.)
>
> I have an NT machine (4.0, service-pack 3 using NTFS)
> exporting a filesystem
> to Linux through smbmount. Specific directories are not
> browsable. By that
> I mean that "ls *" comes up blank, however if you know the
> filename, "ls
> foo.txt" will still find the file and you can access it
> without problems.
>
> I do not have a simple test case for which ones have trouble,
> here is what I
> know. All of them have several thousand entries. A list of
> random files
> that long is OK. If I create an organized list I am OK. If
> I play around
> too much with the files in a directory, it becomes OK (at
> least for a bit).
> But I have a list of several thousand filenames where if I
> create a new
> directory, put files with those names in it, and then try to
> read it from
> Linux, I come up blank.
>
> Other NT machines have no problems with these directories.
>
> My current production workaround is to zip the directory in
> NT, then copy
> the zip file and unzip in Linux.
>
> Ideas?
>
> Ben
> ______________________________________________________________
> __________
> Get Your Private, Free E-mail from MSN Hotmail at
> http://www.hotmail.com
>
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 19:30:13 +0200 (CEST)
> From: Urban Widmark <urban at svenskatest.se>
> To: Ben Tilly <ben_tilly at hotmail.com>
> Subject: Re: smbmount cannot browse large NT directories
> Message-ID:
> <Pine.LNX.4.21.0006271922050.18065-100000 at cola.svenskatest.se>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> On Wed, 28 Jun 2000, Ben Tilly wrote:
>
> > This is a problem I get with various versions of Samba, up
> to and including
> > 2.0.7. (The version shipped with Debian.)
>
> It's not in smbmount, it's in smbfs. What kernel version are
> you using? It
> should be fixed in 2.2.14 and up. It is NOT fixed in
> 2.3/2.4-test since
> that smbfs code has not received the fixes made to 2.2.
>
>
> > I mean that "ls *" comes up blank, however if you know the
> filename, "ls
> > foo.txt" will still find the file and you can access it
> without problems.
>
> You should get an error message from smbfs in your syslog.
>
> > I do not have a simple test case for which ones have
> trouble, here is what I
> > know. All of them have several thousand entries. A list
> of random files
>
> If you want to play with it here is a zip I made when I ran
> into this (the
> 569 files are all supposed to be empty).
>
> http://www.hojdpunkten.ac.se/054/samba/samba-dir.zip
>
> /Urban
>
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 13:44:20 EDT
> From: "Ben Tilly" <ben_tilly at hotmail.com>
> To: urban at svenskatest.se
> Cc: samba at samba.org
> Subject: Re: smbmount cannot browse large NT directories
> Message-ID: <20000627174420.69155.qmail at hotmail.com>
> Mime-Version: 1.0
> Content-Type: text/plain; format=flowed
>
> Urban Widmark wrote:
> >
> >On Wed, 28 Jun 2000, Ben Tilly wrote:
> >
> > > This is a problem I get with various versions of Samba, up to and
> >including
> > > 2.0.7. (The version shipped with Debian.)
> >
> >It's not in smbmount, it's in smbfs. What kernel version are
> you using? It
> >should be fixed in 2.2.14 and up. It is NOT fixed in
> 2.3/2.4-test since
> >that smbfs code has not received the fixes made to 2.2.
> >
> 2.2.12. That sounds like it
> >
> > > I mean that "ls *" comes up blank, however if you know
> the filename, "ls
> > > foo.txt" will still find the file and you can access it without
> >problems.
> >
> >You should get an error message from smbfs in your syslog.
>
> I did.
>
> > > I do not have a simple test case for which ones have
> trouble, here is
> >what I
> > > know. All of them have several thousand entries. A list
> of random
> >files
> >
> >If you want to play with it here is a zip I made when I ran
> into this (the
> >569 files are all supposed to be empty).
> >
> >http://www.hojdpunkten.ac.se/054/samba/samba-dir.zip
> >
> Thanks greatly. Time to file a report with Debian then.
>
> Thanks,
> Ben
> ______________________________________________________________
> __________
> Get Your Private, Free E-mail from MSN Hotmail at
> http://www.hotmail.com
>
>
> ------------------------------
>
> Date: Tue, 27 Jun 2000 19:58:17 +0200 (CEST)
> From: Urban Widmark <urban at svenskatest.se>
> To: klaus-georg.adams at rwg.de
> Subject: Re: [Patch] smbfs in Linux 2.2.16 breaks reading
> from OS/2 Serve
> Message-ID:
> <Pine.LNX.4.21.0006271346160.12124-100000 at cola.svenskatest.se>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> On Tue, 27 Jun 2000 klaus-georg.adams at rwg.de wrote:
>
> >
> > Hi Andrew,
> > your patch from 2.2.15 to 2.2.16, backing out the older
> protocol levels breaks
> > reading from an OS/2 LAN Server.
> > The appended patch fixes things for me (against 2.2.16).
>
> This backs out a lot of desired changes. For example I think
> that 'rm -rf'
> on large directories will no longer work if you apply this because you
> change the cache to the old behaviour.
>
> > - * Jan 2000, cpg at aladdin.de
> > - * - added posix semantics for unlink
> > - * March 2000, tridge
> > - * - removed support for old protocol levels. It
> didn't work anyway
> > and
> > - * was cluttering things up a lot.
> > + * 20/03/00 (chrisp)
> > + * - fixed FINDFIRST flags for OS/2 Server
> > + * - added lastname/mask stuff back (OS/2 needs it)
>
> And you remove the nice "posix semantics for unlink".
>
> It looks like you have simply gone back to the 2.2.14/15
> version, and then
> added findfirst/lastname things. Maybe you could make a
> smaller patch that
> only adds back the parts necessary for it to work with OS/2? (or not,
> Tridge can probably see that anyway).
>
>
> Re: Your other email about listing long directories. I
> suggested something
> similar to your patch for fixing this in 2.2, but the
> preferred change was
> to use infolevel 260 instead of 259.
>
> 2.3/2.4-test hasn't received any of the changes that 2.2 has,
> including
> long dirs, posix unlink, rm -rf fixes. I have a patch vs
> 2.3.99-pre9 to
> upgrade smbfs to 2.2, that haven't made it past the maintainer yet.
>
> /Urban
>
>
> ------------------------------
>
> End of SAMBA Digest 2570
> ************************
>
More information about the samba
mailing list