Hi all,
why "vi" acts differently is single user mode?
Does anyone help ?
I am using "x" to delete and it keeps messing up.
Please help
Thanks (2 Replies)
Hi all,
Well back at work and back to crashing systems again :-)
Does anyone know where I can find some decent information on single user mode? I need to be able to fix a few things. Don't know if it's possible in single user mode but I need to fix the "etc/vfstab" mainly I re-wrote it to... (2 Replies)
Just got a solaris 8 blade 150 box with no users, only a root account. no one seems to know the password. I'd like to add one user. So I booted into single user mode via cdrom and added one. Can't seem to login using the new account, though. Here's what I'm using:
# useradd -d /tmp/"user" -m... (1 Reply)
hello ppl, someone must be able to help with this --> I have an old NCR tower 32 with an ADDS terminal running a unix version 020102 (Im not sure if thats correct but its unix for sure). I have no user names and no passwords and need to login to read a tape. Is there any way to do that? I hear... (3 Replies)
Hi as per the article given.
Boot Linux Grub Into Single User Mode
I m modifying the boot entry
grub edit> kernel /vmlinuz-2.6.18-92.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet Singleand then booting from it by pressing b.
However the machine is getting booted into runlevel 5.
if the... (2 Replies)
Hi all
I am new on sun OS. I have have little experience on linux.
The Story start from this point:
I want to put some script on start-up the terminal, but I cant do that. my shell was sh and I tried so much to find way to do that. at last someone said to me change your shell to bash. I ask how... (4 Replies)
Dear All
I am trying to install my os as :
ok>boot cdrom - install
but receiving the following :
"IDprom checksum error
getexecname() failed
/sbin/rcS /etc/vfstab cannot create
INIT:failed write utmpx enrty
INIT:single user mode
INIT:execle of /etc/sulogin failed
Enter run level"
Can you... (6 Replies)
Discussion started by: hadimotamedi
6 Replies
LEARN ABOUT OPENDARWIN
kill
KILL(1) BSD General Commands Manual KILL(1)NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the processes specified by the pid operand(s).
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following pids have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
Some shells may provide a builtin kill command which is similar or identical to this utility. Consult the builtin(1) manual page.
SEE ALSO builtin(1), csh(1), killall(1), ps(1), kill(2), sigaction(2)STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 6 AT&T UNIX.
BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided.
BSD April 28, 1995 BSD