search for: config_t

.../* seconds to wait for response */ char *confbase = NULL; /* directory in which all config files are */ char *netname = NULL; /* name of the vpn network */ +list_t *cmdline_conf = NULL; /* global/host configuration values given at the command line */ + static int config_compare(const config_t *a, const config_t *b) { int result; @@ -45,12 +47,17 @@ static int config_compare(const config_t *a, const config_t *b) { if(result) return result; + /* give priority to command line options */ + result = !b->file - !a->file; + if (result) + return result; + result = a->l...

Even though so far there is just one possible setting to read, isolate in an own function the code to parse a configuration file and read the settings out of it. Now there's a new config_t handle used every time, but since config_read would reset an handle completely, there is no behaviour change. --- fish/config.c | 88 +++++++++++++++++++++-------------------------------------- 1 file changed, 31 insertions(+), 57 deletions(-) diff --git a/fish/config.c b/fish/config.c index e9f4...

...># mokutil --sb-state > > >>Boot failure only occurs when the grub2/shim/mokutil updates are applied. [root at xxx -]ls -la /sys/firmware/efi total 0 drwxr-xr-x 5 root root 0 Aug 4 17:12 . drwxr-xr-x 7 root root 0 Aug 4 14:30 .. -r--r--r-- 1 root root 4096 Aug 4 17:12 config_table drwxr-xr-x 2 root root 0 Aug 4 14:30 efivars -r--r--r-- 1 root root 4096 Aug 4 17:12 fw_platform_size -r--r--r-- 1 root root 4096 Aug 4 17:12 fw_vendor -r--r--r-- 1 root root 4096 Aug 4 17:12 runtime drwxr-xr-x 10 root root 0 Aug 4 17:12 runtime-map -r-------- 1 root root 4096 A...

...re only occurs when the grub2/shim/mokutil updates are >>> applied. > > > > [root at xxx -]ls -la /sys/firmware/efi > total 0 > drwxr-xr-x? 5 root root??? 0 Aug? 4 17:12 . > drwxr-xr-x? 7 root root??? 0 Aug? 4 14:30 .. > -r--r--r--? 1 root root 4096 Aug? 4 17:12 config_table > drwxr-xr-x? 2 root root??? 0 Aug? 4 14:30 efivars > -r--r--r--? 1 root root 4096 Aug? 4 17:12 fw_platform_size > -r--r--r--? 1 root root 4096 Aug? 4 17:12 fw_vendor > -r--r--r--? 1 root root 4096 Aug? 4 17:12 runtime > drwxr-xr-x 10 root root??? 0 Aug? 4 17:12 runtime-map >...

At 04:18 PM 8/4/2020, you wrote: >Am 05.08.20 um 01:09 schrieb david: >>At 01:54 PM 8/4/2020, you wrote: >>>On Tue, 04 Aug 2020 13:44:05 -0700 >>>david wrote: >>> >>> > After all the updates, the system was NOT bootable. >>> >>>How long did you wait for it to boot, and what >>>did it do when it failed to boot?? What text

...7.x86_64 #1 SMP Wed Jul 21 11:57:15 UTC 2021 yet I have 3.10.0-1160.76.1.el7.x86_64 3.10.0-1160.81.1.el7.x86_64 3.10.0-1160.83.1.el7.x86_64 3.10.0-1160.88.1.el7.x86_64 loaded. The system uses UEFI to boot. sudo ls -l /sys/firmware/efi gives: total 0 -r--r--r--.? 1 root root 4096 Feb 19 16:47 config_table drwxr-xr-x.? 2 root root??? 0 Feb 19 16:47 efivars -r--r--r--.? 1 root root 4096 Mar 14 17:57 fw_platform_size -r--r--r--.? 1 root root 4096 Feb 19 16:47 fw_vendor drwxr-xr-x.? 2 root root??? 0 Mar 14 17:57 mok-variables -r--r--r--.? 1 root root 4096 Feb 19 16:47 runtime drwxr-xr-x.? 9 root roo...