TO THE SAMBA TEAM:
MAY YOUR TRIBE BE HERE FOREVER! YOU' SIMPLY GREAT BUT i CAN'T AFFORD
TO
BUY YOU A PIZZA BUT OUR NATIVE PIE "BUKO (YOUNG COCONUT) PIE" IS
BETTER!
i HAVE BEEN USING SAMBA 1.9.16P9 AND STILL ALRIGHT. PERHAPS I'LL DO CHANGE
TO SAMBA 2.0 AND THIS IS A LONG WAY!
i DID TRIED SAMBA SINCE MY OFFICE CAN'T AFFORD TO BUY NFS TO SERVE AT
LEAST 20 PCs AND I DID IT FOR I NEED TO HAVE MY NETRA i20 (SUN WEBSERVER)
TALK TO MY PCs.WORST IS I DON'T HAVE A C COMPILER IN THAT MACHINE AND I HAVE
NEVER COMPILED A C SOURCE CODE IN MY LIFE AND HAVE NO FORMAL TRAINING IN SYS
ADM EITHER. BUT FOR THE CURIOSITY AND LOVE OF IT AND I MADE IT.
PLEASE DON'T STOP THERE.
HAVE A PIZZA i MEAN "buko PIE"
NESTOR FABELLAR
> -----Original Message-----
> From: samba@samba.org [SMTP:samba@samba.org]
> Sent: Sunday, January 10, 1999 8:42 AM
> To: N.FABELLAR@cgiar.org
> Subject: SAMBA digest 1937
>
> SAMBA Digest 1937
>
> For information on unsubscribing see http://samba.org/listproc/
> Topics covered in this issue include:
>
> 1) a browsing question
> by genght@cn.ibm.com
> 2) Samba 2.0.0 release soon
> by Jeremy Allison <jallison@cthulhu.engr.sgi.com>
> 3) oplock_break with samba 2.0
> by Maurice Agavnian <agavnian@cegelec-red.fr>
>
> ----------------------------------------------------------------------
>
> Date: Sat, 9 Jan 1999 09:39:25 +0800
> From: genght@cn.ibm.com
> To: samba@samba.org
> Subject: a browsing question
> Message-ID: <482566F4.00094D19.00@cn.ibm.com>
>
> Why my WIN9X client can't browse the samba file server,but they can
find
> it
> by searching?
>
>
> thanks,
>
> regards,
> ght
>
> E_mail: genght@cn.ibm.com
>
>
>
> ------------------------------
>
> Date: Fri, 08 Jan 1999 18:37:15 -0800
> From: Jeremy Allison <jallison@cthulhu.engr.sgi.com>
> To: samba@samba.org, jallison@cthulhu.engr.sgi.com, Samba NTDOM
> <samba-ntdom@samba.anu.edu.au>, Samba technical
> <samba-technical@samba.anu.edu.au>
> Subject: Samba 2.0.0 release soon
> Message-ID: <3696C0DB.B51DA7A7@engr.sgi.com>
>
> Hi all,
>
> We're putting together the final Samba 2.0.0
> release, hopefully to ship sometime next week.
>
> I'm currently writing a press release to send to the
> technology news Web and print sites, and was wondering
> if anyone who is currently using Samba would agree to be
> quoted in the press release.
>
> You know the sort of thing (I'm sure you've seen it in
> many other press releases :-) - "We at Company BlahBlah
> have been using Samba for 3 million years and it is the
> most wonderful software.... etc. etc. etc." :-).
>
> Truthful references only please :-).
>
> We're hoping to make a reasonable press splash with
> the Samba 2.0.0 release, so if you want to be quoted
> please email your quotes & testimonials to me at :
>
> Jeremy Allison <jra@samba.org>
>
> As this is a press release all negative comments will
> cheerfully be ignored :-) :-). If you are a corporation
> please make sure your legal people have okay'ed any
> quote you send (I don't want to get sued :-).
>
> Cheers,
>
> Jeremy Allison,
> Samba Team.
>
>
> --
> --------------------------------------------------------
> Buying an operating system without source is like buying
> a self-assembly Space Shuttle with no instructions.
> --------------------------------------------------------
>
> ------------------------------
>
> Date: Sat, 9 Jan 1999 14:24:22 +0100 (MET)
> From: Maurice Agavnian <agavnian@cegelec-red.fr>
> To: samba@samba.org
> Subject: oplock_break with samba 2.0
> Message-ID: <199901091324.OAA00374@k2.cegelec-red.fr>
>
> Sorry for all my emails. I don't know where to post this problem, so I
> also post it to the ntdom mailing list...
>
> Since I upgrade to 2.0beta5, I got a lot of messages like this in log.smb:
>
> [1999/01/08 16:30:38, 0] smbd/oplock.c:(734)
> oplock_break: receive_smb timed out after 30 seconds.
> oplock_break failed for file GN/previsions/previsions 99/previsions
> globales 99.xls (dev = 800073, inode = 904801).
> [1999/01/08 16:31:20, 0] smbd/oplock.c:(804)
> oplock_break: client failure in break - shutting down this smbd.
>
> When this happen, my samba server become very slow and files open by PC
> users are often lost.
>
> I was working with 1.9.18p7 before and never saw this problem.
>
> Does the "blocking locks" paramater has something to do with
oplock ?
>
> Can I use "oplocks = False" as a (poor) workaround ?
>
> Thanks.
> Maurice.
>
>
> My configuration:
> ---------------
> samba 2.0.0 beta 5 on Solaris 2.5.1
> PC are WinNT4 SP3 and Win95
>
> smb.conf:
> ---------
> [global]
>
> workgroup = SAMBA
> security = user
> logon script = logon.bat
> logon path = \\%L\%U\.%a-profile
> domain logons = yes
> encrypt passwords = yes
> passwd program = /bin/passwd %u
> passwd chat = *Enter*login*password* %o\n *New*password* %n\n
> *enter*new*password* %n\n *changed*
> unix password sync = yes
> domain admin group = @group1, @group2
>
> ; printing
> printing = sysv
> printcap name = /opt/samba/lib/printcap
> load printers = No
> print command = (lp -d%p -c -s -o nobanner %s; sleep 120; rm -f %s)
> &
> lpq command = lpstat -o%p
> lprm command = cancel %p-%j
>
> ; Char set
> character set = iso8859-1
> client code page = 850
> valid chars = ?:? ?:? ?:? ?:? ?:? ?:? ?:? ?:? ?:? ?:? ?:? ?:? ?:?
> ?:? ?:? ?:? ? ? ?
> preserve case = yes
> short preserve case = yes
>
> ; divers
> debug level = 0
> dont descend = ./etc,./var
> dead time = 15
> strip dot = yes
> nis homedir = true
> guest account = public
> max connections = 30
> invalid users = root
> dos filetimes = yes
> dos filetime resolution = yes
>
> ; wins server et wins support
> wins support = yes
> name resolve order = lmhosts wins host bcast
>
> ; master browser
> os level = 129
> preferred master = yes
> domain master = yes
> local master = yes
>
>
> [netlogon]
> comment = Logon scripts location
> path = /outils/netlogon
> browseable = no
> locking = No
>
> [homes]
> comment = Sweet Home
> browseable = no
> writable = yes
> max connections = 5
>
>
> [printers]
> comment = All Printers
> path = /tmp
> browseable = no
> public = yes
> printable = yes
> create mode = 0700
>
>
> ------------------------------
>
> End of SAMBA Digest 1937
> ************************
