Elrond's questions

We can use gather_subset at play level. Is it possible to use it on a per host level? Like putting it in a host_vars file? My quick testing on 2.2.1.0 did not work out.

My problem at hand: I have a host, for which get_cpu_facts fails. And really, I never need hardware facts for this host, so I would like to put "!hardware" in its gather_subset.

On the play-level, we have serial: 1 to allow us to run the whole play one host at a time. But I haven't found a simple way to do this on a single task. This is especially relevant, if the task in question doesn't perform proper locking (for whatever reason).

One obvious answer is to put the task in its own play. But that doesn't help with roles. (Having to put serial: 1 on the play using the role isn't really intuitive.)

I have a router/host with multiple public IP addresses. I want to change the source ip depending on some destination addresses. This has already been asked here:

If the traffic originates from some internal/other host, then the source address has already been selected and we are forced to use NAT, fine.

So we're with local originated traffic. The answer to the above question suggests, that this only works using appropiate ip route entries using src.

• Can one create that entry without replicating the default route (which might change for example)?

Another answer on the contrary says, that NAT also works for local originated traffic.

• Does NAT work for local traffic?
• IF it works, is there any recommendations whether NAT or routing should be used? My current thoughts go like this:
  • NAT has the pro, that it handles both local and non-local traffic in one rule (one place to maintain config is good!)
  • NAT has all the cons of NAT.
  • Routing makes things more obvious (and possibly goes into IGP easier).

I have read Can I create a DC without a DNS Server?. But my question is a bit different.

I have one client in a completely different subnet from the DC. That client does not have access to the appropiate DNS structure for the domain, but can otherwise connect to the DC. I would like to tell that client "the DC for domain example.net is at dc1.site2.example.com". I have seen, that this sort of thing is possible for kerberos things using ksetup /addkdc. Is there something like this for generic AD?

I want to add an entry to my suoders to allow one user to run a command with exactly one non-option argument.

# tail -1 /etc/sudoers
ALL     ALL = (:tool) NOPASSWD: /bin/echo [a-z]*
$ sudo -g tool /bin/echo abc def
abc def
$ sudo -g tool /bin/echo -abc def
[sudo] password for user: 

Can I do that using the sudoers sytnax? Or do I need to create a helper script?

I am trying to create some monitoring based on flow-tools: I have flow-capture running to log things into directories. Now I need to merge files together for my analysation interval. I have looked at the manpage for flow-cat and flow-merge. They talk about interleaving and chronological order. As the files by flow-capture are already quite sorted, I wonder, what the real difference is in my case?