On 03/30/2011 01:00 PM, Michal Novotny wrote:
I think you should triage it a bit more, e.g. with strace -ff. Anyway, there is no hurry of doing this I think. Well, you mean to use strace on the daemonized process? Wherever it helps understanding what's happening. :)
Also, I've been testing the --txt-record once again and not grabbed it with wireshark and I had to query the "txt-record" TXT record for this and the wireshark was showing the quotes there as well now. Should I disable it then and use the working syntax for record name which (according to my testing) is to use *--txt-record=txt-record,"some value, which is something"* instead, i.e. to not use quotes in the name? I absolutely cannot parse this sentence. Well, what I meant was that if I invoked dnsmasq with --txt-record="txt-record", "some value" then I had to dig for "txt-record" with quotes, i.e. using the dig TXT \"txt-record\" syntax in bash. In Wireshark it was showing request for record with the quotes, i.e. "txt-record" instead of querying just for txt-record, i.e. without quotes. To be able to query it without quotes I had to invoke dnsmasq with --txt-record=txt-record, "some value" arguments. Who was escaping the double-quotes?
Paolo
Well, it's working without the quotes and I just made a typo there before and that's why invocation failed. Now it's OK without the quotes. Michal -- Michal Novotny <minovotn@redhat.com>, RHCE Virtualization Team (xen userspace), Red Hat