Start-up Hang due to unknown background processing

[ncmprhnsbl]

BTW in the cliexec=haveged~start command mentioned above is the ~start part to be taken literally? Usually parms are preceeded by a - or /.

for cliexec the ~ denotes a space.. so the real command is "haveged start" ..

[Ed_P]

So just to be clear, cliexec=haveged~start and cliexec="haveged start" are the same and either format will work in the APPEND statement?

[ncmprhnsbl]

So just to be clear, cliexec=haveged~start and cliexec="haveged start" are the same and either format will work in the APPEND statement?

no. cliexec=haveged~start is for the APPEND statement and haveged start is what you use in a terminal.
basicly the cliexec= cheat does not take spaces(same with guiexec=)

cheatcodes.txt says:

Code: Select all

cliexec=my_script
cliexec=my_script;reboot

   ... Execute specified command(s) in runlevel 3 (before logging
       in to a graphical interface).
       Use semicolons (;) as command separators with no spaces.
   ... If you need to use spaces in the command line, replace them
       with '~'. For example, 'cliexec=echo~Shutting~power;poweroff'
       will echo your text with spaces instead of '~'.
       NOTE: to start graphical applications please use 'guiexec='
       cheatcode instead.

[Ed_P]

Thank you ncmp

cheatcodes.txt says:

I'm amazed I haven't encountered this before.