![]() ![]() If you can get the executable running that way, you can work from there to getting a script working. ![]() That's even more simple than running it from a bash script. ![]() Frequently there is a way to make it run from a command line (usually for testing, or special applications). The other option is to find the executable for the service/daemon's executable. Right now, invoking it with the service command, before services are supported, it's hard to say where the problem is. If you run the script and then it reports an error, you can be sure it is an error in that script or in the way your service runs. Your mileage may vary, and there may not be a bash script in /etc/init.d you can run. Note that the script is not called sshd, as you might expect. I've been doing that with sshd, sudo /etc/init.d/ssh start rather than sudo service ssh start. Then it won't matter if upstart or service isn't implemented fully. In other words, remove the word "service" from the command and call the script by its full path. Run it like any other bash script, with start as a parameter. ![]() If you get the initctl error message about not being able to talk to upstart, and the service doesn't start, you might want to look for the script in /etc/init.d, which is (usually) a standard bash script. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |