Subject | differences between Classic & Superserver on Linux |
---|---|
Author | Didier Gasser-Morlay <Didiergm@nordnet.f |
Post date | 2003-02-13T22:18:21Z |
every now & again this question comes up in this list & the standard
answer is based on ability to support multi processor & threading or
processes model.
I have found other operational differences which may be obvious to all
of you but were not to me & so I'd like to share my finding:
-Classic
- runs through xinetd script (ie started only when needed)
- does not allow remote management (ie sweep, stats, backups ...).
The error message being that this will be available in a future version)
-Superserver
- runs through init.d script (on RH) (ie started with the OS)
- ALLOWS remote management
hope this helps someone
Didier
answer is based on ability to support multi processor & threading or
processes model.
I have found other operational differences which may be obvious to all
of you but were not to me & so I'd like to share my finding:
-Classic
- runs through xinetd script (ie started only when needed)
- does not allow remote management (ie sweep, stats, backups ...).
The error message being that this will be available in a future version)
-Superserver
- runs through init.d script (on RH) (ie started with the OS)
- ALLOWS remote management
hope this helps someone
Didier