Opened 12 years ago

Closed 12 years ago

Last modified 10 years ago

#19 closed defect (fixed)


Reported by: diver Owned by: psmedley
Priority: minor Milestone: Samba Server for eCS (OS/2) 1.0.1
Component: Samba Server Version: 3.0.25a
Keywords: Cc:


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 (1)

log.swat (8.6 KB) - added by diver 12 years ago.

Download all attachments as: .zip

Change History (5)

Changed 12 years ago by diver


comment:1 Changed 12 years 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."

comment:2 Changed 12 years ago by guest

  • Resolution set to fixed
  • Status changed from new to closed

starting with Samba server 3.0.28 from 08.02.2008 and later SWAT works as a Apache CGI. See

comment:3 Changed 10 years ago by herwigb

  • Milestone set to Samba Server for eCS (OS/2) 1.0.1

comment:4 Changed 10 years ago by herwigb

  • Version set to 3.0.25a
Note: See TracTickets for help on using tickets.