SAMBA digest 2240

Kenny Cho Kenny.Cho at Corp.Sun.COM
Wed Sep 22 17:18:25 GMT 1999


OK, thanks for the info, but that exactly what I DON'T want to do.  Basically 
this is what I want to do.
 
- Map a user's home directory using \\samba_server\unix_login (that's 
successful)
- Basically let the user copy a file over to his home directory w/out setting 
that file to owner:nobody (i.e copy a file over to his samba mounted home 
directory using userlogin as the owner of the file).

I've been successful using v,1.9.18a but not 2.0.4b, I believe it's because I 
ended up downloading the binaries that doesn't have the shadow password support. 
 So my other question is how do I know if the smb binaries that I download has 
that support?

Kenny

>Date: Wed, 22 Sep 1999 16:24:44 +0530
>From: Ganesh S P <ganesh at procsys.com>
>MIME-Version: 1.0
>To: samba at samba.org
>CC: Kenny Cho <Kenny.Cho at Corp.Sun.COM>
>Subject: Re: SAMBA digest 2240
>Content-Transfer-Encoding: 7bit
>
>>
>
>Hi,
>Check if the shared directory has the write permission for all. i.e. chmod 777 
for
>the particular directory
>
>
>
>> Date:   Sun, 19 Sep 1999 21:06:36 -0700
>> From:   Kenny Cho <Kenny.Cho at Corp.Sun.COM>
>> To:     samba at samba.org
>> Subject: Problem copying files to samba mount.
>> Message-ID: <37E5B2CC.9ADC9F8A at ha1pal.corp.sun.com>
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=us-ascii
>> Content-Transfer-Encoding: 7bit
>>
>> Hi Samba Gurus,
>>
>> Here's my problem.
>>
>> I"m running samba 2.0.4a on solaris 7.  Any windows client can mount
>> their home directory OK via (\\samba_server\unix_login_name).  They can
>> also pull data out of their samba mounted home directories OK.  But if
>> the vice versa scenario happens, 2 things either happen.  I either get
>> an "access denied error, Make sure the disk is not write-protected or
>> the disk is full", or if it does copy the file over, it doesn't set it
>> to the right owner and permissions.  I just upgraded the samba version
>> from 1.9.14 and I've never had this problem.  I'm wondering if it's a
>> version incompatibility w/ samba and if there were any default changes
>> on some of the flags.  Here's my smb.conf file concerning the global and
>> homes shares.
>>
>> [global]
>>    wins support = no
>>    wins server = 129.144.174.80
>>    printing = sysv
>>    printcap name = /etc/opt/samba/printcap-samba
>>    load printers = yes
>>    guest account = nobody
>>    preserve case = yes
>>    short preserve case = yes
>>    status = yes
>>    security = share
>>    read prediction = yes
>>    socket options = TCP_NODELAY
>>    share modes = no
>>    netbios aliases = pc-cup03 saccharine
>>    workgroup = green
>>    local master = no
>>    guest ok = yes
>>    server string = "UNIX File/Print services for CUP-03"
>>    interfaces = 129.144.54.21/255.255.255.0 129.144.55.21/255.255.255.0
>> 129.144.
>> 56.21/255.255.255.0 129.144.57.21/255.255.255.0
>> 129.144.94.21/255.255.255.0 129.
>> 144.95.21/255.255.255.0
>>
>> [homes]
>>    comment = Home Directories
>>    read only = no
>>    create mode = 0750
>>
>> Any help is very appreciated.
>>
>> Kenny Cho
>> IR systems administrator, IT Operations
>> Sun Microsystems, Palo Alto
>>
>> ------------------------------
>>
>

---------------------------------------------------
Kenny Cho		
System Administrator, IT Operations
Sun Microsystems, Inc, Palo Alto
Phone:x67458 or (650) 336-7458 
EMail:kenny.cho at sun.com
---------------------------------------------------



More information about the samba mailing list