Oscam telnet command for stopping

Hi.

First you need to find out which launcher for Oscam is used in your system (sysctl / systemd or maybe "init.d" scripts). Accordingly, it is appropriate to drop or restart the service accordingly.

If you are using an "init.d" script, then there should be functional parameters for that script, such as start | stop | restart, for example:

/etc/init.d/softcam restart

-or:

/etc/init.d/softcam.oscam restart

If you want to list files that contain the word "cam" in the file name (inside the "/etc/init.d" folder), use this command:

ls -al /etc/init.d/*cam*

Of course, you can also "kill" the process, but first find out its name, for example like this:

ps -aux | grep -i "cam"

-or:

ps | grep -i "cam"

And here in the list you will probably see your Oscam and its name. Then it should be enough to use a hard kill:

killall -9 <process_name>

When using the "ps" command, you may notice the entire command-line of your Oscam, i.e. including the arguments placed behind the Oscam binary file. To start Oscam again, use exactly the same command-line including the same arguments. For example:

/usr/bin/oscam -b -r 2

Good Luck :)

/// EDIT:

Are you using OE2.5 ?

Oh sorry... so then you probably use "sysctl" and not "init.d", for purpose of the start | stop | restart services. This tool is used a little differently. Of course, you can use the sysctl command to control processes (including the oscam process).

Example: systemctl restart <service_name>

Here is more info: https://crunchify.com/systemd-…respawn-process-linux-os/

Hi.

You could paste a copy from the Linux console into the CODE TAG. It's then clearer.

Also, the "killall" command is unfortunately not quite universal and may behave a little differently, in different versions of it (BusyBox complex versions as well as in full-fledged Linux versions). In some versions, the signal number is not used, but the signal name, such as:

killall -SIGKILL oscam_11704

And somewhere I think the hyphen in front of the signal must not be used. I don't remember exactly. Sorry. But I know it's a mess with the new versions.

You can also use the "kill" command to kill processes, not just "killall". However, then you need to find out all PID numbers (values representing the process number). For example, as follows:

kill -n 9 $(pidof oscam_11704)

- or :

kill -9 $(pidof oscam_11704)

- or :

kill $(pidof oscam_11704)

(It really depends on the version of your "kill" command (or rather "kill" tool) that how it will behave.)

However, using killall and kill is very difficult on new Linux systems (Dreambox firmware) or even compared to old versions, many things always change! Therefore, it is better to use the standard path. If you show me an IPK package for your Oscam, I'll unpack it and tell you exactly how Oscam restarts in your case :) - based on the unpacked IPK package (using a 7-zip archiver you can unpack).

So... again... you must first know what startup principle is used on your Linux system. Maybe sysctl is not used for Oscam but systemd. You have to find out first.

Depending on what you copied from your console, you still haven't tried the "init.d" scripts !

I dont know all Enigma2 distributions in the world and I dont know in which Enigma2 there are exactly what options (installed components and tools of the Linux system).

OpenDreambox 2.5 should use sysctl, if I'm not mistaken. But the systemd / init.d service launcher can also be used there.

Or maybe "start-stop-daemon" is also used in your case. I really do not know. Linux systems are very extensive in this regard - in terms of processes and their management by the system administrator.

How do you know it doesn't work ? This "sysctl" only stop the process but leave it in system memory. Test if Oscam-Webif works. If it doesn't work, then Oscam is stopped.

So what ? All is done ?

Which solution ultimately works in your case ? In case someone comes and finds this discussion thread ... maybe it will help other users :) ...in the future.

36d1ae8c7ec96be8b1.jpg

well done @ddinc

ps

i don't think you really need that

oscam check script when using systemd

OK... ddinc ... now a little off topic:

For what purpose do you actually need to "kill" or "restart" the Oscam process ?

:)

i havent seen your systemd script

but most have a restart after 5 seconds if it stops

typical systemd script

[Unit]
Description=OScam instance 1
After=network.target
Requires=network.target

[Service]
Type=forking
ExecStart=/usr/local/bin/oscam1 -b -c /usr/local/etc/oscam1 -t /tmp/.oscam1 -B /var/run/oscam1.pid -I oscam1 -d 0 -r 2 -p 1024
ExecStop=/bin/rm /var/run/oscam1.pid
TimeoutStopSec=1
Restart=always
RestartSec=5
StartLimitInterval=0

[Install]
WantedBy=multi-user.target

Try adding this as well (under the "Service" configuration section):

[Service]
Restart=always
RestartSec=5
StartLimitInterval=0

Although I'm not sure if this will be recognized by your Lilnux, used in your set-top box. I hope so.

You should not have created this new file there. It probably already exists there. Or have you already looked for him and not found him? You should have used one that already exists there (of course only if you find it there).