multiple outputs from radium

[Jason Carr]

Unless it's there by default, I would say no. I will double check and make sure the issue persists. 

Are you saying I should build with .threads?

On Jan 24, 2011, at 10:19 AM, Carter Bullard <carter at qosient.com> wrote:

> Jason,
> Haven't heard back from you on this.  One last question, are you running threaded or un-threaded?
> (i.e. is there a .threads file in your clients root directory?)
> 
> Carter
> 
> 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
> 
> On Jan 14, 2011, at 2:48 PM, Jason Carr wrote:
> 
>> Hi Carter,
>> 
>> Looks like upgrading didn't help...  here's the details:
>> 
>> - writing to /data/argus/var/core
>> - every 5 minutes move file to /data/argus/var/core.yyyy.mm.dd.hh.mm
>> - file is processed, compressed and the original deleted, moved to another location
>> - starts writing to /data/argus/var/core
>> 
>> This works just fine unless a client is connected to :561 on the machine.  Then it never starts writing to /data/argus/var/core.  It also doesn't increase the byte count in lsof of the deleted file.
>> 
>> Here's the lsof output:
>> 
>> radium     8417        root    5w      REG              254,1 133472416 2148461937 /data/argus/var/core.2011.01.14.14.25 (deleted)
>> 
>> 
>> - Jason
>> 
>> On Jan 14, 2011, at 11:59 AM, Carter Bullard wrote:
>> 
>>> Hey Jason,
>>> Try the newest argus-clients-3.0.3.21 on the development thread:
>>> 
>>> http://qosient.com/argus/dev/argus-clients-latest.tar.gz
>>> 
>>> That seems like a bug from a long long time ago, regardless that is
>>> definitely a bug.  If the new version doesn't do the trick, send email
>>> quickly!!!!
>>> 
>>> Carter
>>> 
>>> 
>>> On Jan 14, 2011, at 11:26 AM, Jason Carr wrote:
>>> 
>>>> 
>>>> On Jan 14, 2011, at 11:24 AM, John Gerth wrote:
>>>> 
>>>>> On 1/14/11 8:11 AM, Jason Carr wrote:
>>>>>> 
>>>>>> I'm attempting to have a radium provide a stream to two different locations.  I had radium writing to an out file and listening on 561.  It appears as though if I connect to 561, the file is no longer written to.
>>>>>> 
>>>>>> If I have an intermediate radium listening on 10561 with two ra clients, the first client will get disconnected once the second client connects.
>>>>>> 
>>>>>> Is this how it's supposed to work?  Is there any way to do what I'm trying to do?
>>>>>> 
>>>>> I use the straightforward configuration in your first paragraph, i.e. radium writing to
>>>>> a file and listening on 561 and radium happily accepts multiple ra connections without
>>>>> interfering in writing the disk file.
>>>>> 
>>>>> Can you tell us what argus versions and OS platform you're running on?
>>>>> 
>>>>> -- 
>>>>> John Gerth      gerth at graphics.stanford.edu  Gates 378   (650) 725-3273  fax 723-0033
>>>>> 
>>>> 
>>>> Radium Version 3.0.2.beta.11 on Ubuntu x86_64
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 
>