Difference between revisions of "OS4X Portal - internal daemons"
Jump to navigation
Jump to search
(Created page with "The internal zone of OS4X Portal consists of more daemons, offering more functionality. In addition to the known OS4X client daemon "os4xclientd", the OS4X Portal daemon is be...") |
|||
| Line 1: | Line 1: | ||
| − | The internal zone of OS4X Portal consists of more daemons, offering more functionality. In addition to the known OS4X client daemon "os4xclientd", the OS4X Portal daemon is being used for the communication attempts from the internal to the external zone. It fetches all required information, events and jobs from the DMZ in order to process them as fast as possible to maintain data security in the DMZ: | + | The internal zone of OS4X Portal consists of more daemons, offering more functionality. In addition to the known OS4X client daemon "os4xclientd", the OS4X Portal daemon is being used for the communication attempts from the internal to the external zone. It fetches all required information, events and jobs from the DMZ in order to process them as fast as possible to maintain data security in the DMZ. The OS4X Portal daemon is automatically started in the internal licensed zone with the runlevel script: |
[[File:Bildschirmfoto 2019-04-08 um 14.13.20.png]] | [[File:Bildschirmfoto 2019-04-08 um 14.13.20.png]] | ||
[[Category:OS4X Portal]] | [[Category:OS4X Portal]] | ||
Revision as of 12:15, 8 April 2019
The internal zone of OS4X Portal consists of more daemons, offering more functionality. In addition to the known OS4X client daemon "os4xclientd", the OS4X Portal daemon is being used for the communication attempts from the internal to the external zone. It fetches all required information, events and jobs from the DMZ in order to process them as fast as possible to maintain data security in the DMZ. The OS4X Portal daemon is automatically started in the internal licensed zone with the runlevel script:
