From: Gerrit Pape <pape@smarden.org>
Subject: Re: Runit error (help urgent !!)
Date: Wed, 1 Feb 2006 10:32:01 +0000 [thread overview]
Message-ID: <20060201103201.1397.qmail@e4f36f90fb70e0.315fe32.mid.smarden.org> (raw)
In-Reply-To: <43DA1D31.6050604@gmail.com>
On Fri, Jan 27, 2006 at 11:16:33AM -0200, Daniel wrote:
> Hi folks!
>
> Something happen with my system. I am using runit 1.3.3 and until tree
> days ago, everything is perfect, but now when I get the login prompt
> this message come out :
>
> chdir: No such file or directory.
>
> This message stay over and over, seem like a loop.
>
> Can someone give me a light ?
This sounds rather like an error message from the service than from
runit. Can it be that the getty or the login program has trouble
changing to the user's home directory and so prints this message? Do
you run the getties under runit?
Regards, Gerrit.
prev parent reply other threads:[~2006-02-01 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 13:16 Daniel
2006-02-01 10:32 ` Gerrit Pape [this message]
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=20060201103201.1397.qmail@e4f36f90fb70e0.315fe32.mid.smarden.org \
--to=pape@smarden.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;
as well as URLs for NNTP newsgroup(s).