> > You can run stunnel in two ways, as a normal user in which case you > > would specify the config file as something you could modify, or you > > could run it as a system service, in which case a SMF manifest would > > be s usefull addition. I plan on creating a SMF manifest and you can > > enable this service if needed, but the default value of > > config/stunnel_config_file needs to be set to something, even if its > > changed before the service is enabled. > > Right, when running stunnel as a client it may not make sense to use a > config file from /etc. Using $SMF_FMRI to decide that this must be a > server is really a heuristic, possibly a bad one (since why shouldn't > servers turn around and act as clients? but then, why not tell stunnel > then what config file to use on its command line?). >
You can make stunnel work as a client and a server from the same configuration file, running from SMF just makes it possible to create a system wide service which can be started automatically when the system boots. This does not prevent a unprivileged user from creating their own service using their own config as well (obviously on non-privileged ports). I don't understand what your suggesting in the last sentance, stunnel will take the config file as a command line arg, the problem is if you don't it will look for /usr/local/etc/stunnel/stunnel.conf which won't exist and cause an error. My question is, if I create a manifest which has a config_file property, what should that default as ? Thanks Mark
