Pete Travis wrote:
I cut out the parts that didn't seem relevant to accomplishing
what it
seems like you are trying to do.
Can you elaborate on what service, specifically, you want to listen on a
different port, how you attempted to change it, and what happened when you
did so?
Hi, it seems as You cut too many from my post. I wrote before, that
I not any problem with doing that with sysv initscrips - ant it
was services:
- sshd (I want run one instance for ordinal remote users, and second
on different port for administration)
- squid (I want run one instance as transparent proxy and another
on different port as stadalone proxy. This was in squid 2 times,
now at squid 3 this is possible in one instance)
- Firebird and Gupta SQLBase SQL DB servers, when differen instances
was running for different purposes
- perhaps some others...
I do not know where you're going with your question - I know that
I can do with systemd units too and I'm doin this. But the core of
the problem is elsewhere - systemd seem be darkly big, complex,
unstable, as Linux will be evolving it perhaps will require
continuing support - it's all far from the Unix systems principles.
IMHO
--
Franta Hanzlik