Arch Linux

inkdinky

Member

Registered: 2011-12-08

Posts: 66

[closed]SSH Server starting non-daemonized: where to prevent -D

I've run into this problem in the past where sshd starts up with the "-D" option which prevents daemonizing.
I solved this problem in the past by editing /etc/init/ssh.conf. However, that file doesn't exist on this system.
I'm assuming that has to do with the move to systemd.

So how can I tell:

sudo systemctl start sshd

to not include the -D option?

Thanks!

Last edited by inkdinky (2013-06-24 20:20:03)

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: [closed]SSH Server starting non-daemonized: where to prevent -D

Why do you want to do this?

(hint: you don't)

---

blog | ±github

inkdinky

Member

Registered: 2011-12-08

Posts: 66

Re: [closed]SSH Server starting non-daemonized: where to prevent -D

Ok. I'll take your word for it. I had just run into problems in the past on Ubuntu where I solved this problem by preventing the -D switch from being included. I thought this was the same case.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [closed]SSH Server starting non-daemonized: where to prevent -D

Please don't use [Closed]: it denotes a thread being locked.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [closed]SSH Server starting non-daemonized: where to prevent -D

Don't assume that problems in ubuntu will be problems here.  Besides being a totally different init system (ubuntu's upstart vs systemd), but also you never really know what you are getting with ubuntu packages because they are typically patched to hell.  With Arch Linux you get vanilla packages... or as vanilla as they can be and still build against the super up-to-date toolchain.  So the software is just like the developer intended it to be, and unless you are having issues with the service (daemon), there should be no need to change anything.

For future reference, the scripts of init.d are replaced by unit files in systemd. Most of the things you will use are service files, since they run... services.  You can find the ones shipped with packages in /usr/lib/systemd/system.  But see our wiki's systemd page to get a basic rundown of how to cofigure things.

Also, as jasonwryan noted above, you shouldn't use [Closed].  To give an indication that you have found a solution to your liking, you would edit the title with [Solved]