Hot answers tagged rc.d
Unless something is very, very wrong with your system, that should have been a harmless copy command. Are you certain /etc/rc.d is the actual location of your startup scripts? Doing some quick googling seems to return a lot of results for potential rc.d locations such as /usr/local/etc/rc.d The only possible way I can imagine that command could have ...
Messages from init scripts are generally not captured anywhere. Thus, you need to implement a way to do it yourself. A good idea is to use logger to send all output to syslog. This example will send stdout and stderr to syslog: exec 1> >(logger -s -t $(basename $0)) 2>&1 I found it in this great article: http://urbanautomaton.com/blog/2014/09/...
I think this would do the job: insserv -r foo
Only top voted, non community-wiki answers of a minimum length are eligible