Hi guys,
Can you give me some hints as to how to do this? Do I need to have multiple instances of the ser2sock scripts and ser2sock.config or is there a way to integrate?
At the moment, after looking at the source, it appears I could install a second init.d ser2sock script with a different name which does not use a ser2sock.conf and specify my startup params in the init.d script. Or... modify ser2sock.c to be able to accept the config file path from the arguments list and then use a second init.d script with a different name. Either way it appears I'll need to use a seconf init.d script.
Am I on the right track or is there a better way?
Thanks for all you do!
Ron