Status of the system Introduction _L_i_n_u_x_c_o_n_f has the unique ability to probe almost every running servers and configuration on the machine and compare this with the "required" configuration. From there it can produce a report, or take action. 11.. PPrriinncciipplleess _L_i_n_u_x_c_o_n_f defines the "required" configuration by looking at many configuration files. From the content or the revision date of each files, _L_i_n_u_x_c_o_n_f may take the following action. +o (re)Configure a system (change the IP number of the Ethernet adaptor). +o Start a daemon. +o Kill a daemon. +o Kill/Restart a daemon. +o Send a signal to a daemon to force it to read its configuration file. _L_i_n_u_x_c_o_n_f can this work in simulation mode. In this mode it simply take note of what have to be done. In activation mode the actions are performed and a log is written in /var/adm/netconf.log. 22.. EEvveerryy ttiimmee yyoouu lleeaavvee LLiinnuuxxccoonnff This probing is done every-time you quit from _L_i_n_u_x_c_o_n_f. The idea is to avoid the state where a system fails to operate as expected not because it is badly configured, but simply because, the configuration has not been activated. Unfortunately many peoples are convinced that rebooting is a necessity. In fact, it is, on most other operating systems. _L_i_n_u_x and _L_i_n_u_x_c_o_n_f are changing that. 33.. CCoommmmaanndd lliinnee mmooddee The command "netconf --status" will produce a report about what have to be done to bring the system current. The command "netconf --update" will bring the system current. If you are used to edit configuration file "by hand" with your favorite editor, you can still do it. A simple "netconf --update" will make sure everything is fine.