Setup Samba server on Centos 6.2

After a long struggle I finally figured out how to setup a Samba server on Centos 6.2. Since Centos 6.2 doesn't have the Samba configuration GUI anymore I didn't know how to set it up. But after a lot of trial and error and my friend Google I manages to get it up and running without disabling SELinux :-).

On a fresh installation of Centos 6.2 you need to follow the following steps:

  1. Install semanage with yum
    yum -y install policycoreutils-python
  2. Configure the samba configuration file: /etc/samba/smb.conf
    [global]
    workgroup = yourworkgroupname
    server string = yourservername
    security = user
    passdb backend = tdbsam
  3. Configure your share in the same file
    [share]
    path = /your/share/path
    writable = yes
    guest ok = yes
  4. Set your samba password for your user by logging in with that user on the target machine and execute the following command:
    smbpasswd
  5. Open the Samba ports on your firewall [139/tcp,445/tcp,137/udp,138/udp]
  6. Now it's time for configuring SELinux. Enable the domain controller by executing the following command:
    setsebool -P samba_domain_controller on
  7. If you want home directories to be shared also execute the following directory:
    setsebool -P samba_enable_home_dirs on
  8. Now you need to use some semanage magic to complete the configuration by executing the following command:
    semanage fcontext -a -t samba_share_t '/shared/path(/.*)?'
  9. And than you need to also execute the following command
    restorecon -R /shared/path
  10. Now the only thing you have to do is start the following samba services:
    - nmb
    - smb

Comments

Post a Comment

Popular posts from this blog

Tomcat behind Apache HTTP server using Spring Security

Since I have been struggling with applications not working properly behind Apache HTTP server that use Spring Security I dedicated this blog to this issue. When you develop an application using Spring security this works fine when just running on a Tomcat server e.g. http://localhost:8080/app-context/. The problems start when you want to setup your environment properly by adding an Apache HTTP server in front of it using proxy AJP. You would start by adding the following to your apache config file: ProxyPass /app-context/ ajp://localhost:8009/app-context/ This works fine when trying to go to http://servername/app-context/ but when you try to login you will be redirected back to the login page everytime. To avoid this behavior you need to add the following line to your Apache configuration: ProxyPass /app-context/j_spring_security_check ajp://localhost:8009/app-context/j_spring_security_check For some reason it doesn't work without this line which seems weird to me since you basical...
Read more

Fastest XML parser

In most applications you need to do some XML parsing to either provide XML to external systems or parse XML from external systems or of course both. Since the systems I work on use a lot of XML and they need to be as fast as possible I did some tests on several XML parsers. I tested the following parsers/XML frameworks: JDom Piccolo StaxMate XStream JAXB 2.1 All parsers were tested in isolation with the following parameters: 25 threads running simultaniously Every thread calls the parser 100 times The results are as follows. JDom Avg. parsing time: 325.24 ms Avg. memory usage: 307 KB Piccolo Avg. parsing time: 88.08 ms Avg. memory usage: 454 KB StaxMate Avg. parsing time: 96.16 ms Avg. memory usage: 203 KB XStream Avg. parsing time: 77.04 ms Avg. memory usage: 319 KB Jaxb 2.1 Avg. parsing time: 1778.12 ms Avg. memory usage: 618 KB As you can see XStream is the fastest one of them all. The total ranking of the parsers you can find below: XStream Piccolo StaxMate JDom JAXB 2.1 ...
Read more

Configure Tomcat as a deamon on Linux

Since I keep on forgetting how to do this I decided to put this on my blog to make it easier for me and other people that have the same issue as me. It's pretty simple actually but yesterday I caught myself forgetting how it needs to be done. Basically you need to follow to following steps to successfully. Step 1 - Creating startup deamon file You can take the following file and adjust it accordingly. You have to create this file in /etc/init.d/. #Jenkins startup script #!/bin/sh -e #Jenkins startup script #chkconfig: 2345 80 05 #description: Jenkins CI # Define some variables # Name of app APP=Jenkins # Name of the user to run as USER=tomcat # Location of application's bin directory BASE=/var/tomcat/instances/jenkins # Location of Java JDK export JAVA_HOME=/opt/java/jdk1.6.0_11 case "$1" in # Start command start) echo "Starting $APP" /bin/su -m $USER -c "cd $BASE/logs && $BASE/bin/startup.sh &> /dev/null" ;; # Stop...
Read more