Sponsored Content
Top Forums UNIX for Advanced & Expert Users Problems when rebooting the system Post 99849 by matrixmadhan on Wednesday 22nd of February 2006 12:36:39 AM
Old 02-22-2006
seems to be a misconfiguration for your hardware.

check for the entry in /etc/inittab
something like
x:<respawn>

then,
thats init's fail-safe mechanism to abort boot ( runlevel - 5) preventing
itself from entering infinite loop,

my suggestion would be to better,
remove the line
and try booting again at runlevel - 5.
I have heard of this problem and not encountered so far, so better rethink about the suggestion
( !!! are frontiers are good !!! )
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Prints Problems on Unix system

We are experiencing printing problems coming from an Unix host. In Feb. 05 we applied patches to the Unix operating system. Shortly the patches were applied we began experiencing problems printing on a IBM 6400 that emulates an Epson printer. When the printing starts we can print about 10 pages and... (1 Reply)
Discussion started by: ddameron
1 Replies

2. UNIX for Advanced & Expert Users

File system problems

Hi All, I am currently running Linux on a file server. The server starts experiencing problems (slow access, no access). After a shutdown and reboot, the file system is corrupted and requires to run fsck to clean up. Is this signs of a failing hard drive? Ken (2 Replies)
Discussion started by: kmcvey
2 Replies

3. AIX

system command and threads problems

Hi, my name is German. Im working with an aix over one year and i have developed a PRO*C multithread process that reads commands from a table and execute it in parallel (one command by thread) with a system function call, so depending the process exit code (system return value) , I put a mark... (2 Replies)
Discussion started by: german83
2 Replies

4. UNIX for Advanced & Expert Users

Suse 9.3 system rebooting automatically

Hello, Can anyone tell me where I can start looking to determine why a suse linux box is reboot automatically.... When doing the last command I get the below. It shows the reboot's... Any help would be appreciated. Thanks. root pts/0 xxxxx.xxx Mon Jun 23 13:50 still logged in... (2 Replies)
Discussion started by: benefactr
2 Replies

5. AIX

hmc not rebooting

Anyone faced this? I rebooted the HMC through command line after patch installation (hmcshutdown -t now -r) The strange thing happened was the hmc never rebooted, I was not able to connect it through graphical view or through ssh, but the session through which i issued the command was still... (4 Replies)
Discussion started by: balaji_prk
4 Replies

6. Linux

Sabayon - KDE4.2 Problems accessing system management - all greyed out

I have just loaded Sabayon KDE4.2. I have a 64bit comp and have tried several Linux/Unix os and have had problems with all of them and now it seems this one as well. I can't load my printer up and I cannot access any login management. I have had trouble accessing my Login Manager. I have looked... (3 Replies)
Discussion started by: Tony_photoplus
3 Replies

7. UNIX for Advanced & Expert Users

System V IPC problems

Hi all, Is there a situation like system assigning same ID's for semaphores and shared memory at the same time. Ex: When I try to create 10 Shared memory objects with starting key as 0x1500 and 10 semaphore objects with starting key as 0x1234 in the same program. Assume those are not deleted... (2 Replies)
Discussion started by: gkreddy
2 Replies

8. Ubuntu

Login Problems when the system is grub mode

Hi Experts, I am using ubuntu.When i am trying to login it is showing grub ..How i can overcome to this problem..Pls reply me ASAP.. Thanks, Sree (1 Reply)
Discussion started by: sree vasu
1 Replies

9. What is on Your Mind?

Rebooting a career

Apologies if this is not the correct place to post this. I used to have a job supporting several custom applications that ran on Unix platforms. I used shell scripting, sed, awk, and SQL, but all on a pretty basic level. I also performed non-technical tasks like helping with project management,... (4 Replies)
Discussion started by: intranslation
4 Replies
ATTILA(1)						  Alliance - attila User's Manual						 ATTILA(1)

NAME
attila - A Tool Installer SYNOPSIS
attila [ -h ] [ -S ] [ -U ] [ -F ] [ -A ] [ --help ] [ --ssh ] [ --user ] [ --asim ] [ --prefix=INSTALL_DIR ] [ --builddir=BUILD_DIR ] --tool=name1 [ --tool=name2... ] [ -c- configure_arg1 [ configure_arg2 ... ] ] [ -m- make_arg1 [ make_arg2... ] ] DESCRIPTION
attila automates the process of compiling and installing one or more Alliance tools. The tool can be installed either in the user's account (during the devellopment stage) or in the Alliance system wide tree (for instance /asim/alliance) when a new version is made avalaible to all. attila proceed with the following steps : 1. Checks if the sources of tools are present in the user's account. If not, check them out from the Alliance CVS tree. Note that you must have access to it. 2. In case of --asim or --full installations, attila will fork itself on one Linux computer (currently bip) and on one Solaris computer (beny). As to connect on thoses computer it will uses rsh so you must setup your ~/.rhosts to access them whithout passwords. You also can uses ssh (but the procedure to allow automatic login is more complicated). 3. Run autostuff for the tool in the ~/alliance/src directory. 4. Run configure in the build directory (see below). 5. Install the tool in the local install directory (see below) or in the system-wide Alliance directory rooted under /asim/alliance. After an --asim install: the build directory tree of the tool will be removed to avoid messing with further local installations. DIRECTORY STRUCTURE attila relies on the following tree structure : (all paths below are given relative to the user's home directory) o ~/alliance/src where the tools sources are to be found. o ~/alliance/Linux/build/$TOOL : the top directory under which the tool will be compiled for Linux. This is where the configure script will be run. o ~/alliance/Linux/install : the top of the install tree when the tool is compiled locally for Linux. Under this directory you will found (at least) : ./bin, ./lib and ./include. o ~/alliance/Solaris/build/$TOOL : the tool's build directory for Solaris. o ~/alliance/Solaris/install : top of the local install tree for Solaris. CVS CHECKOUT If the sources of the requested tool(s) are not found under ~/alliance/src/ attila will try to check them out. So, as says above, you must have access rights to the Alliance CVS tree. In addition to the tool(s) sources, it will also checks for the minimal set of files needed for configure to run. As for now : o autostuff o alliance.m4 o motif.m4 o Makefile.am GUESSING CVSROOT The root of the CVS tree will be set according to the following rules : 1. Uses the user's environment variable CVSROOT if sets. 2. Uses the attila default value sets in attila.conf (variable ATTILA_CVSROOT). GUESSING ALLIANCE_TOP The root of the Alliance installed distribution tree will be set according to the following rules : 1. Uses the user's environment variable ALLIANCE_TOP if sets. 2. Uses the attila default value sets in attila itself (variable ATTILA_ALLIANCE_TOP). ALLIANCE_TOP: is set in attila itself because its value is a prerequisite to load the configuration file attila.conf which is in the directory $ALLIANCE_TOP/etc/. ARGUMENTS
attila accepts the followings arguments : o -h, --help : print help. o -S, --ssh : uses ssh instead of rsh to connect to the remote computers (in case of --asim or --full). o -U, --user : perform a local installation. o -F, --full : install for all avalaibles architectures (currently Linux and Solaris). o -A, --asim : install in the system-wide directory (/asim/alliance). o --prefix=INSTALL_DIR : override the default installation directory. o --builddir=BUILD_DIR : override the default building directory. o --tool=name1 : name of the tool to be installed. o -c- configure_arg1 : all arguments following -c- (until a -m- is encountered) are passed as is to the subsequent call to configure. For example, if you want to first use your local libraries, give --enable-devel. If you want to link or install dynamic libraries, give --enable-alc-shared for alliance libraries and give --enable-shared for other libraries. o -m- make_arg1 : all arguments following -m- are passed as is to the subsequent call to make. If no -m- argument is given, then install is assumed. If you want to completly uninstall a tool and clean it's build directory you can pass uninstall clean CONFIGURATION FILE ATTILA.CONF The configuration file is located in $ALLIANCE_TOP/etc. This file is to be read by the sh shell. It sets up the following variables : o LINUX_TARGET : the computer where to compile for the Linux architecture (default bip). o LINUX_CC : the name or full path to to the C compiler for Linux system (default gcc3). o LINUX_CXX : the name or full path to to the C++ compiler for Linux system (default g++3). o SOLARIS_TARGET : the computer where to compile for the Solaris architecture (default beny). o SOLARIS_CC : the name or full path to to the C compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o SOLARIS_CXX : the name or full path to to the C++ compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o ATTILA_CVSROOT : the root of the Alliance CVS tree (default /users/outil/alliance/cvsroot). o CVS_STARTUP_FILES : the minimal set of files needed to run configure. EXAMPLES
Compile & install nero tool on the local computer (must be either a Linux or a Solaris one) : $ attila --tool=nero Compile & install nero tool for all architectures (currently only Linux and Solaris are supported) : $ attila --full --tool=nero Compile & install nero tool in the system-wide directory (a new version for everyone to use) : $ attila --asim --tool=nero Compile & install mbk then genlib (the order is significant) in a row for a local install on the current computer : $ attila --tool=mbk --tool=genlib Compile nero tool and link it against the locally installed libraries (if any). $ attila --tool=nero -c- --enable-devel Remove poire tool from the system-wide tree. (poire is the old name of nero). $ attila --asim --tool=poire -m- uninstall ASIM
/LIP6 13 October 2002 ATTILA(1)
All times are GMT -4. The time now is 03:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy