hijack EXEC (ONCE)

Posted by: ukengb

hijack EXEC (ONCE) - 15/02/2005 17:44

Can someone point to me to a definition of the difference between hijack's @EXEC and @EXEC_ONCE config.ini options?

I just cannot find anything that actually explains the difference, so a pointer would really help.

Thanks.
Posted by: wfaulk

Re: hijack EXEC (ONCE) - 15/02/2005 17:51

@EXEC executes the given command every time the player app starts.

@EXEC_ONCE does it on power up and that's it.

(I think that's right.)

I can't find an immediate definitive link. It seems that the Hijack FAQ is less than up-to-date.

Edit: Here you go.
Posted by: ukengb

Re: hijack EXEC (ONCE) - 16/02/2005 06:36

That would make sense as the recommendation for telnetd was @EXEC_ONCE and for running ntpdate was @EXEC.

When the empeg 'sleeps', is the player app still running or has it been terminated and it only starts again when you wake up the empeg?

I just answered that - it's still running. I have 14 player processes - is that right, how come so many?

Under what circumstances would the player app be stopped?
Posted by: Roger

Re: hijack EXEC (ONCE) - 16/02/2005 07:09

Quote:
I just answered that - it's still running. I have 14 player processes - is that right, how come so many?


One per thread, probably.
Posted by: tfabris

Re: hijack EXEC (ONCE) - 16/02/2005 13:08

Quote:
Under what circumstances would the player app be stopped?

- When you Q or Ctrl-C or kill at a shell prompt.

- When you use a configuration tweak to add the "Quit" item to the player's main menu, and then select it from the player's main menu.

- When the player app crashes for some reason.

I'm not sure if the player app stops at any point during a synchronization operation, or if the player just receives a reboot command...