I have Samba running on Suse 9.0 as a server. I also have a Sony notebook with Windows XP on it. When I access my Samba server thru the windows client /var/lib/nobody is the directory shared not my home directory. How can I have my home directory show up in the samba client? Why does the nobody directory show up? Here is my samba.conf file: # smb.conf is the main Samba configuration file. You find a full commented # version at /usr/share/doc/packages/samba/examples/smb.conf.SuSE # Date: 2003-09-23 [global] workgroup = WORKGROUP os level = 2 time server = Yes unix extensions = Yes encrypt passwords = yes map to guest = Bad User printing = CUPS printcap name = CUPS socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY wins support = No veto files = /*.eml/*.nws/riched20.dll/*.{*}/ security = user server string = Samba Server add user script = domain master = false domain logons = no local master = no preferred master = auto ;; ldap server = 127.0.0.1 [homes] comment = Home Directories valid users = %S browseable = yes read only = No create mask = 0640 directory mask = 0750 guest ok = yes printable = no [printers] comment = All Printers path = /var/tmp printable = yes create mask = 0600 browseable = no guest ok = no [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 browseable = yes guest ok = no printable = no
Jerome Lyles wrote:
I have Samba running on Suse 9.0 as a server. I also have a Sony notebook with Windows XP on it. When I access my Samba server thru the windows client /var/lib/nobody is the directory shared not my home directory. How can I have my home directory show up in the samba client? Why does the nobody directory show up?
Here is my samba.conf file:
# smb.conf is the main Samba configuration file. You find a full commented
<SNIP>
[homes] comment = Home Directories valid users = %S browseable = yes read only = No create mask = 0640 directory mask = 0750 guest ok = yes printable = no
<SNIP> You have changed this to make the home directory browsable. When a client first browses a server, it is done as nobody. You have not logged on to the server yet. The server has no way to tell who you are. You also are allowing guest access. Try the following: [homes] comment = Home Directories valid users = %S writable = Yes create mask = 0660 directory mask = 0770 browseable = No -- Louis D. Richards LDR Interactive Technologies
On Thursday 06 May 2004 03:27 am, Louis Richards wrote: <SNIP> I did as you suggested and also I added myself as a user using smbpasswd and it worked. Thank you Louis! I checked man chmod but couldn't find out what the modes you suggested I use mean. What are the create mask and directory mask functions? What are modes 0660 and 0750? And from one of your later emails (Samba Share - Access Denied) what does "chmod g+s /some directory do? Thanks again, Jerome
You have changed this to make the home directory browsable. When a client first browses a server, it is done as nobody. You have not logged on to the server yet. The server has no way to tell who you are. You also are allowing guest access. Try the following:
[homes] comment = Home Directories valid users = %S writable = Yes create mask = 0660 directory mask = 0770 browseable = No
--
Louis D. Richards LDR Interactive Technologies
On Thu, May 06, 2004 at 10:35:39PM -1000, Jerome Lyles wrote:
What are modes 0660 and 0750? And from one of your later emails (Samba Share - Access Denied) what does "chmod g+s /some directory do?
The 2nd number are the rights for the user, the 3rd for the group, and the 4th for all others. The numbers are 3 bits (value 0-7); the MSb is read access, the middle bit is write access, and the LSb is executable access. 660 = 110 110 000 = read/write access for user/group 750 = 111 101 000 = read/write/exec access for user, read/exec access for group g+s = set group id bit for the group, which causes files in that directory to get the group id of the directory i.s.o. the group id of the user that creates the file in that directory. Regards, Pieter Hulshoff
On Friday 07 May 2004 11.02, Pieter Hulshoff wrote:
On Thu, May 06, 2004 at 10:35:39PM -1000, Jerome Lyles wrote:
What are modes 0660 and 0750? And from one of your later emails (Samba Share - Access Denied) what does "chmod g+s /some directory do?
The 2nd number are the rights for the user, the 3rd for the group, and the 4th for all others.
and the first is the special bits 100 = SUID 010 = SGID 001 = Sticky
Anders Johansson wrote:
On Friday 07 May 2004 11.02, Pieter Hulshoff wrote:
On Thu, May 06, 2004 at 10:35:39PM -1000, Jerome Lyles wrote:
What are modes 0660 and 0750? And from one of your later emails (Samba Share - Access Denied) what does "chmod g+s /some directory do?
The 2nd number are the rights for the user, the 3rd for the group, and the 4th for all others.
and the first is the special bits
100 = SUID 010 = SGID 001 = Sticky
rwx rwx rwx = 7 7 7 for owner group other rwx = 4+2+1 = 7 which stands for read, write, and execute for a file or read, write, change into for a directory. I know it's a litle confusing at first, but stick with it. The extra bit about "setting the group" means that any files you create or change get owned by THAT group instead of your default group. This works great with the inherit permisions of samba. Imagine the following directories: directory owner group permisions ----------------------------------------- public root public rwx rws rwx Now without creating a new share in samba and assuming all users are in the "public" group, I make a subdirectory in public like: directory owner group permisions ----------------------------------------- accounts root accounts rwx rws --- Now everyone can get in public but only people in the group "accounts" can get into the subdirectory. This mimics the way many shares are set up in NT environments and still works with NFS. Less screaming when we drag them away from the dark side this way ;-) -- Louis D. Richards LDR Interactive Technologies
What are modes 0660 and 0750? And from one of your later
emails (Samba Share - Access Denied) what does "chmod g+s /some directory do? Thanks again, Jerome
On Thursday 06 May 2004 03:27 am, Louis Richards wrote: <SNIP> I did as you suggested and also I added myself as a user using smbpasswd and it worked. Thank you Louis! I checked man chmod but couldn't find out what the modes you suggested I use mean. What are the create mask and
The easiest way to think about it is that the four numbers of a mode
represent -- directory -- owner -- group -- world -- permissions. The
directory bit just signifies whether the filename is a file (0) or a
directory (1). The owner, group and world permissions are each defined by
the read, write and execute bits. (ie. dwrxwrxwrx) The mode numbers are just
short hand for setting the binary attributes of the read-write-execute
permissions you want. For the owner, group and world bits the numbers mean
the following:
# binary wrx permission
1 001 (--x) execute only
2 010 (-w-) write only
3 011 (-wx) write and execute
4 100 (r--) read only
5 101 (r-x) read and execute
6 110 (rw-) read and write
7 111 (rwx) read, write and execute
So chmod 0660 filename sets the file permission of filename to
-rw-rw----
That means owner has read/write and group has read/write and world has no
access
Similarly chmod 0750 filename sets the file permission of filename to
-rwx-r-x---
Which means owner has read/write/execute, group has read/execute and world
has no access.
If your not affecting the directory bit, you can omit the leading 0. So
chmod 660 is the same as chmod 0660.
Hope that helps...... Somebody add this to a man page somewhere........
--
David C. Rankin, J.D., P.E.
RANKIN * BERTIN, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankin-bertin.com
--
----- Original Message -----
From: "Jerome Lyles"
mask functions? What are modes 0660 and 0750? And from one of your later emails (Samba Share - Access Denied) what does "chmod g+s /some directory do? Thanks again, Jerome
You have changed this to make the home directory browsable. When a client first browses a server, it is done as nobody. You have not logged on to the server yet. The server has no way to tell who you are. You also are allowing guest access. Try the following:
[homes] comment = Home Directories valid users = %S writable = Yes create mask = 0660 directory mask = 0770 browseable = No
--
Louis D. Richards LDR Interactive Technologies
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 07 May 2004 16.32, David Rankin wrote:
What are modes 0660 and 0750? And from one of your later
emails (Samba Share - Access Denied) what does "chmod g+s /some directory
do?
Thanks again, Jerome
The easiest way to think about it is that the four numbers of a mode represent -- directory -- owner -- group -- world -- permissions. The directory bit just signifies whether the filename is a file (0) or a directory (1).
What? What? What? There is no such thing as a directory bit in the permissions. The leading number is an octet just like the other, I described it in my other mail, but here goes again 100 = File/Directory is SUID 010 = File/Directory is SGID 001 = File/Directory is sticky (means nothing for files, for directories means that only owner of file may modify file even though directory is world writable, ref: /tmp)
On Friday 07 May 2004 08:48 am, Anders Johansson wrote:
On Friday 07 May 2004 16.32, David Rankin wrote:
What are modes 0660 and 0750? And from one of your later
emails (Samba Share - Access Denied) what does "chmod g+s /some directory
do?
Thanks again, Jerome
The easiest way to think about it is that the four numbers of a mode represent -- directory -- owner -- group -- world -- permissions. The directory bit just signifies whether the filename is a file (0) or a directory (1).
What? What? What?
There is no such thing as a directory bit in the permissions.
The leading number is an octet just like the other, I described it in my other mail, but here goes again
100 = File/Directory is SUID 010 = File/Directory is SGID 001 = File/Directory is sticky (means nothing for files, for directories means that only owner of file may modify file even though directory is world writable, ref: /tmp)
If 001 means only the owner can change the file then the 'world' part of'world writable' means only the owner is the world, correct? Jerome
On Saturday 08 May 2004 08.11, Jerome Lyles wrote:
100 = File/Directory is SUID 010 = File/Directory is SGID 001 = File/Directory is sticky (means nothing for files, for directories means that only owner of file may modify file even though directory is world writable, ref: /tmp)
If 001 means only the owner can change the file then the 'world' part of'world writable' means only the owner is the world, correct? Jerome
No. Normally when you make a directory world writable, anyone can delete or rename anything in that directory, no matter who created it. Try it. Create a directory with mode 777, create a file in there as root, then try to delete or rename it as your regular user. Works a charm, doesn't it? Deleting or renaming works on the directory, not on the actual file. However, if you make the directory sticky with mode 1777, only the owner of the file may delete or rename it. This is how /tmp works
On Sat, 2004-05-08 at 02:23, Anders Johansson wrote:
On Saturday 08 May 2004 08.11, Jerome Lyles wrote:
100 = File/Directory is SUID 010 = File/Directory is SGID 001 = File/Directory is sticky (means nothing for files, for directories means that only owner of file may modify file even though directory is world writable, ref: /tmp)
If 001 means only the owner can change the file then the 'world' part of'world writable' means only the owner is the world, correct? Jerome
No. Normally when you make a directory world writable, anyone can delete or rename anything in that directory, no matter who created it. Try it. Create a directory with mode 777, create a file in there as root, then try to delete or rename it as your regular user. Works a charm, doesn't it? Deleting or renaming works on the directory, not on the actual file.
However, if you make the directory sticky with mode 1777, only the owner of the file may delete or rename it. This is how /tmp works
Branching off a bit. What files\directories in /tmp can you get rid of? Mike
Excellent! Yes it helps very much. Thank you. Jerome On Friday 07 May 2004 04:32 am, David Rankin wrote:
What are modes 0660 and 0750? And from one of your later
emails (Samba Share - Access Denied) what does "chmod g+s /some directory
do?
Thanks again, Jerome
The easiest way to think about it is that the four numbers of a mode represent -- directory -- owner -- group -- world -- permissions. The directory bit just signifies whether the filename is a file (0) or a directory (1). The owner, group and world permissions are each defined by the read, write and execute bits. (ie. dwrxwrxwrx) The mode numbers are just short hand for setting the binary attributes of the read-write-execute permissions you want. For the owner, group and world bits the numbers mean the following:
# binary wrx permission 1 001 (--x) execute only 2 010 (-w-) write only 3 011 (-wx) write and execute 4 100 (r--) read only 5 101 (r-x) read and execute 6 110 (rw-) read and write 7 111 (rwx) read, write and execute
So chmod 0660 filename sets the file permission of filename to
-rw-rw----
That means owner has read/write and group has read/write and world has no access
Similarly chmod 0750 filename sets the file permission of filename to
-rwx-r-x---
Which means owner has read/write/execute, group has read/execute and world has no access.
If your not affecting the directory bit, you can omit the leading 0. So chmod 660 is the same as chmod 0660.
Hope that helps...... Somebody add this to a man page somewhere........
-- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankin-bertin.com -- ----- Original Message ----- From: "Jerome Lyles"
To: Sent: Friday, May 07, 2004 3:35 AM Subject: Re: [SLE] Nobody is home in Samba [Solved] On Thursday 06 May 2004 03:27 am, Louis Richards wrote: <SNIP> I did as you suggested and also I added myself as a user using smbpasswd
and
it worked. Thank you Louis! I checked man chmod but couldn't find out
what
the modes you suggested I use mean. What are the create mask and
directory
mask functions? What are modes 0660 and 0750? And from one of your later emails (Samba Share - Access Denied) what does "chmod g+s /some directory
do?
Thanks again, Jerome
You have changed this to make the home directory browsable. When a client first browses a server, it is done as nobody. You have not logged on to the server yet. The server has no way to tell who you are. You also are allowing guest access. Try the following:
[homes] comment = Home Directories valid users = %S writable = Yes create mask = 0660 directory mask = 0770 browseable = No
--
Louis D. Richards LDR Interactive Technologies
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (6)
-
Anders Johansson
-
David Rankin
-
Jerome Lyles
-
Louis Richards
-
Mike McMullin
-
Pieter Hulshoff