[stunnel-users] limited number of ports
bwilkins at gmail.com
Sat Apr 6 18:39:38 CEST 2013
Windows 2000.... I have not used that in years. I was referring to XP and I
do not need to rename the executable. The executable name should have no
bearing on the PID.
On Apr 6, 2013 11:34 AM, "Javier" <meresponde2001-stn at yahoo.es> wrote:
> On Fri, 5 Apr 2013 18:28:43 -0400
> Brian Wilkins <bwilkins at gmail.com> wrote:
> > I simply have two entries in services. It requires editing the registry
> > giving two different names to the service entries, for instance
> > stunnel-client and stunnel-server. You can call different config files
> Ok, I've played a little with your explanation and SrvAny (link below) and
> I found that is not exactly as you tell, at least under Windows 2000.
> I didn't know this, but stunnel can run several instances just renaming the
> stunnel.exe executable, because what stunnel checks only is the PID name
> not whatever others applications check to check if it is already running.
> just changing the executable name of every stunnel.exe copy is enough to
> several intances running.
> About the services, it is not as you told (with my tests). I created two
> but if they call to the same executable the behavior is as expected:
> unable to
> run 2 or more instances. It only works if you link each service with a
> named executable. Lets say we create service "stn1" and "stn2"; "stn1"
> call to "stunnel1.exe" and "stn2" should call to "stunnel2.exe". Of
> course, each
> one can take each own .conf file.
> Anyway, it was interesting to find out this :-)
> Handy application from the NT Resource Kit:
> Download links, including for Windows 2003 server (microsoft website link):
> Remember to pass an antivirus anyway.
> stunnel-users mailing list
> stunnel-users at stunnel.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the stunnel-users