Odd comma

[Carter Bullard]

Hey Phillip,
No problem!!!  The .rarc is there for convenience, so definitely use  
it as you like!!!!
If you don't print any records to ASCII, then having these options set  
doesn't
affect performance in any way, so no problem at all.

I have fixed the field printing error, and will up load beta.8 clients  
tonight.
There are some important bug fixes to go along with it, so good we got  
this into
this upload.  Actually makes the code smaller ;o)

Carter


On Jun 15, 2009, at 2:47 PM, Phillip Deneault wrote:

> *sigh*  You make an excellent point.
>
> I still want to leave the comma in the ra.conf file since it is a  
> convention I use everywhere else, but yes, I see what you are saying.
>
> Thanks for the extra set of eyes,
> Phil
>
> Carter Bullard wrote:
>> Hey Phillip,
>> Yep, the comma should not be there.  Just wanted to make sure what
>> the bug was.
>> Not related to the bug, but a curiosity. Because rastream() is  
>> writing
>> to a file, its not writing to stdout, so there is no ASCII  
>> conversion, and
>> so there are no fields to separate, and thus no need for a comma.
>> What is it that you expect the RA_FIELD_SPECIFIER to do for you here?
>> Thanks for the bug report, I'll fix it right now.
>> Carter
>> On Jun 15, 2009, at 2:07 PM, Phillip Deneault wrote:
>>> Well, I could, but I'm using RA_FIELD_SPECIFIER in my rastream  
>>> command cause I like comma-delimited things. :-)
>>>
>>> I guess the reason why I'm bringing it up was that rastream/ 
>>> rasplit didn't put that delimiter in the pathname before in argus- 
>>> client-3.0.1 but now in the beta.7 it is in there.  Is it staying  
>>> the way it is now or will it be taken out again?  Or was it just  
>>> an unexpected change when refactoring some code?
>>>
>>> In my opinion, the delimiter should not appear in the pathname  
>>> since $srcid is really the sensor id, not $srcid 
>>> +RA_FIELD_SPECIFIER and its very easy for a RA_FIELD_SPECIFIER to  
>>> be used that has more important meaning to a shell. :-)
>>>
>>> Thanks,
>>> Phil
>>>
>>> Carter Bullard wrote:
>>>> Hey Phillip,
>>>> I suspect that you have a RA_FIELD_SPECIFIER defined in your  
>>>> ~/.rarc file?
>>>> You should be able to override it with a "-c ' ' " on the command  
>>>> line.
>>>> Carter
>>>> On Jun 15, 2009, at 1:36 PM, Phillip Deneault wrote:
>>>>> My apologies,
>>>>>
>>>>> rastream -S <server> -f /path/to/script -B 15 -M time 1m -w / 
>>>>> data/argus/temporal/\$srcid/argus.%Y.%m.%d.%H.%M
>>>>>
>>>>> Dumps out data paths that look like this:
>>>>>
>>>>> /data/argus/temporal/192.168.23.27,/argus.2009.06.15.00.00
>>>>>
>>>>> Thanks,
>>>>> Phil
>>>>>
>>>>> Carter Bullard wrote:
>>>>>> Hey Phillip,
>>>>>> News to me.  Could you send the exact synatx and I'll try to  
>>>>>> replicate the problem here.
>>>>>> Carter
>>>>>> On Jun 15, 2009, at 12:36 PM, Phillip Deneault wrote:
>>>>>>> Has anyone else had an issue with the beta.7 rasplit and  
>>>>>>> rastream clients appending a comma after the ip address when  
>>>>>>> using the $srcid macro in the paths?
>>>>>>>
>>>>>>> Or did I do something wrong?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Phil
>>>>>>>
>>>>>
>>>
>> Carter Bullard
>> CEO/President
>> QoSient, LLC
>> 150 E 57th Street Suite 12D
>> New York, New York  10022
>> +1 212 588-9133 Phone
>> +1 212 588-9134 Fax
>

Carter Bullard
CEO/President
QoSient, LLC
150 E 57th Street Suite 12D
New York, New York  10022

+1 212 588-9133 Phone
+1 212 588-9134 Fax



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3815 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20090615/23d84928/attachment.bin>