You are not logged in.

#1 2008-07-29 19:13:01

kinghajj
Member
Registered: 2008-07-15
Posts: 35

"INIT: cannot fork"

When I turned my computer on this morning, I saw that it froze when starting KDM; there was a black screen with a cursor, but neither the keyboard nor the mouse worked. To troubleshoot, I booted into the ArchLive disk and edited by rc.conf to not load KDM, and to load the other daemons one-at-a-time (i.e. no "@" prefixed). On the next boot, the last daemon, FAM,  took a LONG time to complete, and then nothing happened for the longest time, until I saw a message that said "INIT: cannot fork" (or possibly "INIT: can't fork", etc.). So, I went back to ArchLive and edited rc.conf once again, and disabled FAM, so that samba was the final daemon. I booted again, and samba's still busy! I haven't seen any "INIT" messages yet, but I'm waiting for them to appear (if ever.)

Any idea what's going on? Thanks in advance for all help!

Offline

#2 2008-07-29 20:22:45

floke
Member
Registered: 2007-09-04
Posts: 266

Re: "INIT: cannot fork"

Disable preload if you are using this in your daemons - its a known bug from the latest update and bit me a few days ago.

Offline

#3 2008-07-29 20:50:14

kinghajj
Member
Registered: 2008-07-15
Posts: 35

Re: "INIT: cannot fork"

floke wrote:

Disable preload if you are using this in your daemons - its a known bug from the latest update and bit me a few days ago.

That was it! Thanks. Hopefully that bug gets fixed soon.

Offline

#4 2008-07-29 21:08:27

floke
Member
Registered: 2007-09-04
Posts: 266

Re: "INIT: cannot fork"

Glad to be of service!

Offline

Board footer

Powered by FluxBB