[mk01]

(25th Feb, 2014 04:06 AM)Freddie299 Wrote:  I'd be so happy If you could provide a a little more detailed howto change from inetd to upstart with this ssh-nid because googeling this brings me straight to this thread.]

first of all important info: ssh-nih is name I put there to show it's not the original script (as by default again we use inetd to manage ssh), but for your googling the script 1:1 ssh upstart standard job script and should be by you (and google ) referred to as SSH. nothing else.

yes, the script is part of standard package now.

only difference to DEFAULT is ssh.override file which is slightly changing time (conditions) when the ssh is starting with this overridden second time by "manual" at /etc/init/ssh-nih.conf.

when you remove "manual" ssh-nih (SSH) will start automatically (as always before with all the information and knowledge you have - standard use of config files /etc/ssh/ and others).

but as I told at the beginning, if you do that it will run in conflict because of tcp/22 - ssh should use it according to /etc/ssh/sshd.conf and xbian's default inetd should use it to spawn sshd in case of seeing remote connection to this port.

so you have with removing "manual" also disable ssh (running through inetd) what you can do manually by editing /etc/inetd.conf and commenting line with ssh or through XBIAN-CONFIG where is it shown as SSH standard service. upstart scripts can be started stopped manually by referring to its file name without ".conf" like this:

Code:

sudo start ssh-nih
sudo status ssh-nih
sudo stop ssh-nih

(again "SSH-NIH" only in our particular case)

is it more clear now ?
you have not specified whether you have this "basic" issue or the problem you still have is with the chroot, privilege separation and sftp even with this standard configuration. but I don't see a reason it shouldn't work. even if you was used to startup script in /etc/init.d/ssh with upstart and it's type of configuration (like /etc/init/ssh-nid.conf) the end effect is exactly the same. sshd is started as system process/daemon waiting for own connections (only with sysv (/etc/init.d) scripts you had to write three pages of text to get it started "properly", with upstart 15 lines. but again, "sshd" should appear in "ps ax" and from this moment, all is as you configured, tested, deployed before.