I like to listen to one particular radio and I have made myself a little launcher using vlc that is simply like this :
#!/bin/sh
vlc http://mp3lg.tdf-cdn.com/fip/all/fiphautdebit.mp3
What I would like to do is to have this instance of vlc - I have allowed multiple instances in vlc preferences, immediatly hidden from my desktop. I would like it to run in the 'background'.
How could I achieve this ? I tried to add >/dev/null at the end but without success.
I am on Mint 17 Rebecca, and I am trying this both for fun and because RadioTray and GreatLittleRadioPlayer don't work on my system and I haven't been able to find someone with the same issue on the web.
Thanks
Default VLC depends on X, therefore cannot be run headless. You will need to install vlc-nox to run a headless vlc in the background.
Source: What is vlc-nox?
Related
I've used xampp (lampp) to run an Apache2 server out of my Intel ComputeStick with Ubuntu 18.04.1 installed. I've written a .cgi script with perl:
#!/usr/bin/env perl
use strict;
use warnings;
use CGI;
print CGI::header();
system("vlc /home/jack/Desktop/ayni1.mp4");
However, when I hop onto my laptop (Win10) and use Chrome to visit http://12.345.678.90:80/dashboard/perl/ayni1.cgi (That's my server, and that directory does exist), nothing happens on the hosting machine. In the browser, this line is displayed:
VLC media player 3.0.3 Vetinari Command Line Interface initialized. Type `help' for help. > Shutting down.
I'm afraid I don't quite understand what's happening. I thought cgi scripts interacted directly with the command line; i.e. they could issue commands to Terminal directly. Was I mistaken in that? What am I doing wrong?
Sorry, I know this question is somewhat scattered. If needed, I'll try to provide clarification as best I can.
I'm somewhat new to all of this.
I think you have set VLC to open a command line interface automatically.
Reset the VLC preferences and it should work normally again.
I'm working on some tuning of my raspberry. So I decided that midori should start automaticly after autologin.
With startx it works without problems, but X is still to ressource hungry. So I'll start midori with xinit and matchbox.
As test, I use as user "pi" this command "xinit ./home/pi/startmidori.sh" and it works.
So I'll put this into my rc.local file.
There is the command "su -l pi -c xinit ./home/pi/startmidori.sh", this doesn't work. I don't know why, but xinit exit immediately after starting.
How can I solve this? In guides I find this kind of solution, but for it doesn't work. I tryed to run it as root but it doesn't work, too. I've no idea why.
Check this for more information: Running X from The X Window User HOWTO
In general you always need a wrapper and you must run X with root, since it needs raw access to hardware devices.
So I suggest you to install lightweight display manager like LightDM if possible it has almost no footprint and then easy you can set it up to auto login with desired user and run desired window manager like matchbox in your case.
My cygwin workflow is as follows
Run XServer
Start xfce session (by running xfce4-session)
Start xfce4-terminal
Everything works well, except that xfce4-session seems to bring up an empty floating-panel, which I'm unable to hide without killing the session itself. Is there a way to configure xfce so this panel doesn't get shown?
PS: Running xfce4-terminal by itself gives me the terminal emulator, but the terminal behaves nicer when xfce4-session is active--text is anti-aliased, icons are slicker, etc.
Try killing just the panel process itself:
killall xfce4-panel
I believe the right way to start xfce is running /usr/bin/startxfce4.
If you want to run it the way you are, perhaps you could right click on the panel and click remove to get rid of it.
xfwm4 is the Window Manager, xfce-session is the session manager which "Restores your session on startup and allows you to shutdown the computer from Xfce."
I just found out that running xfsettingsd will load the XFCE theme and settings.
Using that command you can initiate the XFCE configuration without running the full desktop environment.
xfsettingsd &; xfce4-terminal;
Here is the situation, I'm planning to use a simple script to start a program call "STAF", when the Suse system is fully booted. I have achieved this by putting it in the "/etc/init.d/", but this script is basically executed at the background, which means that I cannot see its progress.
When the "STAF" is started this way it works but it doesn't show any working progress when its running service (for example ping, or system backup), instead if I start the "STAF" manually by running the same script whit a terminal, the working progress of "STAF" can be seen on the terminal. Its sort of like the program needs to be started with a interactive terminal, but how can I make this starting process automatic and it should imitate human opening a terminal and run the script?
Sorry if I explained it poorly because its a confusing situation. Thanks.
First, go to the KDE Startup and Shutdown options under System Settings. Then add this command as a new startup script:
konsole -e bash nameofyourscript.sh
I believe the screen utility can do what you describe. Instead of running STAF on startup, you would run screen STAF. To open that terminal, you would run screen -ls to get the screen ID, and screen -r ... to open it.
(Disclaimer: I have not tried this.)
I'm creating an application (command line script) to play videos directly to the secondary monitor, which is connected either via VGA or HDMI.
The video player itself is cvlc, with command cvlc -f myvideo.avi.
Can anyone please help about the script to run the cvlc directly to secondary monitor regardless of which monitor it was launched from.
i've tried DISPLAY=":0.1" vlc -f myvideo.avi, but results a scrambled unusable video player.
Thanks.
Try using the --x11-display :0.1 flag. It's not part of the --help output but I use it on my 2.0.1 vlc.