Talk:Samba

From ArchWiki
Revision as of 09:31, 1 June 2012 by Fengchao (Talk | contribs) (Possible omission in the Installation section: Close old topic.)

Jump to: navigation, search

Missing Instructions

Any comment that claims something is easy, or simple or obvious is fine,.... as long as it is followed by the actual instructions and explanations to complete the task.

Editing a .conf file is exactly one of those tasks where detailed instructions are required. KitchM 00:52, 28 September 2009 (EDT)

Man page has the detailed instruction for this purpose. -- Fengchao (talk) 09:30, 1 June 2012 (UTC)

Possible omission in the Installation section

The Installation section states: "Installing only the client program is sufficient for systems that are not meant to share files, only access them". However installing just the smbclient package doesn't result in the creation of an /etc/samba/smb.conf file that apparently smbclient complains about if absent http://pastebin.com/f793e7a08 . An /etc/samba/smb.conf file is only created when one installs the 'samba' package as well. Please make the necessary edits. ~ erythrocyte Thu Feb 4 21:16:00 IST 2010

The article is correct; smbclient warns about a missing smb.conf, but still works fine (at least on my system).
Also, users only looking to access files will most likely be using mount.cifs that's included with the smbclient package (and doesn't complain about smb.conf).
-- pointone 11:38, 4 February 2010 (EST)
An interesting point. I have also been worried about these strange phrases popping up inappropriately. Do you think this should be mentioned upstream as a bug? - KitchM 12:59, 4 February 2010 (EST)

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)

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)

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): http://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)