Ticket #159 (new wishlist)

Opened 10 years ago

Last modified 10 years ago

Possible Trig2Disk limit

Reported by: stefan Owned by: somebody
Priority: minor Milestone:
Component: ALL modules Version:
Keywords: Cc:


From: salichon@… 5/6/2010

Hi all,

I have been very basic: With Trig2disk I save the traces of events on numerous channels, using a SAC format. It appears that the trig2disk seems limited in number.

Though I put a Maxtraces parameter to overestimated traces (400) (and tracebufferlen to 10240),

the process shuts down (zombie) when I reach more than 107 SAC traces ... I must add that it saves the traces in any cases but stops (zombie) just before the Postproc commands.

I check and shift the saved channels to see if it comes from one of these, but apparently not.

It is not a huge problem, but I wonder If there is a hardcoded limitation on the saved files.

Regards, Jerome

Change History

comment:1 Changed 10 years ago by paulf

We need more information on this one. The SACPUTAWAY routines have a limit on some items, but they write more than just the SAC files themselves. They also write a filelist file and a macro file. Are these being written too? Or is it dying in that process? This is the first I have heard of a 107 file limitation, but I don't have an easy way to test this out at all.

Note: See TracTickets for help on using tickets.