[MacPorts] #72345: openssh: Daemon does not produce logs when running

[MacPorts]

#72345: openssh: Daemon does not produce logs when running
----------------------+----------------------
  Reporter:  joshqou  |      Owner:  artkiver
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.10.5
Resolution:           |   Keywords:  monterey
      Port:  openssh  |
----------------------+----------------------

Comment (by artkiver):

 Thanks for the observation.

 Personally, I basically only have Apple laptops these days and so I don't
 really make much use of sshd, so I don't have meaningful perspective to
 share.

 Anecdotally, I haven't worked anywhere that had Apple XServe systems in an
 very long time and Apple also discontinued their OS X/Server software line
 last updated that in their App Store in 2002.

 Which is to say: my experience is that without assiduous use of
 /usr/bin/caffeinate to keep macOS from sleeping with abandon, it is
 remarkably ill suited to anything daemon/server related and I treat it
 with such constraints in mind. (I tend to prefer BSDs for 24x7
 server/daemon suited systems) I get the impression Apple treats macOS that
 way too based on the writing on they have left on the wall as it were.

 "Enabling the builtin sshd in Sharing seems to result in the same
 behaviour so this may be an upstream issue?"

 Without having looked into it further, that seems as if it is probably
 indicative that this isn't specific to MacPorts' OpenSSH?

 Not to suggest that MacPorts can't have macOS specific patches to change
 functionality from upstream behavior, but a much more pressing set of
 patches that need review and improvement and help from others to me right
 now are documented in this Trac issue which I opened recently:
 https://trac.macports.org/ticket/72317

 Since in that instance, those two patches breaking with 10.0p1/2 impacts
 existing MacPorts' functionality. I've contemplated just submitting a Pull
 Request for 10.0p1/2 as it stands without those patches, but was kind of
 hoping that other MacPorts' contributors might be able to assist where I
 have come up blank?

 TL;DR this issue can probably be addressed, somehow, but it's not going to
 be a very high priority for me at the moment. Patches welcome!

-- 
Ticket URL: <https://trac.macports.org/ticket/72345#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS