03-28-2015
How to make each login shell history independent for same account?
Hello All,
Many developers in our company use same application account to log in Linux Box for code development, how can i redirect my log in shell history to a different file to avoid history being shown to others or accidentally execute the same command which i or others executed?
Thank you.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi,
i am the administrator of my sun solaris 8 server. i want to keep a log file for users who have login.
example: in the end of the day, i want to open file that tells me during these days, what user, from which IP address, and from what time to time has login.
please tell me how should... (4 Replies)
Discussion started by: champion
4 Replies
2. News, Links, Events and Announcements
DARPA contestants make robotic history
http://news.com.com/Driverless+robots+reach+milestone+in+DARPA++race/2100-11394_3-5891793.html?tag=nl (3 Replies)
Discussion started by: Neo
3 Replies
3. UNIX for Dummies Questions & Answers
Is there a way to easily change an account to be a non login account (NP in the shadow) file?
I know I can just edit the file but that is not what we want to do. We use access control software and want to provide a way to set an account to be non-login using simple commands that can be mapped... (0 Replies)
Discussion started by: LordJezo
0 Replies
4. AIX
Hi, yesterday, I changed root's shell in /etc/passwd, cause a mistake then I can not log in root account (can't find correct shell). I attempted to log in single-mode, however, it prompted for single-mode's password then I type root's password but still can not log in.
I'm using AIX 5L version 5.2... (2 Replies)
Discussion started by: neikel
2 Replies
5. Solaris
Hi All,
My application is connecting to a no of sites to get or put files.
one script is using sftp user1@host1
to log into the account to put some files over there.But some other scripts are connecting to some other sites using
ftp host2
user user2 passwd
inside the script.But I... (1 Reply)
Discussion started by: megh
1 Replies
6. Linux
Hi,
How to find remote Linux box login account without login in to that box?
I don't have login account at my remote Linux box. But I need who are all having login account. How do I findout?
Thanks,
--Muthu. (3 Replies)
Discussion started by: Muthuselvan
3 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I was reading a tutorial for Installing Tomcat on Linux machine.
(http://www.puschitz.com/InstallingTomcat.html)
Here the author had mentioned that: For security reasons I created a user account with no login shell for running the Tomcat server.
My question is:
1. What is a User... (6 Replies)
Discussion started by: jw_amp
6 Replies
8. AIX
I want to learn AIX. I would like to find someone who would be willing to give me a login to their AIX home lab server. My intent is to poke around and discover the similarities and differences of AIX compared to other *NIXs.
I am a UNIX admin so I can think of what some immediate concerns may... (1 Reply)
Discussion started by: perl_in_my_shel
1 Replies
9. IP Networking
I have this in /etc/network/interfaces:
auto ens3
iface ens3 inet static
address 46.xx.xxx.1x7
netmask 255.255.252.0
broadcast 46.38.xxx.255
gateway 46.xx.xxx.1
auto ens3:0
iface ens3:0 inet static
address 188.xx.xx.xx5
netmask... (0 Replies)
Discussion started by: Douro
0 Replies
10. IP Networking
Code:
auto ens3
iface ens3 inet static
address 46.xx.xxx.1x7
netmask 255.255.252.0
broadcast 46.38.xxx.255
gateway 46.xx.xxx.1
auto ens3:0
iface ens3:0 inet static
address 188.xx.xx.xx5
netmask 255.255.255.255
I want the... (1 Reply)
Discussion started by: oshihari
1 Replies
history(n) Tcl Built-In Commands history(n)
__________________________________________________________________________________________________________________________________________________
NAME
history - Manipulate the history list
SYNOPSIS
history ?option? ?arg arg ...?
_________________________________________________________________
DESCRIPTION
The history command performs one of several operations related to recently-executed commands recorded in a history list. Each of these
recorded commands is referred to as an "event". When specifying an event to the history command, the following forms may be used:
[1] A number: if positive, it refers to the event with that number (all events are numbered starting at 1). If the number is negative,
it selects an event relative to the current event (-1 refers to the previous event, -2 to the one before that, and so on). Event 0
refers to the current event.
[2] A string: selects the most recent event that matches the string. An event is considered to match the string either if the string
is the same as the first characters of the event, or if the string matches the event in the sense of the string match command.
The history command can take any of the following forms:
history
Same as history info, described below.
history add command ?exec?
Adds the command argument to the history list as a new event. If exec is specified (or abbreviated) then the command is also exe-
cuted and its result is returned. If exec is not specified then an empty string is returned as result.
history change newValue ?event?
Replaces the value recorded for an event with newValue. Event specifies the event to replace, and defaults to the current event
(not event -1). This command is intended for use in commands that implement new forms of history substitution and wish to replace
the current event (which invokes the substitution) with the command created through substitution. The return value is an empty
string.
history clear
Erase the history list. The current keep limit is retained. The history event numbers are reset.
history event ?event?
Returns the value of the event given by event. Event defaults to -1.
history info ?count?
Returns a formatted string (intended for humans to read) giving the event number and contents for each of the events in the history
list except the current event. If count is specified then only the most recent count events are returned.
history keep ?count?
This command may be used to change the size of the history list to count events. Initially, 20 events are retained in the history
list. If count is not specified, the current keep limit is returned.
history nextid
Returns the number of the next event to be recorded in the history list. It is useful for things like printing the event number in
command-line prompts.
history redo ?event?
Re-executes the command indicated by event and returns its result. Event defaults to -1. This command results in history revision:
see below for details.
HISTORY REVISION
Pre-8.0 Tcl had a complex history revision mechanism. The current mechanism is more limited, and the old history operations substitute and
words have been removed. (As a consolation, the clear operation was added.)
The history option redo results in much simpler "history revision". When this option is invoked then the most recent event is modified to
eliminate the history command and replace it with the result of the history command. If you want to redo an event without modifying his-
tory, then use the event operation to retrieve some event, and the add operation to add it to history and execute it.
KEYWORDS
event, history, record
Tcl history(n)