traffic_replay: Make packet generation work on a pre-populated DB again
authorTim Beale <timbeale@catalyst.net.nz>
Mon, 5 Nov 2018 22:14:41 +0000 (11:14 +1300)
committerAndrew Bartlett <abartlet@samba.org>
Wed, 7 Nov 2018 16:55:09 +0000 (17:55 +0100)
commit1d7fb66f7630a994dbb261ce417c26d17b409593
treeed6cbe15c4689742c4d4ad3a60101df97221e1ce
parentc7fe4814777696be06e455de5d04ced9a3366d27
traffic_replay: Make packet generation work on a pre-populated DB again

Generate separate machine accounts for populating a large DB vs
replaying network traffic.

We want to use different userAccountControl flags in each of the above
cases (i.e. commit 3338a3e257fa9f28). However, this means that once you
use the --generate-users-only option, you can't replay network packets
against the machine accounts.

We can avoid this problem by creating separate machine accounts for each
of 2 different cases, e.g. STGM-0-x machines for traffic-replay, and
PC-0-x machines for padding out the database.

Signed-off-by: Tim Beale <timbeale@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
python/samba/emulate/traffic.py