public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Shutting down process hangs - how to proceed?
Date: Sun, 20 Sep 2009 13:46:33 -0500	[thread overview]
Message-ID: <4AB67889.60306@gmail.com> (raw)
In-Reply-To: <26942.1253464941@ccs.covici.com>

covici@ccs.covici.com wrote:
> meino.cramer@gmx.de wrote:
>
>   
>> covici@ccs.covici.com <covici@ccs.covici.com> [09-09-19 15:19]:
>>     
>> I solved the problem:
>>
>> /etc/slim.conf has the 
>>
>>     daemon = no
>>
>> flag, so the boot process seems optically ok but hangs right
>> after slim hast started.
>> Shutting down the system tries to stop services/processes/action,
>> which never has been started...which fails in a hang.
>>
>> I dont know exactly...but...if that flag is the default configuration
>> when installing slim I would suggest to change it to
>>
>>     daemon = yes
>>
>> to prevent users like me to spend the weekend in searching for a 
>> problem in the shutdown process.
>>
>>     
> I don't have such a file, or as far as I know, such a package.  My
> shutdown does not hang, it just says no more processes left at this run
> level and sits there forever and will not restart the system.
>
>   

Has the OP checked his inittab file?  I ran into something like this
once a long time ago and I had to replace the inittab file since some of
it was gone.  That file belongs to sysvinit so it may be worth
re-emerging that to see if helps. 

I can post mine if you want something to compare to.  Off list of
course.  Then again, it may not be to big.

Dale

:-)  :-) 



  reply	other threads:[~2009-09-20 18:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19  1:39 [gentoo-user] Shutting down process hangs - how to proceed? meino.cramer
2009-09-19  1:57 ` Dale
2009-09-19  2:08   ` meino.cramer
2009-09-19  2:42     ` Dale
2009-09-19  9:27     ` Mick
2009-09-19 11:11       ` Pupino
2009-09-19 11:25         ` meino.cramer
2009-09-19 11:47           ` pk
2009-09-19 12:31             ` meino.cramer
2009-09-19 20:17               ` Mick
2009-09-19 21:59               ` [gentoo-user] " walt
2009-09-20  0:07                 ` meino.cramer
2009-09-20  1:09                   ` walt
2009-09-20  2:17                     ` meino.cramer
2009-09-20 16:13                       ` walt
2009-09-20 16:15                         ` meino.cramer
2009-09-20 17:16                           ` walt
2009-09-21  2:40                             ` meino.cramer
2009-09-21 17:30                               ` walt
2009-09-21 17:43                                 ` meino.cramer
2009-09-21 17:52                                   ` Pupino
2009-09-21 18:30                   ` walt
2009-09-19 14:08           ` [gentoo-user] " Pupino
2009-09-19 13:16       ` covici
2009-09-20 16:23         ` meino.cramer
2009-09-20 16:42           ` covici
2009-09-20 18:46             ` Dale [this message]
2009-09-20 19:17               ` covici
2009-09-20 20:00                 ` Dale
2009-09-19 12:25 ` Frank Steinmetzger
2009-09-19 12:47   ` meino.cramer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AB67889.60306@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox