Yes, I was on the console when I run the command, and I did 3 times since we are also working on a mirrored disk problem that time. The last 2 init 0 command I did was when the mirrored disk problem already fixed.
Please see attachment to see the logs...
I have written a daemon and want to make sure that it starts up again after the machine is re-started so I can quit manually doing it. Problem is I'm having difficulty understanding what to do with the init.d
Any help would be appreciated! (1 Reply)
Hi Expert,
I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0..
I can only reboot the system using reboot ... Was... (6 Replies)
Hi,
I am using RHEL4 and I am not booting my computer into graphics mode
i.e. It gets hangs after the step of Enabling swap space...
I.e system is not able to enter into runlevel 5.
However, when I boot it into 'runlevel3' and then I do "#startx",
It enetrs... (1 Reply)
I know if a parent process exits before its child, the last one becomes orphan for a while and then is added to the children of Init process.
I'd like to know deeper
1 how the orphan becomes init process,
2 how init knows that from a some point on it has another child.
Thank you in advance. (2 Replies)
Greetings,
I've visited this forums for a long time and normally got an right answer but this time my problem doesn't seem to go away. What I'm trying to do is the following:
VAR="\n\nline1\nline2\nline3\nline4\nline5\nline6\nline7\n\n"
(The count of newlines is varying!)
If I echo this i... (3 Replies)
Dear all,
I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel):
1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins
So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
What is the difference between 'init s' and 'init 1'.
I know that both will work to change the current run level to single user mode.
Is there any difference in those two commands? (5 Replies)
I encountered a problem on one of our database servers.
OS: CentOS 5.5 final
Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel)
We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies
LEARN ABOUT OSX
iotop
iotop(1m) USER COMMANDS iotop(1m)NAME
iotop - display top disk I/O events by process. Uses DTrace.
SYNOPSIS
iotop [-C] [-D|-o|-P] [-j|-Z] [-d device] [-f filename] [-m mount_point] [-t top] [interval [count]]
DESCRIPTION
iotop tracks disk I/O by process, and prints a summary report that is refreshed every interval.
This is measuring disk events that have made it past system caches.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS -C don't clear the screen
-D print delta times - elapsed, us
-j print project ID
-o print disk delta times, us
-P print %I/O (disk delta times)
-Z print zone ID
-d device
instance name to snoop (eg, dad0)
-f filename
full pathname of file to snoop
-m mount_point
mountpoint for filesystem to snoop
-t top print top number only
EXAMPLES
Default output, print summary every 5 seconds
# iotop
One second samples,
# iotop 1
print %I/O (time based),
# iotop -P
Snoop events on the root filesystem only,
# iotop -m /
Print top 20 lines only,
# iotop -t 20
Print 12 x 5 second samples, scrolling,
# iotop -C 5 12
FIELDS
UID user ID
PID process ID
PPID parent process ID
PROJ project ID
ZONE zone ID
CMD command name for the process
DEVICE device name
MAJ device major number
MIN device minor number
D direction, Read or Write
BYTES total size of operations, bytes
ELAPSED
total elapsed times from request to completion, us (this is the elapsed time from the disk request (strategy) to the disk completion
(iodone))
DISKTIME
total times for disk to complete request, us (this is the time for the disk to complete that event since it's last event (time
between iodones), or, the time to the strategy if the disk had been idle)
%I/O percent disk I/O, based on time (DISKTIME)
load 1 minute load average
disk_r total disk read Kb for sample
disk_w total disk write Kb for sample
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
iotop will run forever until Ctrl-C is hit, or the specified interval is reached.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO iosnoop(1M), dtrace(1M)version 0.75 Oct 25, 2005 iotop(1m)