> Using "start && client -f commands.txt && stop" a) seems unreliable and b) > would seem to need a sleep anyway as otherwise the client tries to connect > while karaf is still starting.
Note that trying the "-d" and "-r" options on the bin/client along with -f seems to result in either "miss the commands file" or "miss the attempts" depending on which way round you put the options (karaf 4.2.2). I'll have a read though the source and see if I can find out why.
