2012/11/12 Yedidyah Bar-David linux...@didi.bardavid.org:
On Mon, Nov 12, 2012 at 06:32:25PM +0200, E.S. Rosenberg wrote:
+1 for tmux, this does however imply that all the admins are using the
same account to login (bad scenario) with or instead the tmux/screen
line should be added at the end
2012/11/12 Yedidyah Bar-David linux...@didi.bardavid.org:
On Mon, Nov 12, 2012 at 12:51:46PM +0200, Nadav Har'El wrote:
On Mon, Nov 12, 2012, Elazar Leibovich wrote about Re: Is forbidding
concurrent ssh sessions a good idea?:
While I can certainly see what's broken with it for using
I'm considering to disallow concurrent ssh sessions on a single-purpose
production machine (say, DB server).
I thought of replacing the default shell with a shell that keeps its pid
file in a central place. If such a file already exist, it'll kill the other
running shell before logging in.
On Mon, Nov 12, 2012 at 10:05 AM, Elazar Leibovich elaz...@gmail.com wrote:
I'm considering to disallow concurrent ssh sessions on a single-purpose
production machine (say, DB server).
I thought of replacing the default shell with a shell that keeps its pid
file in a central place. If such a
On Mon, Nov 12, 2012 at 10:27 AM, Oleg Goldshmidt p...@goldshmidt.orgwrote:
On Mon, Nov 12, 2012 at 10:05 AM, Elazar Leibovich elaz...@gmail.com
wrote:
I'm considering to disallow concurrent ssh sessions on a single-purpose
production machine (say, DB server).
I thought of replacing
On Mon, Nov 12, 2012 at 10:40 AM, Elazar Leibovich elaz...@gmail.com wrote:
No problem with my scheme, if sshd won't kill old sessions, new sessions
will... (or maybe I misunderstand you).
No, I misunderstood you... Sorry.
Killing existing active sessions in mid-flight seems hairy. You want
On Mon, Nov 12, 2012 at 10:54 AM, Oleg Goldshmidt p...@goldshmidt.orgwrote:
On Mon, Nov 12, 2012 at 10:40 AM, Elazar Leibovich elaz...@gmail.com
wrote:
No problem with my scheme, if sshd won't kill old sessions, new sessions
will... (or maybe I misunderstand you).
No, I misunderstood
On Mon, Nov 12, 2012 at 10:05:02AM +0200, Elazar Leibovich wrote:
I'm considering to disallow concurrent ssh sessions on a single-purpose
production machine (say, DB server).
Sessions != shells.
SSH can be used for various things (ssh, scp, whatever).
I normally keep at least one active shell
On Mon, Nov 12, 2012 at 12:30 PM, Tzafrir Cohen tzaf...@cohens.org.ilwrote:
On Mon, Nov 12, 2012 at 10:05:02AM +0200, Elazar Leibovich wrote:
I'm considering to disallow concurrent ssh sessions on a single-purpose
production machine (say, DB server).
Sessions != shells.
Of course, what I
On Mon, Nov 12, 2012, Elazar Leibovich wrote about Re: Is forbidding
concurrent ssh sessions a good idea?:
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
On Mon, Nov 12, 2012 at 12:51:46PM +0200, Nadav Har'El wrote:
On Mon, Nov 12, 2012, Elazar Leibovich wrote about Re: Is forbidding
concurrent ssh sessions a good idea?:
While I can certainly see what's broken with it for using a regular
computer, whose stability I do not value much
On Mon, 12 Nov 2012 12:51:46 +0200
Nadav Har'El n...@math.technion.ac.il wrote:
On Mon, Nov 12, 2012, Elazar Leibovich wrote about Re: Is forbidding
concurrent ssh sessions a good idea?:
While I can certainly see what's broken with it for using a regular
computer, whose stability I do
On 11/12/2012 12:51 PM, Nadav Har'El
wrote:
On Mon, Nov 12, 2012, Elazar Leibovich wrote about "Re: Is forbidding concurrent ssh sessions a good idea?":
While I can certainly see what's broken with it for using a regular
compu
On Mon, Nov 12, 2012 at 12:51:46PM +0200, Nadav Har'El wrote:
Let me offer another completely different idea, without any kills and
similar tricks: End your ~/.profile with screen -R -D
What will this do?
The login shell will start screen(1), and let the admin work in it.
If another
2012/11/12 Yedidyah Bar-David linux...@didi.bardavid.org:
On Mon, Nov 12, 2012 at 12:51:46PM +0200, Nadav Har'El wrote:
On Mon, Nov 12, 2012, Elazar Leibovich wrote about Re: Is forbidding
concurrent ssh sessions a good idea?:
While I can certainly see what's broken with it for using
On 11/12/2012 10:05 AM, Elazar
Leibovich wrote:
I'm considering to disallow concurrent ssh sessions
on a single-purpose production machine (say, DB server).
You shouldn't...
I'd just add 'who' to the end of the .profile / .bashrc /
On Mon, Nov 12, 2012 at 8:33 PM, Dotan Shavit do...@shavitos.com wrote:
On 11/12/2012 10:05 AM, Elazar Leibovich wrote:
I'm considering to disallow concurrent ssh sessions on a single-purpose
production machine (say, DB server).
You shouldn't...
I'd just add 'who' to the end of the
On Mon, Nov 12, 2012 at 06:32:25PM +0200, E.S. Rosenberg wrote:
+1 for tmux, this does however imply that all the admins are using the
same account to login (bad scenario) with or instead the tmux/screen
line should be added at the end of /root/.profile and not ~/.profile
IIRC screen, perhaps
2012/11/12 Yedidyah Bar-David linux...@didi.bardavid.org:
On Mon, Nov 12, 2012 at 06:32:25PM +0200, E.S. Rosenberg wrote:
+1 for tmux, this does however imply that all the admins are using the
same account to login (bad scenario) with or instead the tmux/screen
line should be added at the end
On 11/12/2012 09:05 PM, Elazar
Leibovich wrote:
On Mon, Nov 12, 2012 at 8:33 PM, Dotan Shavit do...@shavitos.com
wrote:
On 11/12/2012 10:05 AM, Elazar Leibovich wrote:
20 matches
Mail list logo
