Project Home
Project Home		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Networking/Discussion/io-net migration/waitfor io-pkt/List of Posts
Forum Topic - waitfor io-pkt: (7 Items)
   
Update
Matthias Klein
09/10/2008 10:38 AM
post13154
waitfor io-pkt   
On QNX 6.3 I started io-net with the following commands:

io-net -p tcpip forward -p qnet &
waitfor /dev/io-net

On QNX 6.4 I want to use the following commands:

io-pkt-v4-hc -p tcpip forward -p qnet &
waitfor /dev/io-net

The problem is, that io-pkt doesn't create the io-net path.


What path can I use with the waitfor command ?
Sean Boudreau(deleted)
09/10/2008 10:41 AM
post13155
Re: waitfor io-pkt   
On Wed, Sep 10, 2008 at 10:38:56AM -0400, Matthias Klein wrote:
> On QNX 6.3 I started io-net with the following commands:
> 
> io-net -p tcpip forward -p qnet &
> waitfor /dev/io-net
> 
> On QNX 6.4 I want to use the following commands:
> 
> io-pkt-v4-hc -p tcpip forward -p qnet &
> waitfor /dev/io-net
> 
> The problem is, that io-pkt doesn't create the io-net path.
> 
> 
> What path can I use with the waitfor command ?

/dev/socket which will also work for io-net with the tcpip stack
loaded in.

Or if you pass the 'prefix' option as in

# io-pkt -ptcpip prefix=/foo

/foo/dev/socket

-seanb
Matthias Klein
09/11/2008 9:00 AM
post13242
Re: waitfor io-pkt   
Waiting for /dev/socket isn't enough in the case qnet is used.

I try the following commands in a startup script:

io-pkt-v4-hc -p tcpip forward -p qnet &
waitfor /dev/socket
waitfor /net
waitfor /dev/netmgr
waitfor /dev/bpf
waitfor /dev/crypto
chkfsys -rsqp /

I get the following error from chkfsys:
Can't get filesystem size -- stat(/net/pstation.qnet/dev/hd0t79)

If I insert a "sleep 1" before the chkfsys it runs fine.
If I remove the qnet protocol from io-pkt it runs also fine.


Which waitfor-path should I use for qnet ?

(I use the second pre-release of QNX 6.4 with VMware 6)
Robert Craig
09/11/2008 3:15 PM
post13275
RE: waitfor io-pkt   
Hi Mathias:

	Do you see different behaviour with io-net?  What is very likely
happening is that the chkfsys is attempting to validate a remote host
file system before it has fully come up in QNET.  Qnet is obviously up
and running at this point in time since you're successfully accessing
the /net directory, so from the local point of view, everything is as it
should be and there's nothing further it should be waiting on.  I think
that there's a very good chance that success or failure of the chkfsys
would depend upon the number of hosts in your networks with a large
number of hosts guaranteed to fail while a small number may or may not
fail depending on timing. 

I would also think that running chkfsys (with repair) on a remote node
file system over the network is, to say the least dangerous (e.g. what
happens if you try and repair the file system and you get a network
outage).


	Robert.

-----Original Message-----
From: Matthias Klein [mailto:community-noreply@qnx.com] 
Sent: Thursday, September 11, 2008 9:00 AM
To: ionetmig-networking
Subject: Re: waitfor io-pkt

Waiting for /dev/socket isn't enough in the case qnet is used.

I try the following commands in a startup script:

io-pkt-v4-hc -p tcpip forward -p qnet &
waitfor /dev/socket
waitfor /net
waitfor /dev/netmgr
waitfor /dev/bpf
waitfor /dev/crypto
chkfsys -rsqp /

I get the following error from chkfsys:
Can't get filesystem size -- stat(/net/pstation.qnet/dev/hd0t79)

If I insert a "sleep 1" before the chkfsys it runs fine.
If I remove the qnet protocol from io-pkt it runs also fine.


Which waitfor-path should I use for qnet ?

(I use the second pre-release of QNX 6.4 with VMware 6)


_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post13242
Matthias Klein
09/11/2008 5:50 PM
post13292
Re: RE: waitfor io-pkt   
Hello Robert,

>I would also think that running chkfsys (with repair) on a remote node
>file system over the network is, to say the least dangerous (e.g. what
>happens if you try and repair the file system and you get a network
>outage).

I only want to check the filesystem on the local harddisk.
/net/pstation.qnet/dev/hd0t79 is the local harddisk.

I don't understand why chkfsys complain about the local harddisk.
(/net/pstation.qnet is the own node)


Which command should I use the check the root filesystem on the harddisk ?
Robert Craig
09/11/2008 5:53 PM
post13293
RE: RE: waitfor io-pkt   
Hmmm...  That's interesting.  I hadn't realized that it was that entry
was for the local hard disk.

How about chkfsys /dev/hd0t79 instead?  I don't think that it'll start
re-cursing through other mountpoints (such as that established by qnet)
in that case...

Either that or (even better) perform the chkfsys BEFORE you start io-pkt
/ qnet.

	R.

-----Original Message-----
From: Matthias Klein [mailto:community-noreply@qnx.com] 
Sent: Thursday, September 11, 2008 5:51 PM
To: ionetmig-networking
Subject: Re: RE: waitfor io-pkt

Hello Robert,

>I would also think that running chkfsys (with repair) on a remote node
>file system over the network is, to say the least dangerous (e.g. what
>happens if you try and repair the file system and you get a network
>outage).

I only want to check the filesystem on the local harddisk.
/net/pstation.qnet/dev/hd0t79 is the local harddisk.

I don't understand why chkfsys complain about the local harddisk.
(/net/pstation.qnet is the own node)


Which command should I use the check the root filesystem on the harddisk
?


_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post13292
Matthias Klein
09/12/2008 4:46 PM
post13366
Re: RE: RE: waitfor io-pkt   
Hello Robert,

when I use chkfsys /dev/hd0t79 it works fine.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems