[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH] Add support for DNS TXT records

> 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?

I had to put the quotes there manually since they were not given there
automatically using virBufferVSprintf() call and invocation without them
failed for case you used space in name or value of the TXT record, i.e.
--txt-record=some name, some value since it was taking name (and value)
as the next arguments.


Michal Novotny <minovotn redhat com>, RHCE
Virtualization Team (xen userspace), Red Hat

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]