Re: Browsing

2002-11-26 Thread Jay Ts
hen restart the Samba server (smbd and nmbd). Jay Ts

Re: Fixed: OpLocks caused the corruptions/slowness (Was: How Samba let us down)

2002-10-31 Thread Jay Ts
development process is very nice, but the top priority has to be on what works in practice. Just my opinion... from someone who's been around consulting and has seen some really extreme, and also mission-critical (i.e., insane *and* life supporting!) computing environments. Jay Ts

Re: Fixed: OpLocks caused the corruptions/slowness (Was: How Samba let us down)

2002-10-28 Thread Jay Ts
it will make life much easier for Samba administrators, help magazine testing labs _fairly_ compare Samba performance with that of Windows (they can make sure to turn oplocks on before running the test), and also make Microsoft look bad, as they should, IMO, since they created this stuff. Maybe i

Re: Fixed: OpLocks caused the corruptions/slowness (Was: How Samba let us down)

2002-10-28 Thread Jay Ts
quest? Or is it worse? (I will also add a note saying that Samba is no different than Windows in its default behavior.) Jay Ts

Re: [Samba] libsmbclient in Mac OS X / Darwin

2002-10-27 Thread Jay Ts
S X, but I don't know who to contact there. Jay Ts

Re: Consistency in parameter names?

2002-10-23 Thread Jay Ts
t it's worth changing the names of the parameters, but maybe in smb.conf(5), the description could more clearly state that the parameters accept _commands_ (with args) as values, and that the commands can run binary programs or interpreted scripts. Make sense? Jay Ts

Re: (no subject)

2002-10-23 Thread Jay Ts
/use Netbios > names anyway so the RFC1001 support that nmbd helps with is not necessary. Er, is that all you're using your test systems for? Jay Ts

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
John H Terpstra wrote: > Jay Ts wrote: > > John H Terpstra wrote: > > > > > > For the record, I thouroughly test samba pre-releases before we ever ship. > > > To the best of my knowledge, NOT ONE version of samba we have released > > > ever CAUSED (or

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
responses is that they don't attract responses. But, well-written questions from people who have a strong desire to be helped, and are willing to take the bother to tune in with someone who cares to provide help, often get responses. Asking questions on mailing lists is both a technique and an art form. There are no guarantees of any kind of reply, ever. Jay Ts

Re: Fixed: OpLocks caused the corruptions/slowness (Was: How Samba let us down)

2002-10-23 Thread Jay Ts
a share, or some number of files with somehow-similar names that can be matched using a file globbing pattern or patterns. > We might reenable kernel then > regular then level2 oplocks later to see if it was > just one particular type. Pretty please! I'm really curious to find out exactly what was happening. Jay Ts

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
people are more likely to choose flaky products or misuse good ones!) Of course, it's still important to keep testing and debugging, to ensure that when something bad is bound to happen, it chooses someone else's software as a conduit of least resistance. ;) Jay Ts

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
t too much time on this today, especially considering that I never intended to start on this subject... Jay Ts [EMAIL PROTECTED]

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
be open to reports, rather than to maintain an "attitude" and try to squash any reports that would suggest otherwise. I'm a little surprised at how quickly Samba Team members jumped on what I wrote, even though I was not actually maintaining that Samba corrupted data! You can take this as a philosophical meandering if you please. ;) Cheers, Jay Ts

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
In any case, it was all more than a year ago, and isn't an issue to me at all. Jay Ts

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
the MS Windows client I just set up the Windows system as usual, with IP address, workgroup, computer name, WINS and DNS servers, etc. But, being Windows 98, the installation that was on the system might well have been corrupted somehow! That would not be unusual, after all. Jay Ts

Re: [Samba] Re: How Samba let us down

2002-10-23 Thread Jay Ts
Jeremy Allison ([EMAIL PROTECTED]) wrote: > Jay Ts wrote: > > > > > The corruption might be related to oplocks. I'm doing Just to keep myself out of more trouble today, I'd like to point out that I didn't write the above. ;-) > File corruption is treated as

Re: Running smb without nmb? (Linux Suse 8.1 feature)

2002-10-23 Thread Jay Ts
ript that does something like: #!/bin/bash /etc/init.d/smb $1 /etc/init.d/nmb $1 That way, it will work like Red Hat and other distributions, so you can start/stop/restart/(etc.) Samba with one command. Jay Ts

Re: How Samba let us down

2002-10-23 Thread Jay Ts
Steve Langasek wrote: > Jay Ts wrote: > > > kernel oplocks are for synchronizing SMB clients and > > local Unix processes. If you have no processes on linux > > accessing the files, then it's probably safe to disable them. > > But, if you are using Linux, the

Re: How Samba let us down

2002-10-23 Thread Jay Ts
Steve Langasek wrote: > Jay Ts wrote: > > If that is the case, then it's important to let the PDC handle > > both domain master browser and local master browser tasks, and > > not ever let any system steal either role away from it (or > > else bad things can hap

Re: How Samba let us down

2002-10-23 Thread Jay Ts
> In smb.conf add: > wins support = yes > > And configure each device to have the IP (of the samba box running with wins > support=yes) in the WINS address field on each device. > On samba servers use this line in smb.conf : > wins server = ip.of.wins.server Yep, then restart the Samba daemons. It's really simple. Jay Ts

Re: How Samba let us down

2002-10-23 Thread Jay Ts
orrect. Since what you wrote above possibly suggests you didn't see that, I suspect you might be running a binary distribution, and maybe it's old ... so, what version of Samba are you running? Try compiling a new version (2.2.6, for example). Older versions had bugs, and I've seen the same behavior that you describe with earlier releases of 2.2.x. Jay Ts author, Using Samba, 2nd edition

Re: logon problem

2002-09-18 Thread Jay Ts
you should see a message on the screen saying that it is executing the logon script. You may see a Command Prompt window appear, and maybe turn into an button on the taskbar. These will disappear when the script finishes. Jay Ts -- This electronic transmission and any files attached to

Re: Two diffs to add paramater self-checking

2002-07-16 Thread Jay Ts
ad ... not terribly different than HTML anyway. Later I might print out all the Samba docs and submit diffs for the typos and other obvious inaccuracies I've found. The *hard* part is going to be translating Using Samba, from Framemaker's buggy HTML output, to SGML. I don't even want to guess if this is even practicable. Jay Ts [EMAIL PROTECTED]

Re: Two diffs to add paramater self-checking

2002-07-15 Thread Jay Ts
>On Mon, 15 Jul 2002, Jay Ts wrote: >> Neither did I, considering that the smb.conf(5) manual page says: >> >> If the security parameter is set to domain, then >> the list of machines in this option must be a list >> of Primary or B

Re: Two diffs to add paramater self-checking

2002-07-15 Thread Jay Ts
hat, then I would like to request that the smb.conf manual page be updated. Jay Ts [EMAIL PROTECTED]

Re: What is the case for preserving case under Samba ...

2002-07-08 Thread Jay Ts
Richard Sharpe wrote: > On Sun, 7 Jul 2002, Jay Ts wrote: > > > At 3:24 PM -0700 7/7/02, Richard Sharpe wrote: > > >I want to preserve case sensitive behaviour for NFS and UNIX clients, > > >while reducing the current high cost to CIFS users of providing &

Re: What is the case for preserving case under Samba ...

2002-07-07 Thread Jay Ts
ly for each client on the network (which would not be a fun maintenance task!). Jay Ts [EMAIL PROTECTED]

Re: Bug found in smbclient

2002-05-13 Thread Jay Ts
Jay Ts wrote: > > $ smbclient //server/share -c "ls" -Tc > added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0 > Segmentation fault BTW, I should have mentioned that I'm running Samba 2.2.4 on Red Hat 7.1 here. Jay Ts [EMAIL PROTECTED]

Bug found in smbclient

2002-05-12 Thread Jay Ts
n odd behavior (the cd command ran, then smbclient hung, without doing a tar backup). I haven't tried any other smbclient commands with -c. Jay Ts [EMAIL PROTECTED]

winbind enum {users|groups} ??

2002-04-19 Thread Jay Ts
nbind enum" in their descriptions in the smb.conf(5) manpage. 3. Just above that in the winbind cache time description, under Default:, it is listed as winbind cache "type", rather than "time". Jay Ts [EMAIL PROTECTED]