bcast | Broadcast message

Don't split into lines but work with full text as single string.

If you split on empty line - \n\n (double new line) - then you should have every device as separated text.

First word in every device is interface - so it needs split(' ', 1) and [0] to get this word.

IP address is after inet addr: so you can use it to split text and get [1] to have text with IP address at the beginning - so you can use again split(' ', 1) and [0]` to get this IP.

Minimal working code.

I found that there is single space in empty line so it needs \n \n instead of \n\n.

Resuming a copy operation doesn't depend on the smb client or server, but on the application which is doing the copying.

The standard Windows copy doesn't know to resume.

Other (third party) apps (maybe Total Commander?) can be more intelligent about it. You could even write your own app to do a smart copy.

Sometimes using perl is simpler:

MergePreferred (in the absence of eagerComplete being true) will complete when all the inputs have completed, which tends to generally be true of stages in Akka Streams (completion flows down from the start).

So that implies that the merge can't propagate completion until both the input and extractSubtree signal completion. extractSubtree won't signal completion (most likely, without knowing the stages in that flow) until bcast signals completion which (again most likely) won't happen until processResponse signals completion which* won't happen until httpFlow signals completion which* won't happen until createRequest signals completion, which* won't happen until merge signals completion. Because detecting this cycle in general is impossible (consider that there are stages for which completion is entirely dynamic), Akka Streams effectively takes the position that if you want to create a cycle like this, it's on you to determine how to break the cycle.

As you've noticed, eagerComplete being true changes this behavior, but since it will complete as soon as any input completes (which in this case will always be the input, thanks to the cycle) merge completes and cancels demand on extractSubtree (which by itself could (depending on whether the Broadcast has eagerCancel set) cause the downstream to cancel), which will likely result in at least some elements emitted by extractSubtree not getting processed.

If you're absolutely sure that the input completing means that the cycle will eventually dry up, you can use eagerComplete = false if you have some means to complete extractSubtree once the cycle is dry and the input has completed. A broad outline (without knowing what, specifically, is in extractSubtree) for going about this:

• map everything coming into extractSubtree from bcast into a Some of the input
• prematerialize a Source.actorRef to which you can send a None, save the ActorRef (which will be the materialized value of this source)
• merge the input with that prematerialized source
• when extracting the subtree, use a statefulMapConcat stage to track whether a) a None has been seen and b) how many subtrees are pending (initial value 1, add the number of (first generation) children of this node minus 1, i.e. no children subtracts 1); if a None has been seen and no subtrees are pending emit a List(None), otherwise emit a List of each subtree wrapped in a Some
• have a takeWhile(_.isDefined), which will complete once it sees a None
• if you have more complex things (e.g. side effects) in extractSubtrees, you'll have to figure out where to put them
• before merging the outside input, pass it through a watchTermination stage, and in the future callback (on success) send a None to the ActorRef you got when prematerializing the Source.actorRef for extractSubtrees. Thus, when the input completes, watchTermination will fire successfully and effectively send a message to extractSubtrees to watch for when it's completed the inflight tree.

Change this line :

The hex character you're using to send the ctrl+] is wrong. Update your exit console commands to this: exit_console = [ 'exit\n', '\x01D' ]

ASCII Reference: http://www.physics.udel.edu/~watson/scen103/ascii.html

It also looks like you're using the invoke_shell() method, you can use the close() method to exit out of that particular shell and establish a new one as needed.

Paramiko reference: http://docs.paramiko.org/en/stable/api/channel.html

The answer to your question is the same as the answer to this one: How to connect KVM guest vm from mac hosts by ssh?

You're using user-mode networking, which doesn't allow the outside world to connect in to the guest, except if you set up specific port forwarding on your QEMU command line.

In order to receive broadcast packets, you need to set the SO_BROADCAST socket option.

Just ran your code, and it works if you use dist = np.concatenate(dist, axis=0) instead of dist = np.asarray(dist).ravel().reshape(num_row(data),-1) Same thing for memb