Hello,
I apologize for this simple question, but I am frustrated by my
inabillity to solve this problem. I'm running Samba v1.9.16p11 on an Ultra
Sparc using Solaris 2.5.1. When Win95/NT clients create files or folders
on a share, the protections are set so only the user has write access. I
want Group write access.
I did RTFM, and tried to set create mask (or mode, I tried both) in
the smb.conf, but in my log file I get the following error: Ignoring badly
formed line: create mask 0775. I then tried force create mask, etc, but I
always get the same badly formed line error. Will somebody please tell me
what I'm doing wrong?
I have been using Samba for 3-4 years, and love it. You people
should be proud of yourselves for developing and supporting such a useful
program. Of course, now that I have to administer samba, I have these
questions.
Thanks,
Eric
On Fri, 12 Feb 1999 Eric_Songer@urscorp.com wrote:> the smb.conf, but in my log file I get the following error: Ignoring badly > formed line: create mask 0775. I then tried force create mask, etc, but IShould this be "create mask = 0775"? ^ B _____________________________________________________________________________ B r i a n L a l o r blalor@hcirisc.cs.binghamton.edu http://hcirisc.cs.binghamton.edu/~blalor Spam me not. To get my pgp key, put "get pgp key" in the subject of your message "Beer is living proof that God loves us and wants to see us happy" -- Benjamin Franklin
Hi dear friends I have Linux Slackware running Samba. I have two Ethernet networks connected by two LAN cards to Linux and PPP connection by leased line to my ISP. I have no file server on my LANs and I want Samba to be my file server and bridge between the Ethernets. In this moment I have routing between Ethernets, but the users from the first LAN cannot see the users from other LAN. I think I need to have configured Samba as WINS server or something else ?! Can somebody help me to configure Samba for this reason ? Sincerely yours Tonych ----------------------------------------------------------------------------- E-mail: tony@soft-press.com; tdobrev@usa.net ICQ UIN: 9091250 GSM: ++359-(0)88-80 55 93 Office Phone: ++359-(0)2-96 32 900; 65 79 97 Toncho Dobrev -----------------------------------------------------------------------------
When the world was young, Eric_Songer@urscorp.com carved some runes like this:> Ultra Sparc using Solaris 2.5.1. When Win95/NT clients create files or > folders on a share, the protections are set so only the user has write > access. I want Group write access.Then the group (that the desired users belong to under Solaris) must own the directory tree that you're exporting as a samba share (make sure it's not owned by root). Depending on whether or not you set the sticky bit on the directory, you can have group read/write access, or group write (where only the file owner can modify).> I did RTFM, and tried to set create mask (or mode, I tried both) in > the smb.conf, but in my log file I get the following error: Ignoring > badly formed line: create mask 0775. I then tried force create mask, etc, > but I always get the same badly formed line error. Will somebody please > tell me what I'm doing wrong?You forgot the equals sign (as in "create mode = 0775). Feel like Homer yet? (Doh! :-p) Steve
At 03:39 12/02/99 +1100, you wrote:> >From: "Daryl L. Biberdorf" <darylb@pobox.com> > >We're having an interesting problem at our >site.[snip]>I'm wondering if an outage between >us and the DNS would result in this kind of failure.Linux sockets seem to react badly to DNS problems - an inability to resolve a name causes the socket opening to hang for about 2 minutes before continuing. I haven't worked out why this is yet - I just disabled DNS resolution altogether (my system isn't part of the 'real' internet). If your DNS is screwed up lots of TCP/IP stuff will break as well as Samba. A good test is to telnet to the Linux box from a computer that isn't in the hosts file - if the connection attempt hangs for a couple of minutes before giving you a login prompt, DNS is stuffed. smbclient -L SERVERNAME will also (probably) hang, while smbclient -L SERVER-IP-ADDRESS will work correctly. I also had unrelated but superficially similar problems with keepalive packets - these weren't being sent by default so when a workstation rebooted Samba didn't always see it and netbios name resolution broke. If this happens you'll be able to see the server (sometimes) but not its shares (sometimes). Enable 'socket options = SO_KEEPALIVE' and 'keep alive = 60' in smb.conf to fix this. If you figure out a way to make Linux time out faster when DNS is broken I'd appreciate an email! Best regards, Paul Paul Sherwin Consulting 22 Monmouth Road, Oxford OX1 4TD, UK Phone +44 (0)1865 721438 Fax +44 (0)1865 434331 Pager +44 (0)7666 797228