09-08-2015
Strange behaviour on Openserver 5.0.2 after 09/2015
Dear friends,
i am having some Problems with a Sco Openserver in a Box (normally on VMWare, importing it on a Virtualbox does the same).
When i boot up the system on xx/09/2015 i got fork failed - too many processes during startup.
The programs which should run on the server, do not run.
I can login, but i got no shell, instead i got: cannot fork to run /usr/bin/mapkey: Resource temporarily unavailable (error 11).
When i start the single user mode, then change the date to 08/2015, for example 31/08/2015, and then restart the server; it comes up like a charm, without any error.
If i change then the date of the system to the actual date the Server is working.
I have already tried a lot to make the server start the programs normally at boot time with the right date, but no luck:
disabling init scripts <P80
adding second swap space
adjusting Kernel Parameters (just doubling the values) on scoadmin -> kernel manager -> tune parameters -> users and group configuration
Does anybody know this kind of behaviour and has a hint for me?
thanks a lot
These 2 Users Gave Thanks to ChipperEs For This Post:
9 More Discussions You Might Find Interesting
1. Linux
Hi there,
first of all, here is my conf of a uname -a
Linux SAMBA 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown
on a fedora machine.
Here is my problem: every once in a while, the line containing root disappears in the /etc/passwd, disabling all logging on my server. Any one have... (0 Replies)
Discussion started by: penguin-friend
0 Replies
2. Shell Programming and Scripting
Can some-one give me a view to this :
I have a directory in an unix server, having permissions r-xr-xr-x .This directory is basically a source directory.
Now there is another directory basically the destination directory which has all the permissions.
Note:I log in as not the owner,but user... (5 Replies)
Discussion started by: navojit dutta
5 Replies
3. UNIX for Advanced & Expert Users
$ echo a.bc | sed -e "s/\|/\\|/g"
|a|.|b|c|
$
Is the behavior of the sed statement expected ? Or is this a bug in sed ?
OS details
Linux 2.6.9-55.0.0.0.2.ELsmp #1 SMP Wed May 2 14:59:56 PDT 2007 i686 i686 i386 GNU/Linux (8 Replies)
Discussion started by: vino
8 Replies
4. UNIX for Dummies Questions & Answers
Had a strange thing going on with my code. It's ok I figured it out for myself.... (2 Replies)
Discussion started by: mrpugster
2 Replies
5. Shell Programming and Scripting
Hi all,
I want to do a very simple thing with sed. I want to print out the line number of a disk I have defined in /etc/exports, so I do:
It's all good, but here's the problem. When I define md0 in a variable, I get nothing from sed:
Why is that? can anybody please help?
Thanks (2 Replies)
Discussion started by: alirezan
2 Replies
6. Shell Programming and Scripting
Hi All,
I got a strange problem here. I have a perl script which is fetching data from a database table and writing a file with that data.
If i run that script from linux command line, the file it creates is a normal ascii text file without any binary character in it.But... (9 Replies)
Discussion started by: DILEEP410
9 Replies
7. HP-UX
Hi all,
I am using HP-UX and I have just noticed that when I log into the network it seems to save the previous windows that were subsequently closed on previous occasions. Does anyone know when I log in, it seems to display these previous windows, e.g. nedit windows open again?
Does... (1 Reply)
Discussion started by: cyberfrog
1 Replies
8. Shell Programming and Scripting
Hello,
I was trying to identify lines who has a word of the following pattern "xyyx" (where x, and ys are different characters).
I was trying the following grep -
egrep '(\S)()\2\1'
This pattern do catches the wanted pattern, but it also catches "GGGG" or "CCCC" patterns. I was trying to... (5 Replies)
Discussion started by: itskov
5 Replies
9. Red Hat
Hi all,
I'm having this scenario which for the moment I cannot resolve. :(
I wrote a script to make a dump/export of the oracle database. and then put this entry on crontab to be executed daily for example.
The script is like below:
cat /home/oracle/scripts/db_backup.sh
#!/bin/ksh
... (3 Replies)
Discussion started by: enux
3 Replies
init(8) System Manager's Manual init(8)
NAME
init - Process control initialization
SYNOPSIS
/sbin/init [0123456789MmQqSs]
DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in
the inittab file. The init program reads and processes the entries in the inittab file.
The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at
that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab
file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init
that tell it which run level to change to.
Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab
file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the
initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the
user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the
virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a
message on the console stating the location of the virtual console.
To change the run level, the user specifies either the 0, 2, 3, or s flag.
For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run
level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these
entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file
systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to
be handled for that level.
Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child
process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal
that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new
entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi-
ately reexamine the inittab file, invoke the init program with the q flag.
FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a
multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no
such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces
init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from
/etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter-
minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single
user state with only the essential kernel services.
FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file
RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8)
Calls: kill(2), reboot(2)
Files: inittab(4) delim off
init(8)