ConfigServer Community Forum

I bought cxs because I was so impressed with csf

While cxs does a lot behind the scenes, the UI is inferior to csf

Why not try to detect if the cxs Watch daemon is running and alert that everything is okay (or not) - similar to what csf does?

Why not do a one-click activation to install the cxs Watch daemon for startup?

Please make cxs have a checklist like csf has to indicate what should be fixed or tightened up?

It's somewhat strange that the free product interface is better than the commercial one.

They are completely different products, so they have different UI's. csf is much more mature and the UI is provided to give access to all levels of user to configure and control csf from a UI.

cxs is aimed purely at server administrators and has been developed as a CLI tool. The UI is provided to allow quick access to some of the tools, but it is not replacement for the CLI and never will be.

There are is no UI access to the cxs watch daemon as it is infinitely configurable with whatever startup method you want to use, the cxswatch.sh script is only provided as a basic example. You caould just as easily have multiple daemons running various configuration setups.

The documentation does indeed suggest a method to start the daemon at boot time using the rc.local file. Since cxs does not have a running daemon service, it is up to you to configure whatever service monitoring tools you use to check whether it is currently running whatever configuration setup you have, which could be different for every person using cxs.