Subj : .service files, and .sh @ reboot To : All From : paulie420 Date : Sat Apr 01 2023 16:28:08 On my Linux system I host .service files in /etc/systemd/system or /usr/lib/systemd/system. I am able to make sure they load after the network is up with an After= line in the [Unit]. I use crontab to run a start.sh script @reboot and it loads my Mystic bbs in daemon mode. All good. I don't use any GUI or Window Manager. ----- I'm helping a friend who has different needs than my setup. They, also, need mrc.service and doorparty-connect.service to load at boot - but putting them in [my] standard locations they fail to load - they don't see the actual locations of the files - dpc2/mrc_client.py... I'm deducing that the mount point isn't there when they're trying to load??? I tried to place those .service files in ~/.config/systemd/user - but that didn't seem to work and I changed the After= line to After=networking.service, but I believe I'm doing this wrong. Where/how is the proper place to put ..services that should load after the Window Manager is fully up, network is up and mountpoints are done? (I want them to load after the system is up, but before the user logs in.) Putting the start.sh in a @reboot in crontab doesn't work for this user, because what they WANT is ./mis to run in server mode w/ that output in a terminal window... like on-screen when they login. I thought of putting that ..sh in a .desktop file in ~/autostart, but that would only load after the user enters their password... again, I want this start.sh to load after the Window Manager is up, but before the user enters creds - and they want it output to a terminal window thats open and waiting on their desktop... I know I'm just used to systems w/o Desktop Environments - anyone have tips to do these two things? |07p|15AULIE|1142|07o |08......... --- Mystic BBS v1.12 A48 (Linux/64) * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129) .