Saturday Aug 25, 2007

SAMBA and SWAT in Solaris 10 Update 4 (Solaris 10 8/07)

I have previously blogged on how to enable SAMBA and SWAT as shipped with Solaris 10.

In Solaris 10 Update 4 (AKA Solaris 10 8/07 - available real soon now) Sun is shipping SAMBA 3.0.25a, and for the first time we are supporting SAMBA's Active Directory Service (ADS) integration.

What caught me out when I installed this new release of Solaris was that the way you stop and start SAMBA and SWAT have changed.

SAMBA processes are now managed using the Service Management Facility (SMF). You configure SAMBA as before, but to start the services you type:

root# svcadm enable samba wins

To stop SAMBA.........

root# svcadm disable samba wins

To check the status of the services....

root# svcs samba wins
STATE          STIME    FMRI
online         Aug_24   svc:/network/samba:default
online         Aug_24   svc:/network/wins:default

To enable SWAT you no longer have to edit any files, you just enable the service as below...

root# svcadm enable swat

And here is how to check the status of the service...

root# svcs swat
STATE          STIME    FMRI
online         Aug_23   svc:/network/swat:default

You still connect to SWAT on port 901, just point your browser at http://servername:901.

Sunday Jun 17, 2007

Configuring the SAMBA Web Administration Tool (SWAT) for Solaris 10

SWAT is a web based tool for managing a SAMBA server environment. It provides a GUI to manage the SAMBA configuration files (Global Settings, Shares, Printers etc), gives you simple interface to view SAMBA documentation and allows you to stop and restart the SAMBA processes.

SWAT ships with Solaris 10 in /usr/sfw/sbin and, like the version of SAMBA we ship, is supported by Sun.

The below is correct for Solaris 9 and Solaris 10 up to Solaris 10 Update 3 (11/06). If you are running  Solaris 10 Update 4 (8/07) or later you need to look at this blog entry.

Here is how you enable SWAT:

  1. Add the following line to /etc/services:

    swat 901/tcp

  2. Add the following line to /etc/inetd.conf:

    swat stream tcp nowait root /usr/sfw/sbin/swat swat

  3. Run the command inetconv to compile the new information in inetd.conf into Solaris. You should see messages about XML files being created, something like the below:

    root# inetconv
    swat -> /var/svc/manifest/network/swat-tcp.xml
    Importing swat-tcp.xml ...Done

You should now be able to connect to SWAT using a browser, just point your browser at http://servername:901.

If you want to know how to enable SAMBA in Solaris 10 in the first place, check out this blog entry.

About

Tim Thomas

Search

Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today