#19 closed defect (fixed)
SWAT
Reported by: | Silvan Scherrer | Owned by: | Paul Smedley |
---|---|---|---|
Priority: | minor | Milestone: | Samba Server for eCS (OS/2) 1.0.1 |
Component: | Samba Server | Version: | 3.0.25a |
Keywords: | Cc: |
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 (1)
Change History (5)
Changed 17 years ago by
comment:1 Changed 16 years ago by
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 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
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
comment:3 Changed 15 years ago by
Milestone: | → Samba Server for eCS (OS/2) 1.0.1 |
---|
comment:4 Changed 15 years ago by
Version: | → 3.0.25a |
---|
SWAT Log