Skip to contentSkip to conversation

splice syscall runs endlessly, usage problem?

DISCUSSION Helia Correia 2 participants 3 messages Sep 3, 2013

lore
Share & tools
lore
#0 lore raw

Hi,

I am getting to know how to use Trinity, and my last attempt was to run below command (on a Fedora 17 64 bits distribution):
trinity -c splice -C1 -D

My problem is that this command doesn't stop running by itself (started yesterday, was still running this morning so I interrupted it), and I don't understand why but guess this is not an expected behavior, am I right? What should I do to have it run normally (I mean, start and end up gracefully)?

Maybe I overlooked something but seems I couldn't find any documentation as regards to this aspect, as well as how much time it nearly takes to have Trinity run entirely, so any pointers would be highly appreciated.

Thank you and best regards,
Helia

#1 lore raw
Quoted 12 lines · Helia Correia

Hi,

I am getting to know how to use Trinity, and my last attempt was to run below command (on a Fedora 17 64 bits distribution):
trinity -c splice -C1 -D

My problem is that this command doesn't stop running by itself (started yesterday, was still running this morning so I interrupted it), and I don't understand why but guess this is not an expected behavior, am I right? What should I do to have it run normally (I mean, start and end up gracefully)?

Quoted 3 lines

Maybe I overlooked something but seems I couldn't find any documentation as regards to this aspect, as well as how much time it nearly takes to have Trinity run entirely, so any pointers would be highly appreciated.

It will run indefinitly unless you pass -N<number> (or unless it hits a kernel bug that taints the kernel).

Dave

#2 lore raw
Quoted 13 lines · Dave Jones
Quoted 12 lines · Helia Correia

Hi,

I am getting to know how to use Trinity, and my last attempt was to run below command (on a Fedora 17 64 bits distribution):
trinity -c splice -C1 -D

My problem is that this command doesn't stop running by itself (started yesterday, was still running this morning so I interrupted it), and I don't understand why but guess this is not an expected behavior, am I right? What should I do to have it run normally (I mean, start and end up gracefully)?

Quoted 10 lines
Quoted 3 lines

Maybe I overlooked something but seems I couldn't find any documentation as regards to this aspect, as well as how much time it nearly takes to have Trinity run entirely, so any pointers would be highly appreciated.

It will run indefinitly unless you pass -N<number> (or unless it hits a kernel bug that taints the kernel).

Dave

Hi Dave,

Thanks for your input, I will try that (and indeed, -N is mentioned in Trinity usage, my bad :)

Best regards,
Helia