Multiple Slingboxes on Linux (Debian)

[tom76017]

Will this work on my Linux server to support a SB500 and M1 from on 1 server?

sling.service

[Unit]
Description=SlingBox Server Service
After=multi-user.target

[Service]
Type=idle
User=slingbox
WorkingDirectory=/home/slingbox
StandardOutput=append:/tmp/sling.log
StandardError=append:/tmp/sling.log
ExecStart=/usr/bin/python3 -u slingbox_server.py config-SB500.ini config-M1.ini
Restart=always

[Install]
WantedBy=multi-user.target

[GerryDazoo]

The short is it “should” depending of which version of system is running on your box. You may find the log file isn’t being updated. I’ve had to adjust the service config for older systemd’s. Something like this [Unit] Description=SlingBox Server Service After=multi-user.target [Service] Type=idle User=slingbox WorkingDirectory=/home/slingbox ExecStart=/bin/bash -ce "exec /usr/bin/python3 -u slingbox_server.py 500_config.ini 500lbr_config.ini >> /tmp/sling.log 2>&1" Restart=always [Install] WantedBy=multi-user.target From: tom76017 ***@***.***> Sent: Wednesday, August 17, 2022 3:10 PM To: GerryDazoo/Slinger ***@***.***> Cc: Subscribed ***@***.***> Subject: [GerryDazoo/Slinger] Multiple Slingboxes on Linux (Debian) (Discussion #27) Will this work on my Linux server to support a SB500 and M1 from on 1 server? [Unit] Description=SlingBox Server Service After=multi-user.target [Service] Type=idle User=slingbox WorkingDirectory=/home/slingbox StandardOutput=append:/tmp/sling.log StandardError=append:/tmp/sling.log ExecStart=/usr/bin/python3 -u slingbox_server.py config-SB500.ini config-M1.ini Restart=always [Install] WantedBy=multi-user.target — Reply to this email directly, view it on GitHub <#27> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYOYVQM7TCKK47A66ZERNZTVZUTJHANCNFSM562OV3CQ> . You are receiving this because you are subscribed to this thread. <https://github.com/notifications/beacon/AYOYVQLTQS3LIQYPGH3URL3VZUTJHA5CNFSM562OV3C2YY3PNVWWK3TUL52HS4DFVJCGS43DOVZXG2LPN2VGG33NNVSW45C7NFSM4ACBZYCA.gif> Message ID: ***@***.*** ***@***.***> >

[tom76017]

Works on Debian with 2 500's and 1 M1. I do get an occasional broken pipe error. Th remote works fine with both my TiVo Mini A92 and A95's. Just a little slow.

BTW, I noticed the a hard reset changes the password and finderid. I wonder what will happen with the passwod and finderid with a hard reset after EOL.

[GerryDazoo]

That’s good news. Can you can you cut and paste the lines around the broken pipe error for me? Make sure you’ve updated the system TCP buffer sizes as described in the readme. It’s not the remote that’s slow (check it while watching the slingbox input directly). It’s video stream buffering, etc in your player. I’m assuming you’re talking about VLC. You can google up how to minimize the delays but it’s a pain. I’ve been using ffplayer with some success. With the proper command line the delays make the remote usable. i.e. C:\ffmpeg\ffplay.exe -infbuf -probesize 32 -analyzeduration 0 -flags nobuffer -flags low_delay http://127.0.0.1:65432/slingbox Yes a hard reset generates a new finderid and password. I would NOT do a hard reset after EOL. I’m not brave enough to give it a test but if you want to see what might happen you could block internet access to your PC. I suspect it would fail miserably and leave your box in an unusable state because it can’t get a new password and finderid from Mr. Sling. After the test you could re-enable Internet access and should be able to recover the slingbox. * Gerry From: tom76017 ***@***.***> Sent: Friday, August 19, 2022 1:58 PM To: GerryDazoo/Slinger ***@***.***> Cc: GerryDazoo ***@***.***>; Comment ***@***.***> Subject: Re: [GerryDazoo/Slinger] Multiple Slingboxes on Linux (Debian) (Discussion #27) Works on Debian with 2 500's and 1 M1. I do get an occasional broken pipe error. Th remote works fine with both my TiVo Mini A92 and A95's. Just a little slow. BTW, I noticed the a hard reset changes the password and finderid. I wonder what will happen with the passwod and finderid with a hard reset after EOL. — Reply to this email directly, view it on GitHub <#27 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYOYVQKBHX3ZCAEQUQN5TRDVZ64KFANCNFSM562OV3CQ> . You are receiving this because you commented. <https://github.com/notifications/beacon/AYOYVQN2QOVFZRG5L3KL4BLVZ64KFA5CNFSM562OV3C2YY3PNVWWK3TUL52HS4DFWFCGS43DOVZXG2LPNZBW63LNMVXHJKTDN5WW2ZLOORPWSZGOAA2GGDY.gif> Message ID: ***@***.*** ***@***.***> >

[GerryDazoo]

Based on my testing ( I used the firewall to block all outgoing connections to the WAN), do NOT do a hard reset after EOL. The sling software will timeout trying to talk to the cloud and there will be no way to recover/set the password.