public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] wpa_supplicant annoyances (mask_service_inactive)
Date: Thu, 24 May 2012 14:31:36 +0100	[thread overview]
Message-ID: <20120524143136.03ee1f5a@digimed.co.uk> (raw)
In-Reply-To: <CAMix8LEexY5hBGHOgh4iYGjvJHdPeMmybiHYXW-wGY_w1wKAJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

On Thu, 24 May 2012 12:50:27 +0200, Jesús J. Guerrero Botella wrote:

> I've been using this for some time now, and I changed the config a lot
> of times. Always had problems. The last time I set this up I removed
> everything from /etc/conf.d/net and /etc/conf.d/wpa_supplicant, and
> let it did it's automatic job instead. So far, it's working... some
> random times. The errors always show though. And they screw up the
> init. The worst is that it bits sshd, which leaves me without remote
> access any random day. Ugh.
> 
> So, any idea where to start looking? :D

"genlop -l --date yesterday" is always a good place to start. I knew
this wasn't down to wpa_supplicant as I got it this morning on a
wirelessless desktop. Genlop showed that openrc was updated yesterday and
searching bugzilla for openrc found https://bugs.gentoo.org/show_bug.cgi?id=417227

It appears that a fix has been committed.


-- 
Neil Bothwick

Last yur I kudnt spel modjerater now I are won.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-05-24 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 10:50 [gentoo-user] wpa_supplicant annoyances (mask_service_inactive) Jesús J. Guerrero Botella
2012-05-24 13:20 ` Mick
2012-05-24 13:31 ` Neil Bothwick [this message]
2012-05-24 13:50   ` Jesús J. Guerrero Botella

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=20120524143136.03ee1f5a@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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