01-31-2018
Respawning
Yes. INIT "C1" through "C6" re-spawning too fast.
8 More Discussions You Might Find Interesting
1. IP Networking
I'm new to this.
My question is I have freebsd installed on one computer. I want to make it a file server. My main computer is windows XP. How do I make the freebsd machine in a fileserver. and so that windows xp can see it and access it (2 Replies)
Discussion started by: akari
2 Replies
2. UNIX for Dummies Questions & Answers
Dear all,
I am a windows user, am not into unix/linux at all.
however, I have a new client who is asking me if unix can act as file server.
i.e. my application imports files from several locations and put them in one location (on a shared folder on the server), so my application will be... (7 Replies)
Discussion started by: KBalquis
7 Replies
3. Solaris
root@test09 # ls -al /sbin/init
-r-xr-xr-x 1 root sys 550000 Jun 29 2002 /sbin/init
root@test09 # ls -al /usr/sbin/init
-r-xr-xr-x 1 root sys 37100 Jun 29 2002 /usr/sbin/init (2 Replies)
Discussion started by: userking
2 Replies
4. Shell Programming and Scripting
Hello there,
I hope I took the right forum...
I never worked with Perl, but now I have to get a simple fileserver running. The goal is to deliver an XML file (it's part of a new security model in the Flashplayer, see Adobe - Developer Center : Setting up a socket policy file server for more... (9 Replies)
Discussion started by: blemmo
9 Replies
5. UNIX for Dummies Questions & Answers
When you open a file on a fileserver from your client, what type of operation takes place on the server? I imagine the server's hard drive reads the file that the client has requested, and then makes it available somehow through the network share, is that accurate? Also what service on Unix/Linux... (0 Replies)
Discussion started by: glev2005
0 Replies
6. Solaris
I am trying to get an old Ultra 45 to boot and it is stuck in a loop. I cannot get anything to come up on a monitor, so when I hook up a serial connection to the TTYa interface I see the following output:
@(#)OBP 4.21.2 2005/12/22 17:17 Sun Ultra 45 Workstation
Clearing TLBs
Loading... (0 Replies)
Discussion started by: Madrox72
0 Replies
7. Shell Programming and Scripting
So, this is weird... I'm running this command:
iotop -o -P -k -bt -d 5
I'd like to save the output relelvant to rsyslogd to a file, so I do this:
iotop -o -P -k -bt -d 5 | grep rsyslogd >> /var/log/rsyslogd
Nothing is written to the file! I can write the full output to the file:
... (2 Replies)
Discussion started by: treesloth
2 Replies
8. Shell Programming and Scripting
Hi, maybe someone could help me optimizing this little script.
It works so far, but when running, reboot does not work. If kill inotifywait reboot from shell works. I think some optimization is required here.
This script starts at the end of the boot process, from an external device and... (3 Replies)
Discussion started by: lowmaster
3 Replies
INIT(8) System Manager's Manual INIT(8)
NAME
init, rc - process control initialization
SYNOPSIS
/etc/init
/etc/rc
DESCRIPTION
Init is invoked as the last step of the boot procedure (see boot(8)). Generally its role is to create a process for each typewriter on
which a user may log in.
When init first is executed the console typewriter /dev/console. is opened for reading and writing and the shell is invoked immediately.
This feature is used to bring up a single-user system. If the shell terminates, init comes up multi-user and the process described below
is started.
When init comes up multiuser, it invokes a shell, with input taken from the file /etc/rc. This command file performs housekeeping like
removing temporary files, mounting file systems, and starting daemons.
Then init reads the file /etc/ttys and forks several times to create a process for each typewriter specified in the file. Each of these
processes opens the appropriate typewriter for reading and writing. These channels thus receive file descriptors 0, 1 and 2, the standard
input, output and error files. Opening the typewriter will usually involve a delay, since the open is not completed until someone is
dialed up and carrier established on the channel. Then /etc/getty is called with argument as specified by the last character of the ttys
file line. Getty reads the user's name and invokes login(1) to log in the user and execute the shell.
Ultimately the shell will terminate because of an end-of-file either typed explicitly or generated as a result of hanging up. The main
path of init, which has been waiting for such an event, wakes up and removes the appropriate entry from the file utmp, which records cur-
rent users, and makes an entry in /usr/adm/wtmp, which maintains a history of logins and logouts. Then the appropriate typewriter is
reopened and getty is reinvoked.
Init catches the hangup signal SIGHUP and interprets it to mean that the system should be brought from multi user to single user. Use
`kill -1 1' to send the hangup signal.
FILES
/dev/tty?, /etc/utmp, /usr/adm/wtmp, /etc/ttys, /etc/rc
SEE ALSO
login(1), kill(1), sh(1), ttys(5), getty(8)
INIT(8)