584
edits
Changes
Jump to navigation
Jump to search
Line 133:
Line 133: + − One of the main things the shell script set up is the debugging level . .+ + + + + + + + + +
Contributing to Zynthian Development (view source)
Revision as of 05:09, 19 January 2024
, 19 January→Where are the zynthian source files located on a zynthian?
[[File:Zynthian-ui-folder.png|600px|thumb|right|Zynthian-ui directory]]
[[File:Zynthian-ui-folder.png|600px|thumb|right|Zynthian-ui directory]]
One of the main things the shell script set up is the debugging level which decides what level of message the zynthian generates when it encounters a logging command in the python script. . .
===== What happens if zynthian crashes and how do I stop it? =====
When a zynthian starts up, most of the early functions and what gets run gets handled by a linux tool called systemd. This organises what order things happen in and nursemaids programmes, setting up procedures for what to do when programmes crash or misbehave. For instance there is no point in starting up the network devices if there is no network, and this is the sort of thing systemd does on your behalf. In the zynthian case it starts up the zynthian programme using the scripts we discussed in /zynthian/zynthian-ui and handles a zynthian by restarting the GUI if the software crashes for some reason. This is what you want if you are performing but is decidedly irritating if you are trying to write and test code.
There are magic incantations to control zynthian via systemd
systemctl stop zynthian
systemctl start zynthian
systemtl status zynthian
So to stop a running zynthian you issue the first of these and this will tell systemd to ignore the restart so you can take over the running of it.