<div dir="ltr">On Mon, Nov 12, 2012 at 12:30 PM, Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir@cohens.org.il" target="_blank">tzafrir@cohens.org.il</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, Nov 12, <a href="tel:2012" value="+9722012">2012</a> at 10:05:02AM +0200, Elazar Leibovich wrote:<br>
> I'm considering to disallow concurrent ssh sessions on a single-purpose<br>
> production machine (say, DB server).<br>
<br>
</div>Sessions != shells.<br></blockquote><div><br></div><div>Of course, what I care about is the shell, not the transport.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This would have badly broken my personal use case.<br></blockquote><div><br></div><div>While I can certainly see what's broken with it for using a regular computer, whose stability I do not value much, and while there are difficulties this may cause, do you see anything specific that will break in the use case of a production server?</div>
</div></div></div>