Hi,
a word of caution: the following terminology may be misleading; I learned it from different sources: Linux and macOS. By "terminal" I refer to Terminal.app, by "(text mode) console" to a shell not running inside Terminal.app, but independently from the GUI (and not Console.app).
After having had some minor exposure to Linux, I miss most on macOS (12.4) the ability to directly switch to a text mode console (that is, not inside the GUI in a terminal) to fix some errand process or to restart the GUI -- both of which is undoubtedly technically possible (remote login via ssh over wlan, e.g.). Most importantly for me it is then possible to run aria2 in a console and let bigger downloads be carried out in a safer environment than the more crash-prone gui. This is, again, obviously possible by connecting via ssh. But as soon as this connection is disrupted (by, say, a short breakdown in signal strength) I am logged out and aria2 (for example) terminates.
I have, therefore, three questions: 1. Is it somehow possible to switch to a different console locally? Alternatively, how may I invoke a process, probably via launchd (and launchctl), into a different console than the one one finally starting the GUI? According to the corresponding man-page "launchctl reboot logout" should be integratable into a users config. (Which would mean, as far I can tell, that a frozen GUI restarts by itself, without interruption of non-gui processes; please correct me, if I am wrong here.)
I hope anyone can help!
Kind Regards
Jochen Kaiserswerth
a word of caution: the following terminology may be misleading; I learned it from different sources: Linux and macOS. By "terminal" I refer to Terminal.app, by "(text mode) console" to a shell not running inside Terminal.app, but independently from the GUI (and not Console.app).
After having had some minor exposure to Linux, I miss most on macOS (12.4) the ability to directly switch to a text mode console (that is, not inside the GUI in a terminal) to fix some errand process or to restart the GUI -- both of which is undoubtedly technically possible (remote login via ssh over wlan, e.g.). Most importantly for me it is then possible to run aria2 in a console and let bigger downloads be carried out in a safer environment than the more crash-prone gui. This is, again, obviously possible by connecting via ssh. But as soon as this connection is disrupted (by, say, a short breakdown in signal strength) I am logged out and aria2 (for example) terminates.
I have, therefore, three questions: 1. Is it somehow possible to switch to a different console locally? Alternatively, how may I invoke a process, probably via launchd (and launchctl), into a different console than the one one finally starting the GUI? According to the corresponding man-page "launchctl reboot logout" should be integratable into a users config. (Which would mean, as far I can tell, that a frozen GUI restarts by itself, without interruption of non-gui processes; please correct me, if I am wrong here.)
I hope anyone can help!
Kind Regards
Jochen Kaiserswerth
