🚀 go-pugleaf

Apparently port access rights are not maintained across
a fork.  My own experience is that receive rights are not maintained
across a fork - after forking my child process tells me that the port
is invalid.  I presume this is due to the restriction that only
one task can have receive rights to a port at any time.  However, 
my child task also seems to have lost send rights to yet another port.  
Since multiple tasks can hold send rights to a port, the previous
restriction does not apply.  What's the scoop?

Although nothing about port access rights is mentioned in the 
netname_look_up() documentation, my experience is that a task can send 
messages to a port after performing a netname_look_up.  This seems to 
imply that port access rights are being transferred.  Is this true?

Many thanks!

Anne