Skip to main content
Unix & Linux

Return to Question

added 143 characters in body
Source Link
gasko peter
gasko peter
  • 5.6k
  • 25
  • 92
  • 149

It's okay that there are history files logging the commands that has been used. That't not the problem. The problem is that when 2 admins are logged in to an AIX server then it could be bad:

If admin #A uses

rm FILENAME

then if admin #B hits the up arrow he gets the

rm FILENAME

command which is not a very good thing. So how can the termial be forced to only write the command history if the ssh session ended? (UPDATE#2: or solution could be that that each session has it's uniq command history, and thus we can't see each others command, only when they sign out for ex.)

UPDATE#1

4:root@SERVER:/root # echo $SHELL /usr/bin/ksh 4:root@SERVER:/root # oslevel -s 6100-05-01-1016 4:root@SERVER:/root #

It's okay that there are history files logging the commands that has been used. That't not the problem. The problem is that when 2 admins are logged in to an AIX server then it could be bad:

If admin #A uses

rm FILENAME

then if admin #B hits the up arrow he gets the

rm FILENAME

command which is not a very good thing. So how can the termial be forced to only write the command history if the ssh session ended?

It's okay that there are history files logging the commands that has been used. That't not the problem. The problem is that when 2 admins are logged in to an AIX server then it could be bad:

If admin #A uses

rm FILENAME

then if admin #B hits the up arrow he gets the

rm FILENAME

command which is not a very good thing. So how can the termial be forced to only write the command history if the ssh session ended? (UPDATE#2: or solution could be that that each session has it's uniq command history, and thus we can't see each others command, only when they sign out for ex.)

UPDATE#1

4:root@SERVER:/root # echo $SHELL /usr/bin/ksh 4:root@SERVER:/root # oslevel -s 6100-05-01-1016 4:root@SERVER:/root #
deleted 13 characters in body
Source Link
gasko peter
gasko peter
  • 5.6k
  • 25
  • 92
  • 149

It's okay that there are history files logging the commands that has been used. That't not the problem. The problem is that when 2 admins are logged in to an AIX server then it could be bad:

If admin #A uses

rm FILENAME

then if admin #B hits the up arrow he gets the

rm FILENAME

command which is not a very good thing. So how can the termial be forced to only write the command history if the ssh session ended? (Linux like)

It's okay that there are history files logging the commands that has been used. That't not the problem. The problem is that when 2 admins are logged in to an AIX server then it could be bad:

If admin #A uses

rm FILENAME

then if admin #B hits the up arrow he gets the

rm FILENAME

command which is not a very good thing. So how can the termial be forced to only write the command history if the ssh session ended? (Linux like)

It's okay that there are history files logging the commands that has been used. That't not the problem. The problem is that when 2 admins are logged in to an AIX server then it could be bad:

If admin #A uses

rm FILENAME

then if admin #B hits the up arrow he gets the

rm FILENAME

command which is not a very good thing. So how can the termial be forced to only write the command history if the ssh session ended?

Tweeted twitter.com/#!/StackUnix/status/209422988947365889
Source Link
gasko peter
gasko peter
  • 5.6k
  • 25
  • 92
  • 149

How to disable live shell session command history under AIX 5-6?

It's okay that there are history files logging the commands that has been used. That't not the problem. The problem is that when 2 admins are logged in to an AIX server then it could be bad:

If admin #A uses

rm FILENAME

then if admin #B hits the up arrow he gets the

rm FILENAME

command which is not a very good thing. So how can the termial be forced to only write the command history if the ssh session ended? (Linux like)