Fix container death after smbd initializes.

[charles-m-knox]

I've seen this in a couple different rpi-samba images. Basically something like this happens:

Creating network "networkshares_default" with the default driver
Creating networkshares_500hdd1_1
Attaching to networkshares_500hdd1_1
500hdd1_1  | Add user 'osmc' with password 'pwd' Added user osmc.
500hdd1_1  | DONE
500hdd1_1  | Add user 'chuck' with password 'pwd' Added user chuck.
500hdd1_1  | DONE
500hdd1_1  | Add share '500hdd1' path '/share/data' read+write for users: osmc chuck DONE
500hdd1_1  | smbd version 4.2.11 started.
500hdd1_1  | Copyright Andrew Tridgell and the Samba Team 1992-2014
500hdd1_1  | STATUS=daemon 'smbd' finished starting up and ready to serve connections
networkshares_500hdd1_1 exited with code 0

This fixes the issue, somehow - thanks to this stack exchange article: http://unix.stackexchange.com/a/277119

After building the image -- you can pull it via docker pull charlesmknox/rpi-samba if you want to test -- the container no longer exits with code 0:

Creating network "networkshares_default" with the default driver
Creating networkshares_500hdd1_1
Attaching to networkshares_500hdd1_1
500hdd1_1  | Add user 'osmc' with password 'pwd' Added user osmc.
500hdd1_1  | DONE
500hdd1_1  | Add user 'chuck' with password 'pwd' Added user chuck.
500hdd1_1  | DONE
500hdd1_1  | Add share '500hdd1' path '/share/data' read+write for users: osmc chuck DONE
500hdd1_1  | smbd version 4.2.11 started.
500hdd1_1  | Copyright Andrew Tridgell and the Samba Team 1992-2014
500hdd1_1  | STATUS=daemon 'smbd' finished starting up and ready to serve connections

The fix is simply to append < /dev/null to the last line in /run.sh. Why does this work? I don't know. But it works, and on top of that, my share works too!

[charles-m-knox]

The other two commits were just interim changes while I tested the change, just look at the "Files Changed" tab to see what this pull request will alter.

[dastrasmue]

Thanks Chuck, I wasn't aware of this bug. I will also create a new container Version for the docker hub.