Hi, I wish to run YAAC on my armbian server (ubuntu bionic ) without GUI. Just a timed beacon transmission and maybe an incoming RX log file. Is this possible ?
Last edit: Rein Mann 2019-07-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is possible, but slightly awkward to set up. YAAC has a -nogui command line option that does not open the UI windows. However, all the configuration controls are graphical, so you might have to start YAAC graphically to configure the beacon, ports, etc., then shut it down and restart it with -nogui.
Note that YAAC is a full X-windows application on Linux, so you can always direct the DISPLAY environment variable to another network host running an X-windows server (assuming that X server is configured to allow other computers to connect to its screen, keyboard, and mouse).
Hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is possible, but slightly awkward to set up. YAAC has a -nogui
command line option that does not open the UI windows. However, all the
configuration controls are graphical, so you might have to start YAAC
graphically to configure the beacon, ports, etc., then shut it down and
restart it with -nogui.
Note that YAAC is a full X-windows application on Linux, so you can always
direct the DISPLAY environment variable to another network host running an
X-windows server (assuming that X server is configured to allow other
computers to connect to its screen, keyboard, and mouse).
Hi Andrew,
After running YAAC with the switch -nogui I inactivated the desktop gui and restarted YAAC from linux cmd line. This works fine.
Question is: Where is the file that contains the configuration (callsign, coordinates and preferences) .
I wish to lift it out and transfer it to another OS that runs without a desktop gui.
R.
Last edit: Rein Mann 2019-10-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, there is no single file, and the location of the data is operating-system-specific. I deliberately designed YAAC not to allow configs to be easily copied from one system to another, because someone would be sure not to change the callsign-SSID assignments to be unique and therefore have duplicate stations on the network.
This is why I mentioned the DISPLAY environment variable. If your target headless system still has the X windows client libraries installed (libX, libXaw, etc.), you can start YAAC with the DISPLAY environment variable pointing to another computer that is running a graphical desktop. For example:
on the graphical system:
xhost +headlesssystem
on the headless system:
DISPLAY=linuxwithscreen:0 java -jar YAAC.jar
This way, you can use the screen on the graphical system (named "linuxwithscreen" in the above example) to access the configuration windows on the headless system (named "headlesssystem" in the example). You would have to install the graphical part of the Java runtime as well as the X client libraries for Java to be able to bring up the graphical screens.
The xhost command is used to tell the local X server that specific other computers are allowed to connect to the screen, keyboard, and mouse. By default, this is disabled to prevent random attackers from taking over your screen and capturing your keystrokes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I wish to run YAAC on my armbian server (ubuntu bionic ) without GUI. Just a timed beacon transmission and maybe an incoming RX log file. Is this possible ?
Last edit: Rein Mann 2019-07-29
This is possible, but slightly awkward to set up. YAAC has a -nogui command line option that does not open the UI windows. However, all the configuration controls are graphical, so you might have to start YAAC graphically to configure the beacon, ports, etc., then shut it down and restart it with -nogui.
Note that YAAC is a full X-windows application on Linux, so you can always direct the DISPLAY environment variable to another network host running an X-windows server (assuming that X server is configured to allow other computers to connect to its screen, keyboard, and mouse).
Hope this helps.
Thanks Andrew, I was not aware of the -nogui switch. It's just the thing I
need. :)
On Mon, 29 Jul 2019 at 23:29, Andrew Pavlin apavlin@users.sourceforge.net
wrote:
Hi Andrew,
After running YAAC with the switch -nogui I inactivated the desktop gui and restarted YAAC from linux cmd line. This works fine.
Question is: Where is the file that contains the configuration (callsign, coordinates and preferences) .
I wish to lift it out and transfer it to another OS that runs without a desktop gui.
R.
Last edit: Rein Mann 2019-10-11
Unfortunately, there is no single file, and the location of the data is operating-system-specific. I deliberately designed YAAC not to allow configs to be easily copied from one system to another, because someone would be sure not to change the callsign-SSID assignments to be unique and therefore have duplicate stations on the network.
This is why I mentioned the DISPLAY environment variable. If your target headless system still has the X windows client libraries installed (libX, libXaw, etc.), you can start YAAC with the DISPLAY environment variable pointing to another computer that is running a graphical desktop. For example:
on the graphical system:
xhost +headlesssystem
on the headless system:
DISPLAY=linuxwithscreen:0 java -jar YAAC.jar
This way, you can use the screen on the graphical system (named "linuxwithscreen" in the above example) to access the configuration windows on the headless system (named "headlesssystem" in the example). You would have to install the graphical part of the Java runtime as well as the X client libraries for Java to be able to bring up the graphical screens.
The xhost command is used to tell the local X server that specific other computers are allowed to connect to the screen, keyboard, and mouse. By default, this is disabled to prevent random attackers from taking over your screen and capturing your keystrokes.
Thanks Andrew for this clear explanation...very useful!