Permissions (maybe the program can not be run as root. If it doesn't start on initialization, but starting manually without problems, you should check: # ln -s /opt/TeamCity/bin/teamcity-server.sh /etc/init.d/teamcity-server If the teamcity start script is a LSB-compliant init script (that is, if it providesĪnd other arguments), you can just copy the script toĪ symbolic link for the file should be OK too. I am doing some reading on systemd but any help will be really appreciated. Can I have any pointers on this? It happens to be a machine with few other things, so I am a little vary of experimenting and if anyone with experience on this could give me some pointers, it will be great. Debian / Ubuntu has update-rc.d, and I guess i need to use chkconfig for this. So do I need to make any changes to the script?Ģ) How do I make this run as a service, for all users? I would want this to start at System Startup. I have couple of questionsġ) The above script is perhaps for Ubuntu or another Linux Distro. So I created the script, substituted the correct values as per my enviroment, and added a Symbolic link to my script. Haha hope esac is not specific to other distro :? Stopcmd='/bin/listener_mm.sh stop > /dev/null &'Įcho "Re-starting the Listener Server. Restartcmd='/bin/listener_mm.sh restart > /dev/null &' Startcmd='/bin/listener_mm.sh start > /dev/null &' I have just set up an application on Centos 7 and I saw on their product website that to run the application as a Linux Service (Start at System Startup), this is the script that one needs to use.Įxport JAVA_HOME="/usr/lib/jvm/jdk1.7.0_07"
Startx on boot manual#
Refer to the Lubuntu manual for more details.Pretty new to Centos 7 and most of my earlier experiences were with Ubuntu. Select "Turn On" to turn NumLock on at startup.Įnter Preferences -> LXQt Settings -> Keyboard and Mouse, and selecting the "Keyboard" tab will let you see a "Turn on NumLock after login" checkbox that you need to click. You can see in the middle section the options for "NumLock on KDE Startup", where you can choose to Turn On, Turn Off, or Leave Unchanged. usr/bin/setleds -D +num System Settings -> Keyboard and Mouse -> Keyboard). To do so add something similar to the following in the file /etc/rc.local: # Turn Numlock on for the TTYs: One way to guarantee that numlock will be turned on after bootup for the TTYs is to run setleds via rc.local (a script run after every runlevel change which in particular runs after booting up).
The status of numlock/scroll-lock/capslock can be manipulated with the setleds command. If you use the virtual consoles regularly, then you will quite likely want to have numlock on for the TTYs after boot up. (See more info in /usr/share/doc/lightdm/).Įnabling NumLock for Virtual Consoles (TTYs) This defines running numlockx command when starting the Unity Greeter. Edit /usr/share/lightdm//nf file and add the following line at the end: greeter-setup-script=/usr/bin/numlockx on It can be run by changing configuration of LightDM display manager. In Ubuntu 14.04 the above methods of running numlockx don't work. If you are not using a graphical display manager then add the following line to /etc/X11/xinit/xinitrc /usr/bin/numlockx onĮnabling NumLock from lightdm configuration Sudo sed -i 's|^exit 0.*$|# Numlock enable\n \&\& numlockx on\n\nexit 0|' /etc/rc.local This setting takes effect after Login and has no effect at the Login screen or consoles.Įnabling Numlock on startup can be done of several different ways. System Settings > Keyboard Layout > Options > Miscellaneous compatibility options