Bit wrote:
Hey everyone,
If anyone could help me with this problem, I'd greatly appreciate it.
Whenever I try to start swat (from the command-line by invoking
/usr/sbin/swat), it sits there for a very long time as if it's
running, but any attempt to use telnet to the port or point my browser
at it results in nothing, as if swat were just not running.
Firewalling is no issue, I've disabled it. Swat ultimately dies after
a few minutes giving no output to the console other than "Alarm
clock". What does this error message mean?
I've tried running swat with -d 10 and "strace /usr/sbin/swat -o
myfile" hoping that the output will mean more to someone else than it
does to me. I've seen other people with this problem googling around,
but no solution, and I can't seem to figure it out on my own.
Thanks in advance for the help,
bit
<snip>
It's been a while since I last used swat so this may have changed, but
back in the day swat didn't handle its own network stuff. Have you tried
adding swat to your *inetd config (assuming you have one). If you don't
have any form of inetd running, maybe it would be possible to hack
something together using netcat (obviously not a good idea for a
production environment)?
*Michael Heydon - IT Administrator *
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
