Sponsored Content
Operating Systems Linux Debian Cannot reboot Debian Etch - 1 Core at 100% Post 302360135 by jelloir on Thursday 8th of October 2009 07:31:45 AM
Old 10-08-2009
the non-tree view looked identical but rearranged the list.

Here is ps aux instead

Code:
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   6124   680 ?        Ss   Oct07   0:00 init [2]
root         2  0.0  0.0      0     0 ?        S    Oct07   0:00 [migration/0]
root         3  0.0  0.0      0     0 ?        SN   Oct07   0:00 [ksoftirqd/0]
root         4  0.0  0.0      0     0 ?        S    Oct07   0:00 [watchdog/0]
root         5  0.0  0.0      0     0 ?        S    Oct07   0:00 [migration/1]
root         6  0.0  0.0      0     0 ?        SN   Oct07   0:00 [ksoftirqd/1]
root         7  0.0  0.0      0     0 ?        S    Oct07   0:00 [watchdog/1]
root         8  0.0  0.0      0     0 ?        S<   Oct07   0:00 [events/0]
root         9  0.0  0.0      0     0 ?        S<   Oct07   0:00 [events/1]
root        10  0.0  0.0      0     0 ?        S<   Oct07   0:00 [khelper]
root        11  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kthread]
root        16  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kblockd/0]
root        17  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kblockd/1]
root        18  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kacpid]
root       116  0.0  0.0      0     0 ?        S<   Oct07   0:00 [khubd]
root       118  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kseriod]
root       169  0.0  0.0      0     0 ?        S<   Oct07   0:17 [kswapd0]
root       170  0.0  0.0      0     0 ?        S<   Oct07   0:00 [aio/0]
root       171  0.0  0.0      0     0 ?        S<   Oct07   0:00 [aio/1]
root       689  0.0  0.0      0     0 ?        S<   Oct07   0:00 [ata/0]
root       690  0.0  0.0      0     0 ?        S<   Oct07   0:00 [ata/1]
root       691  0.0  0.0      0     0 ?        S<   Oct07   0:00 [ata_aux]
root       744  0.0  0.0      0     0 ?        S<   Oct07   0:00 [scsi_eh_0]
root       745  0.0  0.0      0     0 ?        S<   Oct07   0:00 [scsi_eh_1]
root       970  0.0  0.0      0     0 ?        D<   Oct07   0:21 [kjournald]
root      1491  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kedac]
root      1735  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kmirrord]
root      2025  0.0  0.0   3728   592 ?        Ss   Oct07   0:00 /sbin/syslogd
root      2031  0.0  0.0   2656   412 ?        Ss   Oct07   0:00 /sbin/klogd -x
root      2127  0.0  0.0  25840  1236 ?        Ss   Oct07   0:00 /usr/sbin/sshd
ntp       2154  0.0  0.0  14080  1472 ?        Ss   Oct07   0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -u 101:103 -g
root      2164  0.0  0.0  11496   804 ?        Ss   Oct07   0:00 /usr/sbin/cron
root      2239  0.0  0.0   2652   536 tty1     Ss+  Oct07   0:00 /sbin/getty 38400 tty1
root      2240  0.0  0.0   2656   540 tty2     Ss+  Oct07   0:00 /sbin/getty 38400 tty2
root      2241  0.0  0.0   2656   540 tty3     Ss+  Oct07   0:00 /sbin/getty 38400 tty3
root      2242  0.0  0.0   2656   540 tty4     Ss+  Oct07   0:00 /sbin/getty 38400 tty4
root      2243  0.0  0.0   2656   540 tty5     Ss+  Oct07   0:00 /sbin/getty 38400 tty5
root      2244  0.0  0.0   2656   540 tty6     Ss+  Oct07   0:00 /sbin/getty 38400 tty6
root      3104  0.0  0.0      0     0 ?        S    11:54   0:01 [pdflush]
root      3202  0.0  0.0      0     0 ?        S    13:56   0:00 [pdflush]
root      3549  0.0  0.0  11664   908 ?        DN   21:20   0:00 mount /dev/nb0 /mnt/
root      3580  0.0  0.0  11664   908 ?        D    21:25   0:00 mount /dev/nb0 /mnt/
root      3591  0.0  0.0   6960   724 ?        D    21:28   0:00 shutdown -r 0 w
root      3700  0.0  0.0   2508   356 ?        D    21:48   0:00 reboot -f
root      3722  0.0  0.0   2508   320 ?        D    21:54   0:00 rmmod -f nbd
root      3737  0.0  0.0   6956   716 ?        D    22:02   0:00 shutdown -r 0 w
root      3739  0.0  0.0  36792  2724 ?        Ss   22:03   0:00 sshd: root@pts/5
root      3741  0.0  0.0  11548  1992 pts/5    Ss   22:03   0:00 -bash
root      3750  0.0  0.0   9656  1056 pts/5    R+   22:30   0:00 ps aux

 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Install App in Debian Etch 4.0

I am trying to install a couple applications that I downloaded on my Debian Etch 4.0 OS but I don't know how. 1) I tried using sudo apt-get install...but it always tells me I'm not in the sudoers file 2) I tried using root terminal, but I cant seem to navigate anywhere and I don't know where... (3 Replies)
Discussion started by: icecom10
3 Replies

2. Solaris

server reboot itself but no core dump

I wonder if anyone here came accross the same situation like me. One of server in my company reboot itself serveral days ago. I have checked /var/adm/messages... there is nothing there but a few messages mention explorer file has been generated by sysadmin. There is no core dump file either.... (4 Replies)
Discussion started by: uuontario
4 Replies

3. Debian

Debian Etch - install us-keyboard driver

Hi, i'm using a debian-4.0r1 on an old subnet machine. I have to extend it with an other keyboard . What i have is a DVD of etch 4.0r7. How can i install and load the keyboard-driver for the us-keyboard? Can anybody please give me a hint how to do that? Thanks in advance (0 Replies)
Discussion started by: IMPe
0 Replies
chroot(8)						      System Manager's Manual							 chroot(8)

NAME
chroot - Changes the root directory of a command SYNOPSIS
/usr/sbin/chroot directory command DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in effect, directory is relative to the current root of the running process. Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file system and the relevant pathnames for the files map correctly in the new root file system. For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and /etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on description files produced by the ctab command may also fail if the required description files are not present in the new root file system. The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe- cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new root file system in the appropriate locations. EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec- ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among others) on the new root file system. Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial root file system. To create a file relative to the original root rather than the new one, use this syntax and enter: chroot directory command > file CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite the file system. FILES
Specifies the command path. RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1) Functions: chdir(2), chroot(2) exec(2) delim off chroot(8)
All times are GMT -4. The time now is 05:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy