Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [SOLVED]Network init script error??
Date: Tue, 09 Nov 2010 10:47:25 -0800	[thread overview]
Message-ID: <4CD9973D.4040201@balister.org> (raw)
In-Reply-To: <AANLkTi=5W1Sat-egZmbeQv6B+PX+Vatabq=2+YZw_wGx@mail.gmail.com>

On 11/08/2010 08:39 PM, Steve Sakoman wrote:
> Looping in the OE developers list on the issue described below.
>
> It does indeed seem that the ifupdown package init is referencing
> /etc/network/ifstate (which doesn't exist) instead of
> /etc/network/run/ifstate.
>
> Mike's point about having the /etc/network/run directory linked to
> /var/run also seems like a good idea (so that ifstate would not
> persist after an unclean shutdown).

Fixing the script removes the state file before it is checked on boot, 
so I do not think it is necessary to move the state file to a volatile 
file system. I'm going to push the fix to the ifupdown package. There is 
also ifupdown-ubuntu, but I am not sure who is using that. It references 
/var/run/....

Philip


>
> Thoughts?
>
> Steve
>
>
> ---------- Forwarded message ----------
> From: roystonvasey<mikestocks@madasafish.com>
> Date: Mon, Nov 8, 2010 at 7:14 PM
> Subject: [Gumstix-users]  [SOLVED]Network init script error??
> To: gumstix-users@lists.sourceforge.net
>
>
>
> Dear List,
> I as many others are having problems getting the networking to start
> reliably on headless systems, wlan0 in particular.
> If the network is restarted '/etc/init.d/networking restart' wireless and my
> CAN networks come up OK, on system halt and reboot they also come up OK.
> If power is interrupted the networks are not starting after a reboot and
> require a manual restart.
>
> After some investigations I noticed that there is an initialisation script
> '/etc/rcS.d/S39ifup' that is run just before the network is started with
> '/etc/rcS.d/S40networking'. The script looks like it clears up any hanging
> ifstate files.
> #!/bin/sh -e
>
> case "$1" in
>         start|restart)
>                 if [ -e /etc/network/ifstate ]; then
>                         echo -n "Cleaning: /etc/network/ifstate"
>                         echo -n>/etc/network/ifstate
>                         echo "."
>                 fi
>                 ;;
>         stop|reload|force-reload)
>                 ;;
> esac
>
> However the actual ifstate file is created in '/etc/network/run/ifstate'.
> Adjusting the script allows the network to come up properly even after a
> power outage.
> I suspect that ifup checks ifstate to see if the interface is already up and
> doesn't do anything if there is an entry in the ifstate file and ifdown
> takes out etries as it brings down the interface. Hence a clean shut down
> will clear entries and allow the the networks to start normally on start up.
> The other observation is that the '/etc/network/run' directory should
> probably be linked to the '/var/run' directory.
>
> Can anyone verify that my findings are correct an see about amending the
> init scripts?
>
> Cheers Mike.
> --
> View this message in context:
> http://old.nabble.com/-SOLVED-Network-init-script-error---tp30166055p30166055.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



      reply	other threads:[~2010-11-09 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <30166055.post@talk.nabble.com>
2010-11-09  4:39 ` [SOLVED]Network init script error?? Steve Sakoman
2010-11-09 18:47   ` Philip Balister [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=4CD9973D.4040201@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.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