This is not that big a deal since I seem to have Samba configured satisfactorily but I just want to know. I am supposed to be able to access swat by entering http://localhost:901 in my browser but I am unable to access it. I do have local networking active as I can browse other devices on my network. My wife can get to my printer on my Linux system from her XP system so Samba works. I have the appropriate line in /etc/services BUT traditionally you need a line in /etc/inetd.conf. We have /etc/xinetd.conf but it really just seems to refer one to the directory xinetd.d. In the Administration Guide on page 543 it refers you to /etc/xinetd.d/samba and instricts you to edit it. There is no such file. There IS /etc/xinetd.d/swat but it does not seem to require any change as far as I can see. SO, any thoughts? Scott
J. Scott Thayer, M.D. wrote:
This is not that big a deal since I seem to have Samba configured satisfactorily but I just want to know. I am supposed to be able to access swat by entering http://localhost:901 in my browser but I am unable to access it. Use Yast, Network Services, Network Services (xinetd) to enable swat. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Sunday 03 July 2005 09:33, Joe Morris (NTM) wrote:
J. Scott Thayer, M.D. wrote:
This is not that big a deal since I seem to have Samba configured satisfactorily but I just want to know. I am supposed to be able to access swat by entering http://localhost:901 in my browser but I am unable to access it.
Use Yast, Network Services, Network Services (xinetd) to enable swat.
Super suggestion and I did that. Funny thing. When I entered that item in Yast the Disable button was highlighted and the listed items were ghosted. I did the logical thing and selected Enable and the list became unghosted. The swat item was listed as active. I left that part of yast then reented it and it was again marked as Disabled and the items were ghosted. I marked enabled, left Yast, rebooted and still got an error when I pointed Konqueror at http://localhost:901. I reentered Yast and Netowrk services (xinetd) was AGAIN marked Disable and the list ghosted. I guess I am confused. Scott
On Sun, 2005-07-03 at 10:47 -0400, J. Scott Thayer, M.D. wrote:
On Sunday 03 July 2005 09:33, Joe Morris (NTM) wrote:
Super suggestion and I did that. Funny thing. When I entered that item in Yast the Disable button was highlighted and the listed items were ghosted. I did the logical thing and selected Enable and the list became unghosted. The swat item was listed as active. I left that part of yast then reented it and it was again marked as Disabled and the items were ghosted. I marked enabled, left Yast, rebooted and still got an error when I pointed Konqueror at http://localhost:901. I reentered Yast and Netowrk services (xinetd) was AGAIN marked Disable and the list ghosted. I guess I am confused.
Are clicking on the finish button in the lower right corner or just clicking on the X in the top right corner? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sunday 03 July 2005 11:01, Ken Schneider wrote:
On Sun, 2005-07-03 at 10:47 -0400, J. Scott Thayer, M.D. wrote:
On Sunday 03 July 2005 09:33, Joe Morris (NTM) wrote:
Super suggestion and I did that. Funny thing. When I entered that item in Yast the Disable button was highlighted and the listed items were ghosted. I did the logical thing and selected Enable and the list became unghosted. The swat item was listed as active. I left that part of yast then reented it and it was again marked as Disabled and the items were ghosted. I marked enabled, left Yast, rebooted and still got an error when I pointed Konqueror at http://localhost:901. I reentered Yast and Netowrk services (xinetd) was AGAIN marked Disable and the list ghosted. I guess I am confused.
Are clicking on the finish button in the lower right corner or just clicking on the X in the top right corner?
-- Finish
On Sunday, July 03, 2005 @ 9:29 AM, J. Scott Thayer, M.D. wrote:
Sunday 03 July 2005 11:01, Ken Schneider wrote:
On Sun, 2005-07-03 at 10:47 -0400, J. Scott Thayer, M.D. wrote:
On Sunday 03 July 2005 09:33, Joe Morris (NTM) wrote:
Super suggestion and I did that. Funny thing. When I entered that item in Yast the Disable button was highlighted and the listed items were ghosted. I did the logical thing and selected Enable and the list became unghosted. The swat item was listed as active. I left that part of yast then reented it and it was again marked as Disabled and the items were ghosted. I marked enabled, left Yast, rebooted and still got an error when I pointed Konqueror at http://localhost:901. I reentered Yast and Netowrk services (xinetd) was AGAIN marked Disable and the list ghosted. I guess I am confused.
Are clicking on the finish button in the lower right corner or just clicking on the X in the top right corner?
-- Finish
I'm still using INETD, and maybe things are different in the XINETD world, but the intetd.conf file has the following line in it for swat. swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat Seems like I had to at least do some tweaking on that line when I first set up swat, but that's been ages ago. Anyway, you might just take a look to see what you have in there. Greg Wallace
Correcting a typo in previous post. Should have been inetd.conf. On Sunday, July 03, 2005 @ 9:29 AM, J. Scott Thayer, M.D. wrote:
Sunday 03 July 2005 11:01, Ken Schneider wrote:
On Sun, 2005-07-03 at 10:47 -0400, J. Scott Thayer, M.D. wrote:
On Sunday 03 July 2005 09:33, Joe Morris (NTM) wrote:
Super suggestion and I did that. Funny thing. When I entered that item in Yast the Disable button was highlighted and the listed items were ghosted. I did the logical thing and selected Enable and the list became unghosted. The swat item was listed as active. I left that part of yast then reented it and it was again marked as Disabled and the items were ghosted. I marked enabled, left Yast, rebooted and still got an error when I pointed Konqueror at http://localhost:901. I reentered Yast and Netowrk services (xinetd) was AGAIN marked Disable and the list ghosted. I guess I am confused.
Are clicking on the finish button in the lower right corner or just clicking on the X in the top right corner?
-- Finish
I'm still using INETD, and maybe things are different in the XINETD world, but the inetd.conf file has the following line in it for swat. swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat Seems like I had to at least do some tweaking on that line when I first set up swat, but that's been ages ago. Anyway, you might just take a look to see what you have in there. Greg Wallace
On Mon, 2005-07-04 at 03:19 -0800, Greg Wallace wrote:
Correcting a typo in previous post. Should have been inetd.conf. On Sunday, July 03, 2005 @ 9:29 AM, J. Scott Thayer, M.D. wrote:
I'm still using INETD, and maybe things are different in the XINETD world, but the inetd.conf file has the following line in it for swat.
swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat
Seems like I had to at least do some tweaking on that line when I first set up swat, but that's been ages ago. Anyway, you might just take a look to see what you have in there.
You should probably look into starting to use xinetd instead of inetd. I think inetd is going to join the dinosaurs shortly and no longer be available. Yast has an excellent interface for setting it up. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Monday, July 04, 2005 @ 3:34 AM, Ken Schneider wrote:
On Mon, 2005-07-04 at 03:19 -0800, Greg Wallace wrote:
Correcting a typo in previous post. Should have been inetd.conf. On Sunday, July 03, 2005 @ 9:29 AM, J. Scott Thayer, M.D. wrote:
I'm still using INETD, and maybe things are different in the XINETD world, but the inetd.conf file has the following line in it for swat.
swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat
Seems like I had to at least do some tweaking on that line when I first set
up swat, but that's been ages ago. Anyway, you might just take a look to see what you have in there.
You should probably look into starting to use xinetd instead of inetd. I think inetd is going to join the dinosaurs shortly and no longer be available. Yast has an excellent interface for setting it up.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Yes. I need to do that. But first I need to get to a later release of SuSE (I'm still on 8.1!). I plan on taking another crack at upgrading (hopefully) next month. I'm trying to wrap up something else first and should be finished with that by the end of this month. My problem in upgrading has been that I haven't been able to get a backup-recovery to work after an upgrade, so I keep falling back to my fully recoverable 8.1 (else I risk losing data if I take a major hit). Based on some of the things I've read on this list, I'm wondering if part of the problem in my past attempts at upgrading has been that I was using the CD's instead of the DVD. I noticed after I upgraded that some of my packages looked strange. As I recall, in some cases, when I would click on them in Install/Remove under YAST, the only option was to delete them. Normally, there are two options -- delete and re-install. That makes me think that the basic package for those packages might not have been on the CDs for that newer SuSE version. If so, that would seem to explain why I cannot successfully do the following -- 1) Convert to new version 2) Run YAST backup on new version 3) Install basic new version out of the box from CDs. 4) Recover everything from the YAST backup When I have tried this, some critical pieces of software would no longer function. If the base packages were not there for step 2, then trying to do a recover from that file would probably not work (i. e., not get me back to what I had after 1) because those packages, while working on the converted system, would not be recovered properly if the base packages were missing from the CDs (if the CD doesn't have those packages, maybe YAST can't recover them from backup?). So maybe, if I upgrade using the DVD instead of the CDs, my YAST backup-recovery will work. Also, I just got a new (and supposedly improved) version of the STORIX DESKTOP 3rd party backup/recovery utility I bought some months ago. This newer version supports GRUB, which is the boot loader I'm using. I was unable to get a clean recovery from the prior version, which only supported LILO. But I also have reason to think that I may have messed up that backup under the older version to begin with. So, there are a number of reasons that give me hope that I'll finally get upgraded this next go-around (at least my 3rd if not 4th attempt to get this done). Then I can switch to XINETD as well as get all of the other new functionality available with the newer version. Greg W
I'm still using INETD, and maybe things are different in the XINETD world, but the intetd.conf file has the following line in it for swat.
swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat
Seems like I had to at least do some tweaking on that line when I first set up swat, but that's been ages ago. Anyway, you might just take a look to see what you have in there.
Greg Wallace
There is no inetd under Suse 9.3
On Monday, July 04, 2005 @ 6:52 AM, J. Scott Thayer wrote:
I'm still using INETD, and maybe things are different in the XINETD
world,
but the intetd.conf file has the following line in it for swat.
swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat
Seems like I had to at least do some tweaking on that line when I first set up swat, but that's been ages ago. Anyway, you might just take a look to see what you have in there.
Greg Wallace There is no inetd under Suse 9.3
I see now that you mentioned xinetd earlier. Since you send a new message each time, it's sort of hard to keep track of the conversation. See if you have a file called swat.conf. It should be in /etc/xinetd. If not, key in -- locate swat.conf from a shell to locate it. An example of this file from my Samba book is port = 901 <-- This is the standard socket_type = stream <-- This is what mine uses wait = no <-- This is what mine uses only_from = localhost <-- ? user = root <-- This is what mine uses server = /usr/local/samba/bin/swat <-- Points to the swat binary log_on_failure = USERID <-- ? disable = no <-- ? From this, you can see what port is being used on your system (should be 901). Also, I would assume disable should be set to no; else, it is disabled (yes? No?). The only_from line looks interesting. Localhost would seem to indicate it can only be invoked from the machine on which it is installed, but I'm just reading between the lines here. Not sure about log_on_failure, but I don't think you're getting that far anyway. From what I can see, these parameters are common across all networking programs under xinetd, not just samba. If there are any other entries showing under xinetd as being active, they will have also been supplied a set of parms more or less like this one, as far as I can tell. The full list of parameters can supposedly be seen by entering -- man xinted.conf So if there are any other parms in there, you could hopefully use that to figure out what they mean. This man entry should explain all of the above parms also (I don't have xinetd, so I can't look at that). If you have any other networking applications running, you might look at the parms for those and see what, if anything, is different (other than, of course, port and server). Greg W
participants (4)
-
Greg Wallace -
J. Scott Thayer, M.D. -
Joe Morris (NTM) -
Ken Schneider