Difference between revisions of "Talk:Samba"

From ArchWiki
Jump to: navigation, search
m (security = share deprecated)
(Merge)
(14 intermediate revisions by 9 users not shown)
Line 2: Line 2:
  
 
The line states in part: "If xinetd was compiled with tcpwrapper flag enabled".  Does anyone know how one might know if this is the case? - [[User:KitchM|KitchM]] 00:18, 24 March 2010 (EDT)
 
The line states in part: "If xinetd was compiled with tcpwrapper flag enabled".  Does anyone know how one might know if this is the case? - [[User:KitchM|KitchM]] 00:18, 24 March 2010 (EDT)
 +
 +
:: It is currently compiled without tcpwrapper support, as that has been deprecated from the distro. Moving on to use systemd sockets rather than go through xinetd seems wiser.
  
 
When I started xinetd according to instructions I got this message in everything.log: "Port not specified and can't find service: swat with getservbyname"
 
When I started xinetd according to instructions I got this message in everything.log: "Port not specified and can't find service: swat with getservbyname"
 
Portnumber was not set in the default SWAT configuration file /etc/xinetd.d/swat.
 
Portnumber was not set in the default SWAT configuration file /etc/xinetd.d/swat.
 
I added the line "port = 901". When I restarted xinetd I got the message "service/protocol combination not in /etc/services: swat/tcp". I selected an unassigned number and added the line "swat 1001/tcp" in /etc/services. I changed port number to 1001 in /etc/xinetd.d/swat. Now I could log into SWAT on http://localhost:1001. [[User:Erlhel|Erlhel]] 18:45, 7 April 2012 (EDT)
 
I added the line "port = 901". When I restarted xinetd I got the message "service/protocol combination not in /etc/services: swat/tcp". I selected an unassigned number and added the line "swat 1001/tcp" in /etc/services. I changed port number to 1001 in /etc/xinetd.d/swat. Now I could log into SWAT on http://localhost:1001. [[User:Erlhel|Erlhel]] 18:45, 7 April 2012 (EDT)
 +
 +
:: related topic here:
 +
:: https://bbs.archlinux.org/viewtopic.php?pid=1276428#p1276428
 +
 +
:: I've updated the wiki section on SWAT to reflect the systemd option that doesn't require xinetd. Please review--[[User:Stefanwilkens|stefanwilkens]] ([[User talk:Stefanwilkens|talk]]) 13:46, 22 May 2013 (UTC)
 +
 +
::: After review, I've also opted to remove the xinetd middleman method. This duplicated systemd's socket feature by letting xinetd monitor the socket and then starting xinetd through systemd. It seemed needlessly double to me. --[[User:Stefanwilkens|stefanwilkens]] ([[User talk:Stefanwilkens|talk]]) 12:43, 26 May 2013 (UTC)
  
 
== Share Access ==
 
== Share Access ==
Line 12: Line 21:
 
:As I read it, the difference is made between KDE and Gnome's graphical file managers (3.2) and from commandline (3.3). On the other hand, gvfs belongs to gnome - all a tad confusing. See my post below for a suggestion on how to rewrite that bit. [[User:Hokasch|Hokasch]] 12:02, 18 May 2010 (EDT)
 
:As I read it, the difference is made between KDE and Gnome's graphical file managers (3.2) and from commandline (3.3). On the other hand, gvfs belongs to gnome - all a tad confusing. See my post below for a suggestion on how to rewrite that bit. [[User:Hokasch|Hokasch]] 12:02, 18 May 2010 (EDT)
 
::Thanks; very nice!  I'm totally with you on this.  In fact, what if someone uses a different file manager?  Why are there so many different network browser mechanisms?  Why so many different network protocols?  Etc., etc..  I picked Ext3 only once when I installed the OS, and I didn't even have to configure that.  I was able to connect to the Internet with little work.  But to hook my computer to another one on my own LAN, I've got to jump thru hoops.  That bugs the heck out of me.  There's got to be a better way. - [[User:KitchM|KitchM]] 01:43, 19 May 2010 (EDT)
 
::Thanks; very nice!  I'm totally with you on this.  In fact, what if someone uses a different file manager?  Why are there so many different network browser mechanisms?  Why so many different network protocols?  Etc., etc..  I picked Ext3 only once when I installed the OS, and I didn't even have to configure that.  I was able to connect to the Internet with little work.  But to hook my computer to another one on my own LAN, I've got to jump thru hoops.  That bugs the heck out of me.  There's got to be a better way. - [[User:KitchM|KitchM]] 01:43, 19 May 2010 (EDT)
::: I am not aware of other filebrowsers that can browse/mount shares on the fly. With thunar and fluxbox, I used some of the solutions mentioned later (fusesmb or so). Look here for some quick adjustments (didnt' want to mess up the paragraphs on the official page for now): http://wiki.archlinux.org/index.php/User:Hokasch/Samba[[User:Hokasch|Hokasch]] 08:31, 19 May 2010 (EDT)
+
::: I am not aware of other filebrowsers that can browse/mount shares on the fly. With thunar and fluxbox, I used some of the solutions mentioned later (fusesmb or so). Look here for some quick adjustments (didnt' want to mess up the paragraphs on the official page for now): https://wiki.archlinux.org/index.php/User:Hokasch/Samba[[User:Hokasch|Hokasch]] 08:31, 19 May 2010 (EDT)
 
::::The issue is actually that the underlying services are not correctly done.  For instance, if the user wishes to access a network share, the only thing that must be there (besides the other computers being turned on and physically connected to the LAN) is for the proper service to be running so that the OS knows that the computers are available.  All file managers should then be able to see the shares available.  This should be automatic.
 
::::The issue is actually that the underlying services are not correctly done.  For instance, if the user wishes to access a network share, the only thing that must be there (besides the other computers being turned on and physically connected to the LAN) is for the proper service to be running so that the OS knows that the computers are available.  All file managers should then be able to see the shares available.  This should be automatic.
  
Line 30: Line 39:
 
:(Please sign your edits in discussion pages with {{ic|<nowiki>~~~~</nowiki>}})
 
:(Please sign your edits in discussion pages with {{ic|<nowiki>~~~~</nowiki>}})
 
:I think you have a point, _netdev should probably be added to the mount options. -- [[User:Kynikos|Kynikos]] 06:15, 13 December 2011 (EST)
 
:I think you have a point, _netdev should probably be added to the mount options. -- [[User:Kynikos|Kynikos]] 06:15, 13 December 2011 (EST)
 +
{{ic|<nowiki>~~~~</nowiki>}}
 +
:The fstab setting "comment=systemd.automount" does not work with mount.cifs "comment" or x-sysmted.* is not mentioned in the man-page of mount.cifs. -- [[User:Some1|Some1]] 22:05 22.Nov 2013
  
 
 
== Messy ==
 
== Messy ==
  
Line 51: Line 61:
  
 
== security <nowiki>=</nowiki> share deprecated ==
 
== security <nowiki>=</nowiki> share deprecated ==
{{ic|security <nowiki>=</nowiki> share}} is deprecated as of December 2010, apparently. (see more at [http://lists.samba.org/archive/samba/2010-December/160046.html Samba mailing list] [[User:Zachera|Zachera]]) ([[User talk:Zachera|talk]]) 10:22, 13 January 2013 (UTC)
+
{{ic|security <nowiki>=</nowiki> share}} is deprecated as of December 2010, apparently. (see more at [http://lists.samba.org/archive/samba/2010-December/160046.html Samba mailing list]) [[User:Zachera|Zachera]] ([[User talk:Zachera|talk]]) 10:22, 13 January 2013 (UTC)
 +
 
 +
== Fixing this Article ==
 +
 
 +
I am trying to fix this article, see [[User:Axanon/sandbox/Samba]] for my current progress. Suggestions and comments can be made here: [[User talk:Axanon/sandbox/Samba]].
 +
 
 +
Goals:
 +
# Clean up grammar.
 +
# Organize sections for better flow.
 +
# Remove duplicate information.
 +
# Split troubleshooting and tips to: Samba/troubleshooting and Samba/Tips and tricks.
 +
[[User:Axanon|Axanon]] ([[User talk:Axanon|talk]]) 20:25, 23 January 2013 (UTC)
 +
 
 +
== fuse module no longer needed to load? ==
 +
<div style="border-style: dotted;">
 +
and load the {{ic|fuse}} [[kernel module]]:
 +
{{bc|# modprobe fuse}}
 +
</div>
 +
 
 +
Seems like this step is no longer needed as that module is automatically loaded on my machine. Should we remove this? [[User:Axper|axper]] ([[User talk:Axper|talk]]) 17:18, 27 August 2013 (UTC)
 +
 
 +
== Outdated information ==
 +
 
 +
Firstly, security = share is now completely removed, and as such, is ignored when parsed.
 +
 
 +
Secondly, "systemctl start samba" fails to start the service. Checking the log file yields this message:
 +
<pre>  At this time the 'samba' binary should only be used for either:
 +
  'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote'
 +
  You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks
 +
</pre>
 +
 
 +
I will remove the suggestions to use the samba service, as they misled me.
 +
[[User:Dawmail333|Dawmail333]] ([[User talk:Dawmail333|talk]]) 11:30, 4 September 2013 (UTC)
 +
 
 +
:For the record, this is the edit that introduced the mention of the samba service: [https://wiki.archlinux.org/index.php?title=Samba&diff=271999&oldid=271958].
 +
:This is the edit that removed it: [https://wiki.archlinux.org/index.php?title=Samba&curid=5021&diff=274343&oldid=273530&rcid=386073].
 +
:The first edit's summary links to http://www.samba.org/samba/history/samba-4.0.0.html
 +
:I don't have an up-to-date knowledge of Samba and integration with Windows networks in general, but this all seems strictly related to [[Active Directory Integration]], that's also why I've requested the merge of the articles.
 +
:-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:56, 5 September 2013 (UTC)
 +
::I wasn't the first to mention the samba service, it was introduced one revision earlier. I made the edit because i found the prev. version confusing. As to if what i wrote was correct, i admit i didn't test it myself due to time constraint. If it doesn't work as advertised, then good riddance.
 +
::The "AD Integration" article was quite helpful to me recently, there is a lot of info in there. I think it should stay as separate article. There is quite a clear topical separation here. The "Ad Int." article is specifically about setting up a linux-host to join a AD/Kerbereros Domain. The necessary Samba config is just one part of it, it also talks about kerberos and setting up the PAM config correctly.
 +
::[[User:Bwid|Bwid]] ([[User talk:Bwid|talk]]) 17:37, 5 September 2013 (UTC)
 +
 
 +
:::Ok, thanks for explaining, let's leave the article like it is, I've also withdrawn my merge requests. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:42, 8 September 2013 (UTC)
 +
 
 +
== Merge with Troubleshooting ==
 +
 
 +
Why there was [[Talk:Samba#Fixing this Article|splitting]]? I think, a good idea is to add [[Samba/Troubleshooting]] in the end of this article -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 05:41, 28 January 2014 (UTC)

Revision as of 05:41, 28 January 2014

SWAT

The line states in part: "If xinetd was compiled with tcpwrapper flag enabled". Does anyone know how one might know if this is the case? - KitchM 00:18, 24 March 2010 (EDT)

It is currently compiled without tcpwrapper support, as that has been deprecated from the distro. Moving on to use systemd sockets rather than go through xinetd seems wiser.

When I started xinetd according to instructions I got this message in everything.log: "Port not specified and can't find service: swat with getservbyname" Portnumber was not set in the default SWAT configuration file /etc/xinetd.d/swat. I added the line "port = 901". When I restarted xinetd I got the message "service/protocol combination not in /etc/services: swat/tcp". I selected an unassigned number and added the line "swat 1001/tcp" in /etc/services. I changed port number to 1001 in /etc/xinetd.d/swat. Now I could log into SWAT on http://localhost:1001. Erlhel 18:45, 7 April 2012 (EDT)

related topic here:
https://bbs.archlinux.org/viewtopic.php?pid=1276428#p1276428
I've updated the wiki section on SWAT to reflect the systemd option that doesn't require xinetd. Please review--stefanwilkens (talk) 13:46, 22 May 2013 (UTC)
After review, I've also opted to remove the xinetd middleman method. This duplicated systemd's socket feature by letting xinetd monitor the socket and then starting xinetd through systemd. It seemed needlessly double to me. --stefanwilkens (talk) 12:43, 26 May 2013 (UTC)

Share Access

Is the implication with the difference between KDE and Gnome on accessing shares that other DE's need special configurations as well? - KitchM 02:06, 7 May 2010 (EDT)

As I read it, the difference is made between KDE and Gnome's graphical file managers (3.2) and from commandline (3.3). On the other hand, gvfs belongs to gnome - all a tad confusing. See my post below for a suggestion on how to rewrite that bit. Hokasch 12:02, 18 May 2010 (EDT)
Thanks; very nice! I'm totally with you on this. In fact, what if someone uses a different file manager? Why are there so many different network browser mechanisms? Why so many different network protocols? Etc., etc.. I picked Ext3 only once when I installed the OS, and I didn't even have to configure that. I was able to connect to the Internet with little work. But to hook my computer to another one on my own LAN, I've got to jump thru hoops. That bugs the heck out of me. There's got to be a better way. - KitchM 01:43, 19 May 2010 (EDT)
I am not aware of other filebrowsers that can browse/mount shares on the fly. With thunar and fluxbox, I used some of the solutions mentioned later (fusesmb or so). Look here for some quick adjustments (didnt' want to mess up the paragraphs on the official page for now): https://wiki.archlinux.org/index.php/User:Hokasch/SambaHokasch 08:31, 19 May 2010 (EDT)
The issue is actually that the underlying services are not correctly done. For instance, if the user wishes to access a network share, the only thing that must be there (besides the other computers being turned on and physically connected to the LAN) is for the proper service to be running so that the OS knows that the computers are available. All file managers should then be able to see the shares available. This should be automatic.
Why should a person have to use a network browser, such as Avahi or LinNeighborhood? If those work, then the file manager should be able to handle that as well. Right now, if I use one of these to mount a network share, then any file manager can see that item and automatically list it in the directory tree. Since my file manager (XFE) can mount and unmount things, there is only one part missing, and that isn't the fault of the file manager. - KitchM 13:46, 24 May 2010 (EDT)

Rearrangement

It might be a very helpful thing for an expert on the subject to work this whole article over in a better arrangement of the process. I have found that the comments here point out a few issues, and my experience notes a couple things. I found the following basic outline: 1. install, 2. configure smb.conf, 3. start daemons, 4. add users, 5. access shares from other computers on LAN, and 6. mounting those shares

What seems to be left out are: 1. more smb.conf details, 2. creating shares, 3. making them available for other computers, and ?

_netdev mount option

when adding a share to /etc/fstab, wouldn't adding _netdev be a good idea?

(Please sign your edits in discussion pages with ~~~~)
I think you have a point, _netdev should probably be added to the mount options. -- Kynikos 06:15, 13 December 2011 (EST)

~~~~

The fstab setting "comment=systemd.automount" does not work with mount.cifs "comment" or x-sysmted.* is not mentioned in the man-page of mount.cifs. -- Some1 22:05 22.Nov 2013

Messy

This page is a bit of a mess.. KDE file sharing it at the bottom but numerious deprecated method are listed in the main article..

smb.conf file required for smbclient?

I get an error (warning) when I try to use smbclient without Samba server on that client? Should the wiki be updated to clarify the necessity of smb.conf on smbclient installs only? The wiki is confusing to me because it appears that smb.conf is not required for smbclient only installs.

Error below:

params.c:OpenConfFile() - Unable to open configuration file "/etc/samba/smb.conf":
	No such file or directory
smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it

Forgive me, this is my first talk entry.Stevepa (talk) 18:43, 2 December 2012 (UTC)

I tried the smbclient -L command and also got this message. I suspect it is just an overly talkative program rather than an indication of an error. Might be worth mentioning this, unless someone knows how a missing config file could cause a real problem. Vadmium (talk) 01:58, 3 December 2012 (UTC).

security = share deprecated

security = share is deprecated as of December 2010, apparently. (see more at Samba mailing list) Zachera (talk) 10:22, 13 January 2013 (UTC)

Fixing this Article

I am trying to fix this article, see User:Axanon/sandbox/Samba for my current progress. Suggestions and comments can be made here: User talk:Axanon/sandbox/Samba.

Goals:

  1. Clean up grammar.
  2. Organize sections for better flow.
  3. Remove duplicate information.
  4. Split troubleshooting and tips to: Samba/troubleshooting and Samba/Tips and tricks.

Axanon (talk) 20:25, 23 January 2013 (UTC)

fuse module no longer needed to load?

and load the fuse kernel module:

# modprobe fuse

Seems like this step is no longer needed as that module is automatically loaded on my machine. Should we remove this? axper (talk) 17:18, 27 August 2013 (UTC)

Outdated information

Firstly, security = share is now completely removed, and as such, is ignored when parsed.

Secondly, "systemctl start samba" fails to start the service. Checking the log file yields this message:

  At this time the 'samba' binary should only be used for either:
  'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote'
  You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks

I will remove the suggestions to use the samba service, as they misled me. Dawmail333 (talk) 11:30, 4 September 2013 (UTC)

For the record, this is the edit that introduced the mention of the samba service: [1].
This is the edit that removed it: [2].
The first edit's summary links to http://www.samba.org/samba/history/samba-4.0.0.html
I don't have an up-to-date knowledge of Samba and integration with Windows networks in general, but this all seems strictly related to Active Directory Integration, that's also why I've requested the merge of the articles.
-- Kynikos (talk) 09:56, 5 September 2013 (UTC)
I wasn't the first to mention the samba service, it was introduced one revision earlier. I made the edit because i found the prev. version confusing. As to if what i wrote was correct, i admit i didn't test it myself due to time constraint. If it doesn't work as advertised, then good riddance.
The "AD Integration" article was quite helpful to me recently, there is a lot of info in there. I think it should stay as separate article. There is quite a clear topical separation here. The "Ad Int." article is specifically about setting up a linux-host to join a AD/Kerbereros Domain. The necessary Samba config is just one part of it, it also talks about kerberos and setting up the PAM config correctly.
Bwid (talk) 17:37, 5 September 2013 (UTC)
Ok, thanks for explaining, let's leave the article like it is, I've also withdrawn my merge requests. -- Kynikos (talk) 10:42, 8 September 2013 (UTC)

Merge with Troubleshooting

Why there was splitting? I think, a good idea is to add Samba/Troubleshooting in the end of this article -- Kycok (talk) 05:41, 28 January 2014 (UTC)