Odd comma
Phillip Deneault
deneault at WPI.EDU
Mon Jun 15 14:07:07 EDT 2009
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
>>>>
>>
More information about the argus
mailing list