SAMBA digest 1954
Bruce Kerr
bkerr at lcgs.tas.edu.au
Mon Jan 25 10:14:35 GMT 1999
Hi, How much is mail-gear and where can I buy it?
----- Original Message -----
From: <samba at samba.org>
To: Multiple recipients of list <samba at samba.org>
Sent: Monday, January 25, 1999 6:14 PM
Subject: SAMBA digest 1954
> SAMBA Digest 1954
>
>For information on unsubscribing see http://samba.org/listproc/
>Topics covered in this issue include:
>
> 1) Re: [WIN NT] uppercase
> by Majid Tajamolian <majid at sobhan.bol.sharif.ac.ir>
> 2) Using UserManager with Samba2.0
> by "=?iso-8859-1?Q?Wolfgang_Pf=FCller?=" <w.pfueller at abo.freiepresse.de>
> 3) Re: What kind of system works best?
> by "A.G. Russell IV" <arussell at bifrost.hos.net>
> 4) Compilation Warning
> by Boorman Tim <tim.boorman at hyder.com>
> 5) Re: What kind of system works best?
> by Peter Debus <pdebus at turing.une.edu.au>
> 6) HPUX 9.05 & Samba 2.0.0 & problems -> solved !
> by Panu Outinen <Panu.Outinen at vertex.fi>
> 7) Re: Digest Only?
> by "Rask Ingemann Lambertsen" <rask at kampsax.k-net.dk>
> 8) Problems running apps from Samba 2.0.0 share on NT 4.0
> by Firebeard <stend+samba at sten.tivoli.com>
>
>----------------------------------------------------------------------
>
>Date: Sun, 24 Jan 1999 12:33:19 +0330 (IST)
>From: Majid Tajamolian <majid at sobhan.bol.sharif.ac.ir>
>To: Tajthy Tamas <tajthy at mail.euroweb.hu>
>Subject: Re: [WIN NT] uppercase
>Message-ID:
<Pine.LNX.3.96.990124122903.108D-100000 at sobhan.bol.sharif.ac.ir>
>
>Hi Tajthy,
>
>> I have a problem. If I create a file under UNIX (samba 1.18.xx) with
>> capital letters in its name and look at this file under NT the name
>> become small letters. Not under Win95.
>>
>> What should I set to avoid the case changing in file names???
>
>Add the followings to your smb.conf file:
>
> case sensitive = no
> preserve case = yes
> short preserve case = yes
> mangled names = no
>
>For more read smb.conf(5) man page.
>
>-- Cheers,
> M. Tajamolian
>
>
>------------------------------
>
>Date: Sun, 24 Jan 1999 13:27:49 +0100
>From: "=?iso-8859-1?Q?Wolfgang_Pf=FCller?=" <w.pfueller at abo.freiepresse.de>
>To: "Samba" <samba at samba.org>
>Subject: Using UserManager with Samba2.0
>Message-ID: <000201be4795$6123fc00$07e919c2 at ws>
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_001C_01BE479D.560ECA40
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>How can I change the users password in the smbpasswd-file on my Unix-Box =
>(SCO OS5.0.5) from an NT-WS4.0 using the UserManager for WinNT,
>or must I use the smbpasswd-command on the Unix-Side
>
>Thanks, Wolfgang Pfueller
>
>------=_NextPart_000_001C_01BE479D.560ECA40
>Content-Type: text/html;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
><HTML>
><HEAD>
>
><META content=3Dtext/html;charset=3Diso-8859-1 =
>http-equiv=3DContent-Type>
><META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT size=3D2>How can I change the users password in the =
>smbpasswd-file on=20
>my Unix-Box (SCO OS5.0.5) from an NT-WS4.0 using the UserManager for=20
>WinNT,</FONT></DIV>
><DIV><FONT size=3D2>or must I use the smbpasswd-command on the=20
>Unix-Side</FONT></DIV>
><DIV><FONT size=3D2></FONT> </DIV>
><DIV><FONT size=3D2>Thanks, Wolfgang Pfueller</FONT></DIV></BODY></HTML>
>
>------=_NextPart_000_001C_01BE479D.560ECA40--
>
>
>------------------------------
>
>Date: Sun, 24 Jan 1999 13:05:15 -0600 (CST)
>From: "A.G. Russell IV" <arussell at bifrost.hos.net>
>To: samba at samba.org, ben at amvalue.com
>Subject: Re: What kind of system works best?
>Message-ID: <199901241905.NAA19548 at bifrost.hos.net>
>
>Ben, just as a thought, why not attack this as a High Availiblity
>problem, much cheaper than fault-tolerant... Most fault-tolerant
>solutions that I have seen, (Compaq/Tandem,Sequent,Digital) will run
>in the neighborhood of $100,000.00 USD or more.
>
>With Linux and little scripting you could have 2 solid servers, and a
>fail-over solution that could meet your needs.
>
>I am not conversent with Dell, but I know that there are servers with
>raid 5, for around $5000.00 and a pair would give you a
>High Availiblity answer.
>
>If you like we can take this offline...
>
>A.G.
>
>"Benjamin Suto wrote..."
>> If any of you recall, I sent a message before regarding issues with a
>> 100 client-based Samba server. After speaking with the company I'm
>> working with and showing them some of the replies, they are enthusiastic
>> about the system, and we're all looking forward to seeing it working.
>>
>> Thank you for all your replies and for your help. There were quite a
>> few replies, and I can't get a chance to reply to all of them. All this
>> help I'm getting really makes me want to try and contribute back however
>> I can. The support on this mailing list is remarkable.
>>
>> One last question, I promise. :-) They're willing to spend around
>> $10000 USD for the system, as they want the best system, since this will
>> be a mission-critical part of their corporation. I figure that the
>> amount is probably overkill, but I'd like to spend the money in getting
>> the most fault-tolerant and reliable system they can get. We're also
>> looking for a good disk subsystem with a lot of storage.
>>
>> They use Dell as a vendor for most of their systems. Is a Dell
>> Poweredge server shipped with no OS installed and RAID a good buy? Will
>> the hardware work with Linux? They're looking to have a RAID 5 based
>> array. There are too many options with those systems, and I'm not sure
>> what all of it means.
>>
>> Dell is their preferred vendor. If there is another vendor that would
>> make a system that works better, and it's a compelling difference, I'm
>> sure they would go along with it.
>>
>> If you have any experiences with hardware for a powerful fault-tolerant
>> redundant RAID system on the budget of $10000 or less, I'd be interested
>> in finding out what kind of hardware you got and whether you have any
>> problems with it.
>>
>> Thanks for your help,
>>
>> Ben
>
>
>___________________________________________________________________________
____
>A.G. Russell IV KC5KFD High Order Software e-mail:
ag4 at hos.net
>Phone 512-834-1145
> These are my views, on anyone else they would look silly.
> When it absolutely, positively has to be destroyed by tomorrow...
> United States Marine Corps
>---------------------------------------------------------------------------
----
>
>------------------------------
>
>Date: Sun, 24 Jan 1999 20:00:05 -0000
>From: Boorman Tim <tim.boorman at hyder.com>
>To: "'samba at listproc.anu.edu.au'" <samba at anu.edu.au>
>Subject: Compilation Warning
>Message-ID:
<152FFA7887B6D111A1EC0020AFA477FBB4F068 at ww-bridgend-5.WelshWater>
>
>While compiling Samba 2.0.0 on an Intel based DG AViiON running DG/UX
>Release R4.20MU01, I get the following warning message:
>
>smbd/chgpasswd.c: In function `findpty':
>smbd/chgpasswd.c:71: warning: assignment makes pointer from integer without
>a cast
>
>Is this something I should be concerned about?
>
>Regards,
> Tim
>
>> Tim Boorman
>> Team Leader, UNIX Systems Support
>> Hyder, PO Box 110, Technology Drive, Bridgend Science Park, Bridgend,
>> United Kingdom CF31 3WA
>> Extension: 44966
>> Direct Line: +44 (0)1656 765966
>> Mobile: +44 (0)468 647495
>> Email: tim.boorman at hyder.com
>>
>
>------------------------------
>
>Date: Mon, 25 Jan 1999 09:39:54 +1100 (EST)
>From: Peter Debus <pdebus at turing.une.edu.au>
>To: ben at amvalue.com
>Cc: samba at samba.org
>Subject: Re: What kind of system works best?
>Message-ID: <199901242239.JAA18541 at turing.une.edu.au>
>
>There is a heap of info about RAID. Only some RAID hardware is supported,
>You must read the HOWTOs and other recources to find out if the supllied
>DELL hardware is supported. DPT RAID hardware, there are others, is well
>supported.
>
>A little light reading:
>
> http://sunsite.unc.edu/mdw/HOWTO/mini/DPT-Hardware-RAID.html
> http://sunsite.unc.edu/mdw/HOWTO/Root-RAID-HOWTO.html
> http://sunsite.unc.edu/mdw/HOWTO/mini/Software-RAID.html
> RAID at linas.org:
> http://linas.org/linux/raid.html
>
>also check out the following for general and Linux specific
>RAID discussions.
>
>http://www.uni-mainz.de/~neuffer/scsi/
>
>If you are unsure about the Dell hardware, try a search on
>Deja news, someone may have been over that territory before.
>
>
>Benjamin Suto wrote:
>>
>> If any of you recall, I sent a message before regarding issues with a
>> 100 client-based Samba server. After speaking with the company I'm
>> working with and showing them some of the replies, they are enthusiastic
>> about the system, and we're all looking forward to seeing it working.
>>
>> Thank you for all your replies and for your help. There were quite a
>> few replies, and I can't get a chance to reply to all of them. All this
>> help I'm getting really makes me want to try and contribute back however
>> I can. The support on this mailing list is remarkable.
>>
>> One last question, I promise. :-) They're willing to spend around
>> $10000 USD for the system, as they want the best system, since this will
>> be a mission-critical part of their corporation. I figure that the
>> amount is probably overkill, but I'd like to spend the money in getting
>> the most fault-tolerant and reliable system they can get. We're also
>> looking for a good disk subsystem with a lot of storage.
>>
>> They use Dell as a vendor for most of their systems. Is a Dell
>> Poweredge server shipped with no OS installed and RAID a good buy? Will
>> the hardware work with Linux? They're looking to have a RAID 5 based
>> array. There are too many options with those systems, and I'm not sure
>> what all of it means.
>>
>> Dell is their preferred vendor. If there is another vendor that would
>> make a system that works better, and it's a compelling difference, I'm
>> sure they would go along with it.
>>
>> If you have any experiences with hardware for a powerful fault-tolerant
>> redundant RAID system on the budget of $10000 or less, I'd be interested
>> in finding out what kind of hardware you got and whether you have any
>> problems with it.
>>
>> Thanks for your help,
>>
>> Ben
>>
>
>
>--
>Peter Debus
>Computer Systems Administrator
>School of Mathematical Computer Sciences
>University of New England
>Armidale NSW
>Australia
>
>Ph: 61 (0)267 73 2412 Fax: 61 (0)267 73 3312
>
>------------------------------
>
>Date: Mon, 25 Jan 1999 00:43:08 +0200
>From: Panu Outinen <Panu.Outinen at vertex.fi>
>To: jallison at cthulhu.engr.sgi.com, samba at samba.org
>Subject: HPUX 9.05 & Samba 2.0.0 & problems -> solved !
>Message-ID: <3.0.1.32.19990125004308.00ab7330 at vertex.fi>
>
>Hi there !
>
>I just solved the problem that produced following error in smb.log file:
> 'check_access_allowed_for_current_user: The process is no longer
waiting!'
>
>Since nobody gave me any help I had to dig this out myself :-)
>
>This error happens if two programs hold more than 10 same files
>simultaneously open through Samba and
>check_access_allowed_for_current_user() gets called. And this failed
>occassionally!
>
>The problem was that HPUX 9.0x and earlier don't restart (by default!)
system
>calls! And here waitpid() gets interrupted!
>-----------------------------------
>ftp://ftp.interworks.org/pub/comp.hp/porting_info/sun_hpux_port_ascii_0295
>.
>SunOS's sigaction() automatically restarts system calls. The default
>behavior on HP-UX is to not restart. As noted in the Solaris Porting FAQ,
>code that depends on restarting system calls is generally considered to be
>bad practice and should be avoided. SunOS provides the SA_INTERRUPT option,
>which is used to prevent system calls from being restarted. SA_INTERRUPT is
>not available on HP-UX, but is the default behavior of sigaction() on HP-UX
>(that is, does not restart signal calls).
>
>SA_RESTART is used on SunOS to make system calls restart. It is not
>available on HP-UX. Instead, the sigcontext parameter passed to the signal
>handler can be used within the signal handler itself to specify SIG_RESTART
>or SIG_RETURN after handling an interrupted system call:
>.
><code example>!!!!
>-----------------------------------
>Good code example HPUX 9.0x specific code for signals:
>
>ftp://ftp.cup.hp.com/dist/networking/benchmarks/netperf/netperf-2.1pl3.tar.
gz
>-----------------------------------
>
>
>OK, here's my fix HPUX9.0x patch against Samba 2.0.0:
>
>There are actually two patches, only one is obligatory.
>
>The ugly one is the restartable signal code for HPUX < 10.20. I think 10.20
>has SA_RESTART according to people's code example posts to usenet, but
>since I don't have access to 10.20 right now, please verify! (our only
>10.20 burned its hard drive recently!)
>
>The open.c patch is a must on OS's (there can be more than just HPUX <10.20
>!) where system calls are not restarted automatically!
>
>-----------------------------------
>diff -u --recursive --new-file source/lib/signal.c source.new/lib/signal.c
>--- source/lib/signal.c Thu Jan 14 22:07:33 1999
>+++ source.new/lib/signal.c Sun Jan 24 23:32:44 1999
>@@ -47,8 +47,21 @@
> catch child exits - leave status;
>
****************************************************************************
/
>
>-static void sig_cld_leave_status(int signum)
>+static void
>+#if defined(HPUX) && !defined(SA_RESTART) /* e.g. HPUX 9.0x */
>+sig_cld_leave_status(int signum, int code, struct sigcontext *scp)
>+#else
>+sig_cld_leave_status(int signum)
>+#endif
> {
>+#if defined(HPUX) && !defined(SA_RESTART) /* e.g. HPUX 9.0x */
>+ extern int DEBUGLEVEL;
>+ if(scp->sc_syscall!=SYS_NOTSYSCALL) {
>+ scp->sc_syscall_action = SIG_RESTART; /* default: SIG_RETURN */
>+ /* waitpid() -> scp->sc_syscall == 200 ! */
>+ DEBUG(9,("sig_cld_leave_status: syscall %d
>restarted\n",scp->sc_syscall));
>+ }
>+#endif
> /*
> * Turns out it's *really* important not to
> * restore the signal handler here if we have real POSIX
>@@ -134,5 +147,5 @@
>
> void CatchChildLeaveStatus(void)
> {
>- CatchSignal(SIGCLD, sig_cld_leave_status);
>+ CatchSignal(SIGCLD, SIGNAL_CAST sig_cld_leave_status);
> }
>diff -u --recursive --new-file source/smbd/open.c source.new/smbd/open.c
>--- source/smbd/open.c Thu Dec 31 03:37:01 1998
>+++ source.new/smbd/open.c Sun Jan 24 23:32:32 1999
>@@ -225,8 +225,10 @@
> */
> pid_t wpid;
> int status_code;
>- if ((wpid = sys_waitpid(child_pid, &status_code, 0)) < 0) {
>- DEBUG(0,("check_access_allowed_for_current_user: The process is no
>longer waiting!\n"));
>+ while ((wpid = sys_waitpid(child_pid, &status_code, 0)) < 0) {
>+ if(errno == EINTR)
>+ continue;
>+ DEBUG(0,("check_access_allowed_for_current_user: The process is no
>longer waiting, errno = %d!\n", errno));
> CatchChild();
> return(False);
> }
>-----------------------------------
>
>
>------
>Panu Outinen Tel. +358 3 318 2500
>Vertex Systems Oy Fax +358 3 318 2450
>Vaajakatu 9 http://www.vertex.fi
>33720 Tampere, FINLAND email: Panu.Outinen at vertex.fi
>
>
>------------------------------
>
>Date: 25 Jan 99 03:58:40 +0100
>From: "Rask Ingemann Lambertsen" <rask at kampsax.k-net.dk>
>To: "Samba mailing list" <samba at samba.anu.edu.au>
>Subject: Re: Digest Only?
>Message-ID: <954.694T2019T2385187 at kampsax.k-net.dk>
>
>Den 23-Jan-99 14:05:57 skrev Ron Lavoie følgende om "Digest Only?":
>> Is this list only available in digest form only?
>
> No, fortunately not, digest is just the default because ???
>
> You can switch your subscription to individual messages by sending
>
> set samba mail ack
>
>(if you want to receive your own messages) or
>
> set samba mail noack
>
>(if you don't want to receive your own messages) to listproc at samba.org.
There
>are more options, try sending "help set" for a list and explanation.
>
>Regards,
>
>/¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯T¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯\
>| Rask Ingemann Lambertsen | E-mail: mailto:rask at kampsax.k-net.dk |
>| Registered Phase5 developer | WWW: http://www.gbar.dtu.dk/~c948374/ |
>| A4000, 775 kkeys/s (RC5-64) | "ThrustMe" on XPilot, ARCnet and IRC |
>| Reality is that which, when you stop believing in it, it still exists. |
>
>
>------------------------------
>
>Date: 24 Jan 1999 22:13:58 -0600
>From: Firebeard <stend+samba at sten.tivoli.com>
>To: samba at samba.org
>Subject: Problems running apps from Samba 2.0.0 share on NT 4.0
>Message-ID: <vpr9skm1kp.fsf at grendel.tivoli.com>
>
>
> Ever since I upgraded from Samba 1.9.18 to 2.0.0, I've been
>having problems with applications started from a Samba share dying
>silently, or with an Illegal Instruction message, on NT 4.0
>Workstation. Since the only configuration change has been the Samba
>upgrade, that would seem to be the orgin of the problem. Below is my
>smb.conf file, in case I have something configured (or not configured)
>which might be causing it. If you know of anything I can look for in
>the samba log (and what log level to use to get it), I would
>appreciate it.
>
># Samba config file created using SWAT
># from localhost (127.0.0.1)
># Date: 1999/01/21 23:55:35
>
># Global parameters
> workgroup = TIVOLI-NT
> server string = Sten Drescher's home SMB server
> security = SERVER
> encrypt passwords = Yes
> password server = austin2-nt arbor-nt haydn
> smb passwd file = /etc/smbpasswd
> username map = /etc/smb.username
> log level = 2
> log file = /var/log/samba-log.%m
> max log size = 50
> read bmpx = No
> socket options = TCP_NODELAY
> add user script = /usr/sbin/useradd %u
> local master = No
> wins server = 146.84.3.8
> lock dir = /var/lock/samba
> remote announce = 146.84.3.255/Tivoli-Support
146.84.110.255/Tivoli-Support
> create mask = 0644
>
>[homes]
> comment = Home Directories
> read only = No
> create mask = 0750
> browseable = No
>
>[printers]
> comment = All Printers
> path = /var/spool/samba
> create mask = 0700
> print ok = Yes
> browseable = No
>
>[winapps]
> comment = Windows Applications
> path = /winapps
> read only = No
> volume = Windows Applications
>
>[wingames]
> comment = Windows Games
> path = /wingames
> read only = No
> volume = Windows Games
>
>[cdrom0]
> comment = KeyFontsPro for Windows and Macintosh
> path = /mnt/cdrom
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom || /bin/mount /mnt/cdrom
> root postexec = /bin/umount /mnt/cdrom
> volume = CD-ROM 0
>
>[cdrom1]
> comment = USENIX 1997 Annual Technical Conference and USELINUX
> path = /mnt/cdrom1
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom1 || /bin/mount /mnt/cdrom1
> root postexec = /bin/umount /mnt/cdrom1
> volume = USENIX_Anaheim_97
>
>[cdrom2]
> comment = 11th Systems Administration Conference
> path = /mnt/cdrom2
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom2 || /bin/mount /mnt/cdrom2
> root postexec = /bin/umount /mnt/cdrom2
> volume = USENIX_LISA-97
>
>[cdrom3]
> comment = 1998 USENIX Annual Technical Conference
> path = /mnt/cdrom3
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom3 || /bin/mount /mnt/cdrom3
> root postexec = /bin/umount /mnt/cdrom3
> volume = USENIX_New_Orleans_98
>
>[cdrom4]
> comment = 12th Systems Administration Conference
> path = /mnt/cdrom4
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom4 || /bin/mount /mnt/cdrom4
> root postexec = /bin/umount /mnt/cdrom4
> volume = USENIX_LISA_98
>
>[cdrom5]
> comment = Java Reference Library
> path = /mnt/cdrom5
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom5 || /bin/mount /mnt/cdrom5
> root postexec = /bin/umount /mnt/cdrom5
> volume = JRL
>
>[cdrom6]
> comment = PalmPilot: The Ultimate Guide
> path = /mnt/cdrom6
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom6 || /bin/mount /mnt/cdrom6
> root postexec = /bin/umount /mnt/cdrom6
> volume = Ultimat_Pilot
>
>[cdrom7]
> comment = CD-ROM 7
> path = /mnt/cdrom7
> guest ok = Yes
> root preexec = /bin/mount /mnt/cdrom7 || /bin/mount /mnt/cdrom7
> root postexec = /bin/umount /mnt/cdrom7
> available = No
> volume = CD-ROM 7
>
>
>--
>#include <disclaimer.h> /* Sten Drescher */
>Unsolicited bulk email will be stored and handled for a US$500/KB fee.
>Amendment II, Revised: A well-regulated population being necessary to
>the security of a police state, the right of the Government to keep
>and destroy arms shall not be infringed.
>
>------------------------------
>
>End of SAMBA Digest 1954
>************************
More information about the samba
mailing list