Ticket #19 (closed defect: fixed)

Opened 17 months ago

Last modified 10 months ago

SWAT

Reported by: diver Owned by: psmedley
Priority: minor Milestone:
Component: Server Version:
Keywords: Cc:
Blocking: Blocked By:

Description

SWAT seems not to open a socket and is because of that not usable. According to the log it reads the smb.conf. The log shows no error

Attachments

log.swat (8.6 kB) - added by diver 17 months ago.
SWAT Log

Change History

Changed 17 months ago by diver

SWAT Log

Changed 10 months ago by herwigb

Rich Walsh about our SWAT problem after having looked at the source:

"As written, SWAT expects that inetd has created a socket for it and has redirected its i/o to stdin & stdout. Apparently, OS/2's inetd can't do that kind of redirection, so it just passes the socket's handle on the command line & leaves it to the app to use TCP/IP calls to access it.

From what I could see, it shouldn't take more than an hour for someone with experience to change the fread() and fwrite() calls to the TCP/IP equivalent.

Maybe I don't know what I'm talking about, but it looks really simple."

Changed 10 months ago by guest

  • status changed from new to closed
  • resolution set to fixed

starting with Samba server 3.0.28 from 08.02.2008 and later SWAT works as a Apache CGI. See http://svn.netlabs.org/samba/wiki/Cookbook

Note: See TracTickets for help on using tickets.