Sameer N I wrote:
>>> Look at qmail-pop3d-ssl.run Sorry - I mean /var/qmail/boot/qmail-pop3d-ssl/run (but its exactly the same...) This is placed there by running 'make setup check' in the qmail-ldap source directory. >> I have this script in /var/bin/boot but will copying it to >> /var/qmail/service >> and creating a link to it in /service (to start using it with svc) is >> enough? I guess this dont worked because svscan look for run and not for other files like "qmail-pop3d-ssl.run" >> I have /var/qmail/control/cert.pem and the control/*cert files in place. >> I already have tcpserver running, patched with tcpserver ssl/tls patch. With permissions like this? rw-r----- 1 qmaild qmail /var/qmail/control/cert.pem > I tried linking /var/qmail/boot/qmail-pop3d-ssl in > /var/qmail/service/qmail-pop3d-ssl > and creating a link to /var/qmail/service/qmail-pop3d-ssl in > /service/pop3d-ssl Why do you linking /var/qmail/boot/ directorys to /var/qmail/service and then to /service? My svscan is looking at /service. Therefore I linked the needed service-directorys to /service. You have to do: # ln -s /var/qmail/boot/qmail-pop3d-ssl/ /service/qmail-pop3d-ssl But, before you do this, go to /var/qmail/boot/qmail-pop3d-ssl and type ./run tcpserver: status: 0/40 tcpserver: status: 1/40 tcpserver: pid 38667 from xxx tcpserver: ok 38667 xxx:xxx:995 :xxx::53016 pbsadd unable to read controls [1] tcpserver: end 38667 status 0 tcpserver: status: 0/40 [1] you can comment out pbsadd in the run-filerun So you can see if this works out... (you can connect with telnet and then with an POP3-SSL capaple Client to port 995 and see whats going on) If this all OK, you can place the link into /service. Oskar
