Skip to main content ↑ ↓
Topic: Can't run services any longer after the update (Read 830 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Can't run services any longer after the update

I run apache with
Quote
/usr/local/apache/bin/apachectl start
as I have for decades and now when I start it up and log out, the system is killing httpd after closing the terminal.  I had the same thing happen with mariadb and I fixed the start file under init and now it works, but only when started with /etc/init.d/mariadb start


what the heck was changed?

Re: Can't run services any longer after the update

Reply #1 –
Hello

I was hoping to get some feedback on this because it has to affect so many other systems and testing environment.  Classically, from a terminal, I can run and test a dameon from the shell and then run it with

Code: [Select]
nohup /usr/sbin/dameon &

and the process detatches from the shell.  I can log out without trouble.

Now it seems that kernel is killing these processes if you kill the getty process that the shell is attached to.

For example, I ssh to a server
I su-  to root

I start the dameon
I exit root - process is still running
I exit user and terminate the ssh session - now the dameon is killed by a "normal" signal automatically according to the logs.

When I start it with opernrc though it remains working.



 

Re: Can't run services any longer after the update

Reply #2 –
Check /etc/elogind/logind.conf for KillUserProcesses=yes, if there change it to "no".

If that wasn't the problem, use nohup(1) to make sure your backgrounded process stays alive after logout.