init: Id "x1" respawning too fast

[Kulle]

I've solved a problem,
look at the end of this thread:
Automatic connection to the wireless network

Since then a new problem has arisen.

Startup ends with the message:
init: Id "x1" respawning too fast: disabled for 5 minutes

This error does not always occur, but quite often.
Why?
Can someone help?
Thanks

[Kulle]

Supplement:
Do you have to change/add anything to the file /etc/rc.d/rc.4 ?

[Ed_P]

It could be related to what you saved with your network module. Does the problem occur when you don't use it?

Also do you boot Windows on the machine? I get a similar error if I don't shut Windows down before rebooting.

[michalpelszyk]

I have the same problem and it occurs randomly.
I found that adding a pause of 2-4 seconds at the start of /etc/rc.d/rc.4 allows me to far more consistently boot straight to X.

This happens in Virtualbox, eeePC netbook and some old Toshiba laptop as well. All random.

It's as if X is (re)starting before Porteus finishes some kind of initialisation, because startx always works. Some kind of unaccounted dependency?

5.0 rc2 Openbox. Install on a ext4 partition

[rych]

I confirm this problem remains in 5.0 rc3. I'm also on Openbox ext4 partition. (Perhaps unrelated, but every now and then at shutdown it prints a message that next time I need to use fsck cheatcode. I now always boot with fsck, it's so fast anyway, I wonder if it actually checks anything)

michalpelszyk, I'll try to add a pause you suggest in /etc/rc.d/rc.4. What's the syntax, more exactly, please? Because really a manual startx, which self-destroys after the 5 minutes with all GUI programs that were running (I guess because the original process wakes up and tries to bring up the original Desktop) -- all this is becoming a big nuisance.

[ncmprhnsbl]

I'll try to add a pause you suggest in /etc/rc.d/rc.4. What's the syntax, more exactly, please?

Code: Select all

sleep 5

(before slim)where 5 is 5 secs.. could have more or less..

a manual startx, which self-destroys after the 5 minutes

if you have the "init: Id "x11" respawning too fast:", you should do:

Code: Select all

init 3

to kill the rc.init4 process, then either do startx, slim, or try init 4 to run rc.init4 again..

[babam]

If you are using persistent then add this to /etc/rc.d/rc.local_shutdown

Code: Select all

rm -f /var/run/slim.lock

[Blaze]

rych,
need some more Porteus reboot tests

Open as root /etc/rc.d/rc.4

Find:

Code: Select all

/usr/bin/slim

Replace with:

Code: Select all

if [ -x /usr/bin/slim ]; then
  exec /usr/bin/slim -nodaemon
fi

[rych]

ncmprhnsbl, sleep 4 works. Blaze, your solution I didn't test, sorry. Because babam's solution works too and feels better as intuitively this must be a leftover from a previous session, so rc.local_shutdown seemed a better place to fix it. Thanks everyone.

[Blaze]

rych, thanks for your report.

babam, thanks for your solution.

[ncmprhnsbl]

something worth mentioning here is, if using the changes=EXIT: cheatcode, there's the conf file: /etc/changes-exit.conf, which lists the default directories saved and the ones excluded, one of which is /var/run :

Code: Select all

# Folders listed in this config file will be saved during reboot and shutdown when 'changes=EXIT:' cheatcode is used.
# Folders starting with '!' are omitted. This is useful if you want to save whole folder except for particular subfolder(s).
# An example is inclued in default config below: Porteus will save whole /var folder except for /var/run and /var/tmp subfolders.
# Other example: "!/home/guest/.mozilla/firefox/c3pp43bg.default/Cache" will skip saving of Firefox caches from guest account.
# Thanks to Rava for suggesting implementation of '!' exceptions.

/bin
/etc
/home
/lib
/lib64
/opt
/root
/sbin
/usr
/var
!/var/run
!/var/tmp

[Ed_P]

Some suggested additions to the /etc/changes-exit.conf file to help keep the save.dat's size down.

Code: Select all

!/root/.local/share/Trash/
!/root/.cache/thumbnails/normal
!/home/guest/.cache/thumbnails/normal
!/home/guest/.mozilla/firefox/Crash?Reports/pending/
!/home/guest/.mozilla/firefox/dxsqumip.default/datareporting/archived

The latter one needs to be tweaked to the user's firefox browser's profile name.

[rych]

ncmprhnsbl, Blaze, why does the /var folder needs to be persistent at all? It doesn't appear to have anything important in it to keep between boot sessions which could not be instantaneously reproduced each boot, and seems to accumulate junk from booting into different computers etc. The log files there from previous boot are also unimportant when the system operates without problems. Could I make it a tmpfs like we did here /tmp mounted as tmpfs , for it to live in RAM and to be wiped on restart?