09-06-2001
I assume these programs start up on boot?
If so, depending on where your system
startup commands/scripts are, for instance
in "/etc/inittab" and/or in some "/etc/rc.d"
directory, you should be able to find the
command(s) used to start this.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused:
I have put together an old machine with a 386DX CPU (40MHz)
with 8Mb of RAM and a 160Mb hard disk. One guy told me that its still suitable for UNIX. Can enyone give me some hints on how to start? (1 Reply)
Discussion started by: msm
1 Replies
2. UNIX for Dummies Questions & Answers
I just installed FreeBSD 4.5 and I want to find out how I can start and run X? When I boot I get taken to the command line. Xconfigurator doesn't want to work. (2 Replies)
Discussion started by: AMDPwred
2 Replies
3. Shell Programming and Scripting
I am re-learning UNIX and want to download Unix to my lab for studying on the road. Any suggestions? Got several books, but need to run scripts :rolleyes: (2 Replies)
Discussion started by: DudeMan
2 Replies
4. UNIX for Dummies Questions & Answers
Does anyone know it it is possible to start a program with a timeout, so that it is automatically killed if the timeout expires? If yes, how? (6 Replies)
Discussion started by: soheil.samii
6 Replies
5. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
6. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
7. SCO
Hello - We have setup printers to startup in the /etc/rc.d/8 directory and when the SCO system is booted this script should kick them off or start them up but it doesn't. So I have to start it from root and leave the window open. I know this isn't right and trying to figure out what's missing. ... (13 Replies)
Discussion started by: dbm7230
13 Replies
8. AIX
Hello,
I'm having a problem starting the cron daemon automatically from inittab, let me provide the details below:
We are having five equally installed machines. One of them was upgraded in the past, one we upgraded recently, both from 5300-05-06 to 5300-07-01-0748. On the upgraded... (6 Replies)
Discussion started by: hybr1d
6 Replies
9. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
10. UNIX for Dummies Questions & Answers
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
LEARN ABOUT LINUX
sulogin
SULOGIN(8) Linux System Administrator's Manual SULOGIN(8)
NAME
sulogin - Single-user login
SYNOPSIS
sulogin [ -e ] [ -p ] [ -t SECONDS ] [ TTY ]
DESCRIPTION
sulogin is invoked by init(8) when the system goes into single user mode. (This is done through an entry in inittab(5).) Init also tries
to execute sulogin when the boot loader (e.g., grub(8)) passes it the -b option.
The user is prompted
Give root password for system maintenance
(or type Control-D for normal startup):
If the root account is locked, as is the default on Ubuntu, no password prompt is displayed and sulogin behaves as if the correct password
were entered.
sulogin will be connected to the current terminal, or to the optional device that can be specified on the command line (typically /dev/con-
sole).
If the -t option is used then the program only waits the given number of seconds for user input.
If the -p option is used then the single-user shell is invoked with a dash as the first character in argv[0]. This causes the shell
process to behave as a login shell. The default is not to do this, so that the shell will not read /etc/profile or $HOME/.profile at
startup.
After the user exits the single-user shell, or presses control-D at the prompt, the system will (continue to) boot to the default runlevel.
ENVIRONMENT VARIABLES
sulogin looks for the environment variable SUSHELL or sushell to determine what shell to start. If the environment variable is not set, it
will try to execute root's shell from /etc/passwd. If that fails it will fall back to /bin/sh.
This is very valuable together with the -b option to init. To boot the system into single user mode, with the root file system mounted
read/write, using a special "fail safe" shell that is statically linked (this example is valid for the LILO bootprompt)
boot: linux -b rw sushell=/sbin/sash
FALLBACK METHODS
sulogin checks the root password using the standard method (getpwnam) first. Then, if the -e option was specified, sulogin examines these
files directly to find the root password:
/etc/passwd,
/etc/shadow (if present)
If they are damaged or nonexistent, sulogin will start a root shell without asking for a password. Only use the -e option if you are sure
the console is physically protected against unauthorized access.
AUTHOR
Miquel van Smoorenburg <miquels@cistron.nl>
SEE ALSO
init(8), inittab(5).
17 Jan 2006 SULOGIN(8)