Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Lots of documentation is included in the samba packages of Red Hat Linux and Fedora Core. There's even the "Using Samba" book included. Start there and ask specific questions.
Thanks for advice. I think I have Samba upand running now. but I still can not get Swat working. http://127.0.0.1:901 just does not work I get an error like "document empty..." I know it is better to use the smb.conf file but I would like to get swat working for peace of mind.
i Have configured samba its working fine but I found one problem:
Samba seems to replace uppercase letters in filenames by lowercase ones.
Probably it is a Samba configuration issue.
Controlling the filename exactly is of crucial importance for us.
how to deal with this can any body help
To start Samba swat, all a user of Red Hat Linux would need to do is to login as root and run chkconfig swat on -- this is provided that xinetd service is still running, swat would be started automatically. In case xinetd was disabled, a chkconfig xinetd on ; service xinetd restart would be necessary. Afterwards, use a command like netstat or socklist to show that something listens on port 901 TCP.
Originally posted by srikz i Have configured samba its working fine but I found one problem:
Samba seems to replace uppercase letters in filenames by lowercase ones.
Probably it is a Samba configuration issue.
Controlling the filename exactly is of crucial importance for us.
how to deal with this can any body help
I found this:
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
preserve case = yes
short preserve case = yes
# Default case is normally upper case for all DOS files
default case = lower
# Be very careful with case sensitivity - it can break things!
case sensitive = no
I am using Red Hat 9.0. My SWAT wasnt working so I downloaded the latest Samba version from Samba.org and compiled it, but the status remains same i.e. my Samba is working fine and it has installed the required SWAT files, but there is no SWAT service appearing in the xinetd.d directory.
I added the following code in the xinetd.conf file:
service swat
{
port = 901
socket_type = stream
wait = no
only_from = localhost
user = root
server = /usr/sbin/swat
log_on_failure += USERID
disable = no
}
I also turned on the httpd, but nothing gained... I cannot start the SWAT service and cant use SWAT using the browser.
SWAT is independent from the HTTP server as it provides an own server. Just point your web browser to "http://127.0.0.1:901". Change the xinetd template file to "only_from = 127.0.0.1". Because you added the file manually, make sure you restart xinetd with "service xinetd restart". Then show that xinetd listens on port 901, run "netstat -tpan" and post output here. When you try to connect, what is logged in /var/log/secure?
service swat
{
port = 901
socket_type = stream
wait = no
only_from = 127.0.0.1
user = root
server = /usr/local/samba/sbin/swat
log_on_failure +=USERID
disable = no
}
Thankyou so very much! But u wont believe how it worked. I was using Mozilla browser and writing http://127.0.0.1:901/ in the window that is appearing, this time i chose the Open Web Location option from File Menu and wrote http://127.0.0.1:901/ and it opened SWAT...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.