to kick off vi as the history editor if it is not in your .profile - and how would you edit .profile is another thread if you do not know vi and don't have another editor...
Hi All,
I would like to know how to get the command history from the prompt. For example in dos, if we hit the Up Arrow, we get the previous command. I am not getting this in my telnet session (AIX) at the prompt.
I know that if I type history command it will give a list of cammands I typed... (2 Replies)
Is it possible to use the keyboard UP ARROW in place of k to recall history? If so, how/what do I need to do change terminal emulation, etc.?
TIA,
George (7 Replies)
Can anyone tell this:
If two users are logged into the same server from different locations. Is there a way to see the history command of the other user? I tried the history command, but it is showing me only the commands I used.
Thanks in advance for your help.
Iamnew2solaris (1 Reply)
Hi All,
I have a NFS mount filesystem, however it is not supporting a creation of filesize greater than 2 GB in it, how can i enable the option (bf = true) in it.
The AIX version is 4.3.2
Thanks in Advance!! (1 Reply)
Hello,
The system has been rebooted and I need to see the commands executed in the system prior to restart by the oracle user.The history command is not showing me the commands executed prior to reboot.
Please advise.
Best regards,
Vishal (1 Reply)
I have SNMPv3 working on our server but when viewed from the security software, it shows no privacy enabled
AIX 7.1, TL1, snmp.crypto 6.1.2.0 installed, ran snmpv3_ssw -e
Unsure what I have configured wrong.
What is needed to show Privacy in AIX. I looked at a config on a Solaris box... (5 Replies)
Discussion started by: anrivera140
5 Replies
LEARN ABOUT OPENSOLARIS
profile
profile(7D) Devices profile(7D)NAME
profile - DTrace profile interrupt provider
DESCRIPTION
The profile driver is a DTrace dynamic tracing provider that adds time-based interrupt event sources that can be used as DTrace probes.
Each profile event source is a time-based interrupt firing every fixed, specified time interval. You can use these probes to sample some
aspect of system state every unit time and the samples can then be used to infer system behavior. If the sampling rate is high, or the sam-
pling time is long, an accurate inference is possible. By using the DTrace facility to bind arbitrary actions to probes, you can use the
profile provider to sample practically anything in the system. For example, you could sample the state of the current thread, the CPU
state, or the current machine instruction each time a probe fires.
The profile driver is not a public interface and you access the instrumentation offered by this provider through DTrace. Refer to the
Solaris Dynamic Tracing Guide for a description of the public documented interfaces available for the DTrace facility and the probes
offered by the profile provider.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWdtrp |
+-----------------------------+-----------------------------+
|Interface Stability |Private |
+-----------------------------+-----------------------------+
SEE ALSO dtrace(1M), attributes(5), dtrace(7D)
Solaris Dynamic Tracing Guide
SunOS 5.11 4 Sep 2003 profile(7D)