Did you really need tinyproxy in the target template? It should be
needed only in your netvm... Or are you saying that tinyproxy
was missing in your netvm?
it was red in my fed24 minimal journalctl.
after i installed it, it went away (currently most things i am doing are
kind of blind
i am currently looking whether i can do the same in a top file (but i doubt
it, since there is no templating in top files)
And the last sentence is exactly the reason why it's tricky to have it
in one place.
well it seems we were totally wrong.
you can put jinja code in your top file.
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Jan 17, 2017 at 04:40:24PM +0100, john.david.r.smith wrote:
> > > 6)
> > > currently i really don't like the way the configuration works.
> > > i have a top file where i execute some states for dom0
> > > these states create and configure my
1)
even when some states fail for some vm, the cli tool displays ok. it would
be better, if it displayed error in case of an error (some errors are
displayed).
Can you provide example error which wasn't detected? Regardless of the
result, output is logged to /var/log/qubes/mgmt-*.log in dom0.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Jan 16, 2017 at 11:24:13PM +0100, john.david.r.smith wrote:
> hi.
> i played around with salt and noticed a few things/ have some questions:
> 1)
> even when some states fail for some vm, the cli tool displays ok. it would
> be better, if it