Featureless Make is using "settings" and the Controller program is using "setting".
Fix this inconsistency.
The term "settings" sounds more accurate than "setting".
return controller_rule_item_type_service_e;
}
- if (fl_string_dynamic_compare(item, controller_setting_s) == F_equal_to) {
- return controller_rule_item_type_setting_e;
+ if (fl_string_dynamic_compare(item, controller_settings_s) == F_equal_to) {
+ return controller_rule_item_type_settings_e;
}
if (fl_string_dynamic_compare(item, controller_utility_s) == F_equal_to) {
case controller_rule_item_type_service_e:
return controller_service_s;
- case controller_rule_item_type_setting_e:
- return controller_setting_s;
+ case controller_rule_item_type_settings_e:
+ return controller_settings_s;
case controller_rule_item_type_utility_e:
return controller_utility_s;
* Codes representing rule items.
*
* controller_rule_item_type_*:
- * - command: The item type represents a command operation.
- * - script: The item type represents a script operation.
- * - service: The item type represents a service operation.
- * - setting: The item type represents a setting operation.
- * - utility: The item type represents a utility operation.
+ * - command: The item type represents a command operation.
+ * - script: The item type represents a script operation.
+ * - service: The item type represents a service operation.
+ * - settings: The item type represents a setting operation.
+ * - utility: The item type represents a utility operation.
*/
#ifndef _di_controller_rule_item_types_t_
enum {
controller_rule_item_type_command_e = 1,
controller_rule_item_type_script_e,
controller_rule_item_type_service_e,
- controller_rule_item_type_setting_e,
+ controller_rule_item_type_settings_e,
controller_rule_item_type_utility_e,
};
#endif // _di_controller_rule_item_types_t_
const f_string_static_t controller_scheduler_s = macro_f_string_static_t_initialize(CONTROLLER_scheduler_s, 0, CONTROLLER_scheduler_s_length);
const f_string_static_t controller_script_s = macro_f_string_static_t_initialize(CONTROLLER_script_s, 0, CONTROLLER_script_s_length);
const f_string_static_t controller_service_s = macro_f_string_static_t_initialize(CONTROLLER_service_s, 0, CONTROLLER_service_s_length);
- const f_string_static_t controller_setting_s = macro_f_string_static_t_initialize(CONTROLLER_setting_s, 0, CONTROLLER_setting_s_length);
+ const f_string_static_t controller_settings_s = macro_f_string_static_t_initialize(CONTROLLER_settings_s, 0, CONTROLLER_settings_s_length);
const f_string_static_t controller_session_s = macro_f_string_static_t_initialize(CONTROLLER_session_s, 0, CONTROLLER_session_s_length);
const f_string_static_t controller_session_new_s = macro_f_string_static_t_initialize(CONTROLLER_session_new_s, 0, CONTROLLER_session_new_s_length);
const f_string_static_t controller_session_same_s = macro_f_string_static_t_initialize(CONTROLLER_session_same_s, 0, CONTROLLER_session_same_s_length);
#define CONTROLLER_session_s "session"
#define CONTROLLER_session_new_s "session_new"
#define CONTROLLER_session_same_s "session_same"
- #define CONTROLLER_setting_s "setting"
+ #define CONTROLLER_settings_s "settings"
#define CONTROLLER_sigpending_s "sigpending"
#define CONTROLLER_show_s "show"
#define CONTROLLER_shutdown_s "shutdown"
#define CONTROLLER_session_s_length 7
#define CONTROLLER_session_new_s_length 11
#define CONTROLLER_session_same_s_length 12
- #define CONTROLLER_setting_s_length 7
+ #define CONTROLLER_settings_s_length 8
#define CONTROLLER_show_s_length 4
#define CONTROLLER_shutdown_s_length 8
#define CONTROLLER_sigpending_s_length 10
extern const f_string_static_t controller_session_s;
extern const f_string_static_t controller_session_new_s;
extern const f_string_static_t controller_session_same_s;
- extern const f_string_static_t controller_setting_s;
+ extern const f_string_static_t controller_settings_s;
extern const f_string_static_t controller_show_s;
extern const f_string_static_t controller_shutdown_s;
extern const f_string_static_t controller_sigpending_s;
if (fl_string_dynamic_compare(controller_main_s, actions->array[cache->ats.array[at_j]].parameters.array[0]) == F_equal_to) {
continue;
}
- else if (fl_string_dynamic_compare(controller_setting_s, actions->array[cache->ats.array[at_j]].parameters.array[0]) == F_equal_to) {
+ else if (fl_string_dynamic_compare(controller_settings_s, actions->array[cache->ats.array[at_j]].parameters.array[0]) == F_equal_to) {
continue;
}
entry->items.used = 1;
}
}
- else if (fl_string_dynamic_compare(controller_setting_s, cache->action.name_item) == F_equal_to) {
+ else if (fl_string_dynamic_compare(controller_settings_s, cache->action.name_item) == F_equal_to) {
status = controller_entry_settings_read(global, is_entry, *range, cache);
continue;
for (i = 0; i < process->rule.items.used && controller_thread_is_enabled_process(process, global.thread); ++i) {
- if (process->rule.items.array[i].type == controller_rule_item_type_setting_e) continue;
+ if (process->rule.items.array[i].type == controller_rule_item_type_settings_e) continue;
for (j = 0; j < process->rule.items.array[i].actions.used; ++j) {
break;
}
- if (fl_string_dynamic_compare(controller_setting_s, cache->action.name_item) == F_equal_to) {
+ if (fl_string_dynamic_compare(controller_settings_s, cache->action.name_item) == F_equal_to) {
rule->items.array[rule->items.used].type = 0;
}
else if (fl_string_dynamic_compare(controller_command_s, cache->action.name_item) == F_equal_to) {
}
if (cache.name_item.used) {
- fl_print_format("rule %r '%]", print.to.stream, item ? controller_item_s : controller_setting_s, print.context);
+ fl_print_format("rule %r '%]", print.to.stream, item ? controller_item_s : controller_settings_s, print.context);
fl_print_format("%[%Q%]", print.to.stream, print.notable, cache.name_item, print.notable);
fl_print_format("%[' on line%] ", print.to.stream, print.context, print.context);
fl_print_format("%[%un%]", print.to.stream, print.notable, cache.line_item, print.notable);
# A very basic boot process.
#
-setting:
+settings:
pid ready
show init
# A boot to bash process.
#
-setting:
+settings:
pid disable
show init
# fss-0005
-setting:
+settings:
mode program
main:
# fss-0005
-setting:
+settings:
mode program
main:
# fss-0005
-setting:
+settings:
mode service
main:
# This example shows how htop can be started during the exit process rather than the entry.
# See the htop-alternate.exit example.
-setting:
+settings:
mode program
control htop.socket
# fss-0005
-setting:
+settings:
mode program
control htop.socket
# fss-0005
-setting:
+settings:
mode program
control htop.socket
# fss-0005
-setting:
+settings:
mode program
main:
# fss-0005
-setting:
+settings:
mode program
main:
# fss-0005
-setting:
+settings:
control controller/run/up.socket
pid ready
pid_file controller/run/up.pid
# Note: The example setting "limit nice 1 2" may cause this rule to fail if the user has insufficient privileges granted by ulimits or some other system security measure.
#
-setting:
+settings:
name "Sleep 1 Seconds."
nice 15
limit nice 1 2
# Note: The example setting "limit nice 1 2" may cause this rule to fail if the user has insufficient privileges granted by ulimits or some other system security measure.
#
-setting:
+settings:
name "Sleep 10 Seconds."
nice 15
limit nice 1 2
# Note: The example setting "limit nice 1 2" may cause this rule to fail if the user has insufficient privileges granted by ulimits or some other system security measure.
#
-setting:
+settings:
name "Sleep 2 Seconds."
nice 15
limit nice 1 2
# Note: The example setting "limit nice 1 2" may cause this rule to fail if the user has insufficient privileges granted by ulimits or some other system security measure.
#
-setting:
+settings:
name "Sleep 3 Seconds."
nice 15
limit nice 1 2
# Note: The example setting "limit nice 1 2" may cause this rule to fail if the user has insufficient privileges granted by ulimits or some other system security measure.
#
-setting:
+settings:
name "Sleep 5 Seconds."
nice 15
limit nice 1 2
# Note: The example setting "limit nice 1 2" may cause this rule to fail if the user has insufficient privileges granted by ulimits or some other system security measure.
#
-setting:
+settings:
name "Sleep 8 Seconds."
nice 15
limit nice 1 2
# fss-000d
-setting:
+settings:
name "Run htop"
command:
# fss-000d
-setting:
+settings:
name "Multiple Commands: id, whoami, date, etc.."
capability "all="
control_group new memory/example
# Rule for a long delay.
#
-setting:
+settings:
name "Delay for 3 minutes."
script:
# Rule for a short delay.
#
-setting:
+settings:
name "Delay for 3 seconds."
script:
# fss-000d
-setting:
+settings:
name "Environment default"
engine bash
# fss-000d
-setting:
+settings:
name "Environment set to nothing"
environment
engine bash
# fss-000d
-setting:
+settings:
name "Environment with PATH"
environment PATH
engine bash
# fss-000d
-setting:
+settings:
name "Environment with PATH"
environment PATH custom_variable
engine bash
# fss-000d
-setting:
+settings:
name "Explosion!"
engine sh
# fss-000d
-setting:
+settings:
name "Create Socket Path"
parameter verbose -v
# fss-000d
-setting:
+settings:
name "Script #2"
on start need script succeed
# fss-000d
-setting:
+settings:
name "IKI Variable Substitution"
environment PATH IKI_TEST
define IKI_TEST "This is iki data in an environment variable."
# fss-000d
-setting:
+settings:
name "PHP script"
environment PATH
engine php
# fss-000d
-setting:
+settings:
name "Python (Version 3.X) script"
environment PATH
engine python3
# fss-000d
-setting:
+settings:
name "Example script for needs, wants, and wishes."
environment PATH
engine sh
# fss-000d
-setting:
+settings:
name "Script #1"
environment PATH
engine sh
# fss-000d
-setting:
+settings:
name "Serial 1"
on stop need serial s_2
# fss-000d
-setting:
+settings:
name "Serial 2"
on start need serial s_1
on stop need serial s_3
# fss-000d
-setting:
+settings:
name "Serial 3"
on start need serial s_2
on stop need serial s_4
# fss-000d
-setting:
+settings:
name "Serial 4"
on start need serial s_3
on stop need serial s_5
# fss-000d
-setting:
+settings:
name "Serial 5"
on start need serial s_4
on stop need serial s_6
# fss-000d
-setting:
+settings:
name "Serial 6"
on start need serial s_5
# Sshd appears to require a full path.
#
-setting:
+settings:
name "SSH Service"
nice 15
# fss-000d
# sleeper rule whose program creates its own PID file, runs in the background, sleep for a while, removes PID file, and returns.
-setting:
+settings:
name "Sleeper #1"
nice 10
# fss-000d
# sleeper rule whose program creates its own PID file, runs in the background, sleep for a while, removes PID file, and returns.
-setting:
+settings:
name "Sleeper #2"
nice 10
# fss-000d
# sleeper rule whose program creates its own PID file, runs in the background, sleep for a while, removes PID file, and returns.
-setting:
+settings:
name "Sleeper #2"
nice 10
# Rule for initializing the /dev file system.
#
-setting:
+settings:
name "Setup /dev file system"
on start need boot root
# Rule for initializing the filesystem.
#
-setting:
+settings:
name "Setup Filesystem"
on start need boot root
# Rule for initializing the kernel modules.
#
-setting:
+settings:
name "Setup Kernel Modules"
on start need boot root
# Rule for initializing the /proc filesystem.
#
-setting:
+settings:
name "Setup /proc Filesystem"
on start need boot root
# Rule for initializing the root filesystem, assuring certain directories always exist.
#
-setting:
+settings:
name "Setup Root Filesystem"
command:
# Rule for maintenance/failsafe console.
#
-setting:
+settings:
name "Maintenance Console"
command:
# Rule for starting all network devices.
#
-setting:
+settings:
name "System Network"
capability cap_net_admin=
# Rule for loopback device.
#
-setting:
+settings:
name "Loopback Device"
on start need boot modules
# Rule for D-Bus service.
#
-setting:
+settings:
name "D-BUS"
capability all=
nice 15
# Rule for system logger service.
#
-setting:
+settings:
name "System Logger"
capability all=
nice 19
# Rule for console mouse.
#
-setting:
+settings:
name "Console Mouse"
capability all=
nice 15
# Rule for setting the clock.
#
-setting:
+settings:
name "Setup Clock"
capability cap_sys_time=
nice 15
# Rule for setting the keyboard.
#
-setting:
+settings:
name "System Keyboard"
nice 15
# Rule for executing ntpdate.
#
-setting:
+settings:
name "System Clock Using NTP Date"
capability cap_sys_time=
nice 15
# -J = don't clear on start, good for debugging.
# 9600 and 115200 are common frequencies.
-setting:
+settings:
name "System Terminal 4"
command:
# -J = don't clear on start, good for debugging.
# 9600 and 115200 are common frequencies.
-setting:
+settings:
name "System Terminal 1"
command:
# -J = don't clear on start, good for debugging.
# 9600 and 115200 are common frequencies.
-setting:
+settings:
name "System Terminal 3"
command:
# -J = don't clear on start, good for debugging.
# 9600 and 115200 are common frequencies.
-setting:
+settings:
name "System Terminal 2"
command:
All other Basic List Objects are not executed unless either an "item" or a "failsafe" specifies a valid Item name.
Execution of all Items are top-down.
- - The "setting" item Object\:
+ - The "settings" item Object\:
Represents Entry settings and is not an "item" that can be executed.
A number of settings are supported, but if this Item Object is not specified, then defaults are used.
The following settings are available: "control", "control_group", "control_mode", "control_user", "define", "mode", "parameter", "pid", "pid_file", "session", "show".
An Exit is a special variation or subset of an Entry.
- - The "setting" Item Object\:
+ - The "settings" Item Object\:
Represents settings and is not an "item" that can be executed.
A number of settings are supported, but if this Item Object is not specified, then defaults are used.
The following settings are available: "pid" and "show".
A Rule file, such as "ssh.rule", is intended to designate what to execute.
- The rule file is read top-down, except for the outer most list "setting", which is intended to store setting data for this rule.
+ The rule file is read top-down, except for the outer most list "settings", which is intended to store setting data for this rule.
Multiple outer most list Objects may be specified and they are executed as provided, in a top-down manner.
- - The "setting" Rule Type has the following FSS-0001 (Extended) Content\:
+ - The "settings" Rule Type has the following FSS-0001 (Extended) Content\:
- "affinity": Define one or more processors to restrict this rule by with each number representing a specific processor by its id (starting at 0).
- "capability": Define a set of capabilities in which to use, using the capability "text" format (such as "= cap_chown+ep").
- "cgroup": Define a cgroup (control group) in which everything within this rule executes under.
The first Content represents the file path (without any leading/trailing slashes and without file extension).
The second Content represent the basename of the command file.
- - "setting": optional, Actions may be one of\:
+ - "settings": optional, Actions may be one of\:
- "control": One to two Content.
The first Content is a relative or absolute path to a socket file.
The second Content an optional "readonly".
The Items:
- "main": required.
- - "setting": optional, Actions may be one of:
+ - "settings": optional, Actions may be one of:
- "pid": Exactly one Content that is one of "disable", "require", or "ready".
- "session": Exactly one Content that is one of "new" or "same".
- "show": Exactly one Content that is one of "normal" or "init".
- "command": FSS-0003 (Extended List) or FSS-0001 (Extended).
- "script": FSS-0003 (Extended List) or FSS-0001 (Extended).
- "service": FSS-0003 (Extended List) or FSS-0001 (Extended).
- - "setting": (Required) FSS-0001 (Extended).
+ - "settings": (Required) FSS-0001 (Extended).
- "utility": FSS-0003 (Extended List) or FSS-0001 (Extended).
- For the above Rule Types, "setting" may be specified only once whereas the others may be specifed multiple times.
- The "setting" Rule Type is always processed first, regardless of position.
+ For the above Rule Types, "settings" may be specified only once whereas the others may be specifed multiple times.
+ The "settings" Rule Type is always processed first, regardless of position.
The other Rule Types are processed top-down.
- The "setting" Rule Type has the following FSS-0001 (Extended)\:
+ The "settings" Rule Type has the following FSS-0001 (Extended)\:
- "affinity": One or more Content, each must be a 0 or greater whole number.
- "capability": One Content representing capabilities.
- "cgroup": Two or more Content, the first Content being either "existing" or "new" and the remaining representing a valid cgroup (control group) name, must have at least 1 graph character (non white space printing character) (leading and trailing white space are trimmed off).
* Build settings data.
*
* data_build_setting_flag_*:
- * - has_environment: Designate that the "environment" is specified in the "setting" Section of the Fakefile.
+ * - has_environment: Designate that the "environment" is specified in the "settings" Section of the Fakefile.
*
* flag: Flags from data_build_setting_flag_* (Not strictly part of the build settings file).
*
projects / fll / commitdiff