search

braice / MuMuDVB

A DVB IPTV streaming software
http://mumudvb.braice.net/
GNU General Public License v2.0
219 stars 133 forks source link

After quitting with ctrl+c and then launch mumudvb the tuner keeps polling #249

Open Dazzler1985 opened 5 years ago

Dazzler1985 commented 5 years ago

After quitting with ctrl+c and then launch mumudvb the tuner keeps polling This is when i clean boot my server sudo mumudvb -d -v -c mumu2.conf Info: Autoconf: We update the channel CAM support Info: Autoconf: Diffusion 6 channels Info: Autoconf: Channel number : 8, service id 409 name : "TV Oranje" Info: Autoconf: Multicast4 ip : 239.100.0.8:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 1900 (PMT), 1901 (Video (MPEG4-AVC)), 1902 (Audio (MPEG1) dut), Info: Autoconf: Channel number : 9, service id 410 name : "SchlagerTV" Info: Autoconf: Multicast4 ip : 239.100.0.9:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2000 (PMT), 2001 (Video (MPEG4-AVC)), 2002 (Audio (MPEG1) ger), Info: Autoconf: Channel number : 10, service id 411 name : "NashvilleTV" Info: Autoconf: Multicast4 ip : 239.100.0.10:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2100 (PMT), 2101 (Video (MPEG4-AVC)), 2102 (Audio (MPEG1) eng), Info: Autoconf: Channel number : 12, service id 413 name : "NL Regionaal 1" Info: Autoconf: Multicast4 ip : 239.100.0.12:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2300 (PMT), 2301 (Video (MPEG4-AVC)), 2302 (Audio (MPEG1) dut), Info: Autoconf: Channel number : 13, service id 414 name : "NL Regionaal 2" Info: Autoconf: Multicast4 ip : 239.100.0.13:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2400 (PMT), 2401 (Video (MPEG4-AVC)), 2402 (Audio (MPEG1) dut), Info: Autoconf: Channel number : 25, service id 432 name : "Enjoy TV HD" Info: Autoconf: Multicast4 ip : 239.100.0.25:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 4200 (PMT), 4201 (Video (MPEG4-AVC)), 4202 (Audio (MPEG2) eng), Info: Autoconf: The NIT version changed, channels number could have changed ! Info: Autoconf: We got the NIT, we update the channel names

So it works and i can watch channels now. But when i quit mumudvb with CTRL+C Main: Caught signal 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 Info: Main: End of streaming. We streamed during 0d 0:02:46 Info: Main: Caught signal 2 - closing cleanly. Info: Main: ========== MuMuDVB version 2.1.0_20181020_mumudvb2 is stopping with ExitCode 0 ==========

and i want to launch it with the same command again: sudo mumudvb -d -v -c mumu2.conf The tuner keeps polling and eventually it will exit with error code: Info: Main: Autoconfiguration, we activate SAP announces. if you want to disable them see the README. Info: Main: Autoconfiguration, we activate PAT rewriting. if you want to disable it see the README. Info: Main: Autoconfiguration, we activate SDT rewriting. if you want to disable it see the README. Info: Main: ========== End of configuration, MuMuDVB version 2.1.0_20181020_mumudvb2 is starting ========== Info: Main: Streaming. Freq 12074000.000000 Info: Tune: Using DVB card "TurboSight TBS 6904 DVB-S/S2 " tuner 0 Info: Tune: Tuning DVB-S to Freq: 1474000 kHz, LO frequency 10600000 kHz Pol:V Srate=30000000, LNB number: 0 Info: Tune: LNB voltage 13V Info: Tune: DISEQC SETTING SUCCEDED Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Info: Main: Card not tuned after timeout - exiting

So i hope someone can point me in the right direction because rebooting everytime i want to change something is not doable.

braice commented 5 years ago

Try to unload/reload the modules of the card, looks like the driver is stuck somewhere.

You can also have a look to the kernel logs

Hope this helps

Brice

On Fri, May 31, 2019 at 3:12 AM Dazzler1985 notifications@github.com wrote:

After quitting with ctrl+c and then launch mumudvb the tuner keeps polling This is when i clean boot my server sudo mumudvb -d -v -c mumu2.conf Info: Autoconf: We update the channel CAM support Info: Autoconf: Diffusion 6 channels Info: Autoconf: Channel number : 8, service id 409 name : "TV Oranje" Info: Autoconf: Multicast4 ip : 239.100.0.8:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 1900 (PMT), 1901 (Video (MPEG4-AVC)), 1902 (Audio (MPEG1) dut), Info: Autoconf: Channel number : 9, service id 410 name : "SchlagerTV" Info: Autoconf: Multicast4 ip : 239.100.0.9:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2000 (PMT), 2001 (Video (MPEG4-AVC)), 2002 (Audio (MPEG1) ger), Info: Autoconf: Channel number : 10, service id 411 name : "NashvilleTV" Info: Autoconf: Multicast4 ip : 239.100.0.10:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2100 (PMT), 2101 (Video (MPEG4-AVC)), 2102 (Audio (MPEG1) eng), Info: Autoconf: Channel number : 12, service id 413 name : "NL Regionaal 1" Info: Autoconf: Multicast4 ip : 239.100.0.12:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2300 (PMT), 2301 (Video (MPEG4-AVC)), 2302 (Audio (MPEG1) dut), Info: Autoconf: Channel number : 13, service id 414 name : "NL Regionaal 2" Info: Autoconf: Multicast4 ip : 239.100.0.13:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 2400 (PMT), 2401 (Video (MPEG4-AVC)), 2402 (Audio (MPEG1) dut), Info: Autoconf: Channel number : 25, service id 432 name : "Enjoy TV HD" Info: Autoconf: Multicast4 ip : 239.100.0.25:1234 Info: Autoconf: Unicast : Channel accessible via the master connection, 0.0.0.0:4242 Deb0: Autoconf: pids : 4200 (PMT), 4201 (Video (MPEG4-AVC)), 4202 (Audio (MPEG2) eng), Info: Autoconf: The NIT version changed, channels number could have changed ! Info: Autoconf: We got the NIT, we update the channel names

So it works and i can watch channels now. But when i quit mumudvb with CTRL+C Main: Caught signal 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 ERRO: Main: Autoconf error 2 Info: Main: End of streaming. We streamed during 0d 0:02:46 Info: Main: Caught signal 2 - closing cleanly. Info: Main: ========== MuMuDVB version 2.1.0_20181020_mumudvb2 is stopping with ExitCode 0 ==========

and i want to launch it with the same command again: sudo mumudvb -d -v -c mumu2.conf The tuner keeps polling and eventually it will exit with error code: Info: Main: Autoconfiguration, we activate SAP announces. if you want to disable them see the README. Info: Main: Autoconfiguration, we activate PAT rewriting. if you want to disable it see the README. Info: Main: Autoconfiguration, we activate SDT rewriting. if you want to disable it see the README. Info: Main: ========== End of configuration, MuMuDVB version 2.1.0_20181020_mumudvb2 is starting ========== Info: Main: Streaming. Freq 12074000.000000 Info: Tune: Using DVB card "TurboSight TBS 6904 DVB-S/S2 " tuner 0 Info: Tune: Tuning DVB-S to Freq: 1474000 kHz, LO frequency 10600000 kHz Pol:V Srate=30000000, LNB number: 0 Info: Tune: LNB voltage 13V Info: Tune: DISEQC SETTING SUCCEDED Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Deb0: Tune: polling.... Info: Tune: FE_STATUS: Info: Main: Card not tuned after timeout - exiting

So i hope someone can point me in the right direction because rebooting everytime i want to change something is not doable.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/249?email_source=notifications&email_token=AACRID7N4LYCKPCTZZQCM2LPYDFWHA5CNFSM4HRU7YJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GW4L6HQ, or mute the thread https://github.com/notifications/unsubscribe-auth/AACRID6SX3HA2QZSE5IP5O3PYDFWHANCNFSM4HRU7YJA .

pszemus commented 5 years ago

I think your issue is similar to mine. Reloading kernel modules helps but it's not a solution for me.

scramatte commented 4 years ago

Similar issue here... Reloading kernel modules helps but it's not a solution for me.

braice commented 4 years ago

Do you have the same issue with other applications?

There is an exit function that is called when Ctrl-C ing MuMuDVB, you might want to close the tuner there.

On Thu, Jan 23, 2020 at 3:08 AM scramatte notifications@github.com wrote:

Similar issue here... Reloading kernel modules helps but it's not a solution for me.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/249?email_source=notifications&email_token=AACRID4FYEP4DPW5HQGMZR3Q7FF7JA5CNFSM4HRU7YJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJWQSHI#issuecomment-577571101, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACRID2QFTIKWBZ74CHQT7LQ7FF7JANCNFSM4HRU7YJA .

borismcfishtank commented 4 years ago

Interestingly I am seeing this same issue now on a TBS 6281SE card. I haven't seen this issue previously on DVB-S or DVB-T cards from them or on the little USB dongles I use for testing.

If I simply run mumudvb -d -c with the following as its contents

tuner=0
freq=474000
delivery_system=DVBT2
unicast=1
ip_http=127.0.0.1
port_http=8458
bandwidth=8MHz
multicast_ipv4=0
autoconf_radios=1
autoconfiguration=full

I can exit prior to mumu reporting and FE_STATUS out, after that if I press Ctrl-C It simply reports that it's caught the signal but just sits there. This is after a fresh reboot and I can replicate this every time. The DVB-S card in the system works fine.

The output I see is:

Info:  Autoconf:  Channel number :   5,   service id 18112  name : "CBBC HD"
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 127.0.0.1:8458
Info:  Autoconf:  Channel number :   6,   service id 20160  name : "TBN UK"
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 127.0.0.1:8458
Info:  Autoconf:  Channel number :   7,   service id 20224  name : "Shopping Quarter"
Info:  Autoconf:        Unicast : Channel accessible via the master connection, 127.0.0.1:8458
Info:  Main:  Channel "BBC TWO HD" down.Card 8
Info:  Main:  Channel "Channel 5 HD" down.Card 8
Info:  Main:  Channel "CBBC HD" down.Card 8
Info:  Main:  Channel "TBN UK" down.Card 8
Info:  Main:  Channel "Shopping Quarter" down.Card 8
^CERRO:  Main:  Caught signal 2
Info:  Main:  Channel "BBC ONE HD" down.Card 8
Info:  Main:  Channel "ITV HD" down.Card 8
Info:  Main:  Channel "Channel 4 HD" down.Card 8
^CERRO:  Main:  Caught signal 2
^CERRO:  Main:  Caught signal 2
ERRO:  Main:  Caught signal 14

The only way I can exit it is kill -9 it.

I've installed the latest drivers and firmware from TBS and I was using the mumudvb deb package, but I just did a git-clone and build to see if that made any difference but the behavior was still the same.

I will attempt to test this later this evening with some other DVB-T cards from TBS and see what I get. I only mention the manufacturer as I've used their DVB-T cards previously and haven't had a problem, but this particular card I don't recall using before.

Any suggestions?

After leaving it running for a while after pressing Ctrl-C it loops output of:

ERRO:  Main:  No data from card 8 in 600s, exiting.
ERRO:  Main:  No data from card 8 in 600s, exiting.
ERRO:  Main:  No data from card 8 in 600s, exiting.
ERRO:  Main:  No data from card 8 in 600s, exiting.
ERRO:  Main:  No data from card 8 in 600s, exiting.
ERRO:  Main:  No data from card 8 in 600s, exiting.
ERRO:  Main:  No data from card 8 in 600s, exiting.
borismcfishtank commented 4 years ago

Adding to this, after some testing it appears to only occur when setting deliver_system to DVBT2 not on DVBT or S or S2

zhang111chao commented 4 years ago

please add skype jack_2431.

zhang111chao commented 4 years ago

Modify the mumudvb source code can solve the above problems 1 . mumudvb.c static void SignalHandler (int signum) { ............. else if (signum == SIGUSR1 || signum == SIGUSR2 || signum == SIGHUP )

------->

    else if (signum == SIGUSR1 || signum == SIGUSR2 || signum == SIGHUP || signum == SIGINT || signum == SIGPIPE || signum == SIGTERM)
  1. mumudvb_mon.c void monitor_func(void arg){ ................... else if (received_signal == SIGHUP) //Sync logs { log_message( log_module, MSG_DEBUG,"Sync logs\n"); sync_logs(); received_signal = 0; } // add source else if (received_signal == SIGINT) //ctrl+c { printf("ctrl+c exit !!!\n"); exit(1); received_signal = 0; } else if (received_signal == SIGALRM) //timeout { printf("timeout exit !!!\n"); exit(1); received_signal = 0; }
    else if (received_signal == SIGTERM) //timeout { printf("timeout exit !!!\n"); exit(1); received_signal = 0; }
zhang111chao commented 4 years ago

1

yo2loj commented 4 years ago

Just a small comment: SIGINT and SIGTERM exit the program in a "normal" fashion, so there is no need to exit with error 1. Use exit(0) instead. Also I would output a message like "Terminating by request" or something on SIGTERM, not "timeout".

borismcfishtank commented 4 years ago

I ended up with this

else if (received_signal == SIGHUP) //Sync logs
{
    log_message( log_module, MSG_DEBUG,"Sync logs\n");
    sync_logs();
    received_signal = 0;
}
else if (received_signal == SIGINT)
{
    printf("SIGINT received, Terminating by request\n");
    exit(0);
}
else if (received_signal == SIGALRM)
{
    printf("SIGALRM received, Terminating by request\n");
    exit(1);
}
else if (received_signal == SIGTERM)
{
    printf("SIGTERM received, Terminating by request\n");
    exit(0);
}

In monitor_func and it will terminate now when hung with ctrl-z or using timeout 60 mumudvb .....

SIGALRM was added as I wasing using timeout to run mumudvb in autoconf for a period of time to just grab the channels.json to parse. I'm not sure if that should exit with a 1 or a 0, other docs I've read suggest SIGALRM should exit with its signal code (14)? Not my area of expertise I'm afraid, but more information is always nice to have.

I'm just curious as to why this is needed for the specific case of DVB-T2 delivery system and it finding channels, but those channels reporting as down.

Any ideas? I'm not over the code base by any means, but this seems like a bit of a brute force approach here when these are gracefully handled when simply tuning DVB-T/S/S2.

braice commented 4 years ago

Hello

The exit value is for any script or other program around MuMuDVB to know why it has excited so as long as it's consistent with common practices it's fine.

Could you please prepare a pull request of your changes for review and potential merge ?

Thank you

On Mon, Jun 29, 2020 at 5:04 AM borismcfishtank notifications@github.com wrote:

I ended up with this

else if (received_signal == SIGHUP) //Sync logs { log_message( log_module, MSG_DEBUG,"Sync logs\n"); sync_logs(); received_signal = 0; } else if (received_signal == SIGINT) { printf("SIGINT received, Terminating by request\n"); exit(0); } else if (received_signal == SIGALRM) { printf("SIGALRM received, Terminating by request\n"); exit(1); } else if (received_signal == SIGTERM) { printf("SIGTERM received, Terminating by request\n"); exit(0); }

In monitor_func and it will terminate now when hung with ctrl-z or using timeout 60 mumudvb .....

SIGALRM was added as I wasing using timeout to run mumudvb in autoconf for a period of time to just grab the channels.json to parse. I'm not sure if that should exit with a 1 or a 0, other docs I've read suggest SIGALRM should exit with its signal code (14)? Not my area of expertise I'm afraid, but more information is always nice to have.

I'm just curious as to why this is needed for the specific case of DVB-T2 delivery system and it finding channels, but those channels reporting as down.

Any ideas? I'm not over the code base by any means, but this seems like a bit of a brute force approach here when these are gracefully handled when simply tuning DVB-T/S/S2.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/braice/MuMuDVB/issues/249#issuecomment-651032505, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACRID3M6OYU2L26A4DM7DTRZBKJTANCNFSM4HRU7YJA .

borismcfishtank commented 4 years ago

Sure thing.