Tag Info

New answers tagged

0

Most importantly you should have permissions to do so. Most of the problem like cannot start process or cannot find some file are due to permissions. Use sudo before any command. Now for ssh you can simply do sudo stop ssh sudo start ssh This leverages upstart


0

I just ran into this problem. By default install on my raspian wheezy, hostapd is started as S01 in services. This makes it start before ifplugd which configures eth0 and wlan0. The reason for this is that S01h[ostapd] < S01i[fplugd] since scripts are sorted in alphabetical order for execution. I think that the bridge gets a hard time getting configured ...


0

Depending on how early in the boot you want this to run, you may want to use cron @reboot. (You may need to play with environmental variables.) Then wrap it in a detached terminal. tmux new -d '/path/to/python /full/path/program/proxy.py' # or # screen -d -m '/path/to/python /full/path/program/proxy.py' Effectively these are backgrounded to synthetic ...


0

I don't think it has to do with graceful or fast shutdown, since I've been using graceful stop and I'm also having this problem. In my case, I've noticed the possibly related/additional problem that nginx continues to try to connect to a long-since-defunct socket, even after the socket and all the calls to it have been deleted (at least so far as files that ...


1

A secure way is to do this through ssh. Create a service-specific user ("dhcpkiller") and a private/public key pair so that the client can run this command: ssh dhcpkiller@dhcpserver pkill dnsmasq This one-line script gets triggered by your dhcp environment, which can happen in various ways, depending on the DHCP suite on the client. Quoting from dhclient ...


0

On my Deepin Linux (a variant of Ubuntu), I know two ways to start the Virtualbox services. In the terminal type service --status-all -- It will list the services registered in system with the status mentioned in output. You can see VirtualBox related services with the name vbox*. This step is now trivial. To start a service type service service_name start ...


0

They are not risky(except for finger) but it depend if can reach from outside(internet) or from local net,in the first case they are risky,but depend if you must use service associated or not. My rule are A service is necessary / used? Y=OK N=Simply shutdown it and turn off on boot Is possible to upgrade to secure service(imaps instead of imap)? Y=do it ...


2

Run netstat -pan --tcp --udp (Linux-specific syntax) on each server to find out which programs are listening to which ports, and disable those you don't need. Don't leave them running just is case, any open port is a potential risk.


1

Yes there is, quoting the relevant section of the man page for system.unit: WantedBy=, RequiredBy= This option may be used more than once, or a space-separated list of unit names may be given. A symbolic link is created in the .wants/ or .requires/ directory of each of the listed units when this unit is installed by systemctl enable. This has the ...


0

Is there any way to tell systemd to 'rescan' for another executable when the original executable died? Executables do not die. Processes die. Get the question right, and the answer appears. Is there a way to tell systemd about a new main service process and hand over to it so that the old main service process can quietly exit? Yes, there is. It's ...


0

No, there is not. This is a hard limitation imposed by systemd, and a substantial breaking change to the expectation of how processes work. I really hope that I'm wrong here, and I just haven't found it yet. FWIW, you're not alone. The best suggestions so far are to use at, cron, or systemd timer units. I understand if that's small consolation to you.



Top 50 recent answers are included