Sponsored Content
Full Discussion: Booting Problem
Top Forums UNIX for Advanced & Expert Users Booting Problem Post 13639 by LivinFree on Tuesday 22nd of January 2002 01:52:03 AM
Old 01-22-2002
You need to make sure the lilo software is on your system - most likely is with Redhat. In Redhat, you should be able to simply run (as root) liloconfig.

If not, post back, and I'll be glad to help.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with booting

Hi! I installed Slackware on my computer so I thought I could have dual booting with ME, but that didn't work. So I installed another bootmanager that I find on internet. When I startup my computer the second bootmangaer that I did find on internet lets me choose system. When I have choosen... (3 Replies)
Discussion started by: Mr.Rudiment
3 Replies

2. UNIX for Dummies Questions & Answers

<< booting problem with redhat 8.0 >>

i have the Redhat installed in this Hard Drive and i wanna use it in this old computer of mine.. it works fine in my new computer.. but when i put it in my old one.. which is.. P1 150MHz 32MBramz it wont load the kernal and keeps on restarting the computer.. keeps on goin like this.. i get the GRUB... (2 Replies)
Discussion started by: dezithug
2 Replies

3. Solaris

Problem with 280R not booting

The box is in Houston, and I am in Dallas. Anyway, I do have serial access to the console. The box is hanging just after the WARNING's for the SDS modules not loading (normal boot message). I booted off CD, and mounted up all the file systems. Everything looked normal, and I could not find any... (3 Replies)
Discussion started by: 98_1LE
3 Replies

4. Solaris

Booting problem Veritas

Hi , I am having 490 Sun Fire Server ,Server having Two 72 GB each Disk.Disk are under veritas VM 4 control. Both disk are mirred with veritas VM4. Fisrt disk is encapsulate and other disk is mirred.System is working Fine but when I removed Fitrst Disk and reboot the system it does not boot from... (4 Replies)
Discussion started by: pradeeprajput_k
4 Replies

5. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

6. Ubuntu

Problem while booting linux

Hi all, We are using linux Redhat 9. While booting the server, it says /proc not mounted and it says "Segmentation fault" and doesn't continue with booting. Basically, it started while we inserted a pen drive and removed it without mounting and un mounting it. After removing the pen drive &... (1 Reply)
Discussion started by: mjdarm
1 Replies

7. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

8. AIX

Booting problem

Dears, I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line. Kindly find the attached screenshot. Anyway to let it login automatically to Desktop? Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies

9. AIX

Problem to booting up p730

Hi Everyone, We have IBM p730 that I am trying to booting up to AIX 7.1. But it stops at RUNTIME. C7004087 C7004091 C7004091 (show is code number twice) STANDBY RUNTIME The explanation for C7004091 is the final IPL status progress code to be displayed before the system reaches... (5 Replies)
Discussion started by: lilyn
5 Replies
PROOFD(1)						      General Commands Manual							 PROOFD(1)

NAME
proofd - PROOF (The Parallel ROOT Facility) DESCRIPTION
Using PROOF (The Parallel ROOT Facility) one can analyze trees in parallel on a cluster of computers. The PROOF system consists of the proofd(1) from-end program which is started via inetd(8). proofd takes care of user authentication and overlays itself then with the desired version of the proofserv(1) executable. The proofserv(1) is a basically the same as the ROOT interactive module root(1), except that it reads its commands from a socket instead of from the terminal. Since it is a remote server it will not do graphics and therefore is not linked with any graphics libraries (Motif, X11, etc.). SETTING UP PROOF
Since you need to handle sensitive system files, you need to have root (the user, not the program!) privileges. Also, it's recommended that you read the appropriate man(1) pages first. These are inetd(8) (the internet daemon), sysklogd(8) and syslog(3) (the system logger dae- mon), and init(8) (the SYSV process control initializer). In other words: Be very VERY carefull when installing proofd There, I said it. And ofcourse, no warrenties what so ever. 1 Make sure every node has ROOT installed. We'll assume you installed the ROOT applications in <bindir> (e.g. /usr/bin) and the PROOF configuration files in files in <proofdir>/etc (e.g. /usr/share/root/etc). 2 The TCP port 1094 was allocated by IANA, ( www.iana.org <Iwww.iana.org> ), to rootd, so add to /etc/services the lines: proofd 1093/tcp rootd 1094/tcp 3 On each node, add to /etc/inetd.conf the lines: proofd stream tcp nowait root <bindir>/proofd proofd <proofdir>/proof rootd stream tcp nowait root <bindir>/rootd rootd -i You can substitute the <proofdir> with any directory that holds your PROOF configuration, for example /etc/root/proof. However, it should be shared among all nodes in the cluster. 4 Restart inetd or force it to re-read the config file: kill -1 <inetd pid> If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/inetd restart or whatever is appropriate for your system. 5 On the master node, add to /etc/syslog.conf the line: local5,local6.debug <proofdir>/log/proof.log and all slave nodes: local5,local6.debug @<master hostname> where <master hostname> is domain name of the master node. All PROOF syslog messages will be collected on the master node. Just make one node in the cluster the master, all others are slaves. 6 On all nodes, change the below lines in /etc/syslog.conf, *.info;mail.none;news.none;authpriv.none /var/log/messages to: *.info;local5,local6,mail.none;news.none;authpriv.none /var/log/messages 7 Create an empty <proofdir>/log/proof.log: echo "" > <proofdir>/log/proof.log 8 Restart syslogd or force it to re-read the config file: kill -1 <syslogd pid>. If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/sysklogd restart or whatever is appropriate for your system. 9 Edit <proofdir>/etc/proof.conf to reflect your cluster configuration. See the example proof.conf file for more information. If you installed ROOT using some precompiled package (for example a Redhat Linux or a Debian GNU/Linux package), steps 2 to 4 may already be done for you. If you're running Linux, Steps 5 to 7 can be somewhat automated using the script proof-facility in <proofdir> of your distribution. This script uses syslog-facility(1), from the Linux syslog(1) distribution, and may run on other platforms as well - but no warrenties mind you! Step 9 is completely up to the user. EXAMPLE
That's it. To test PROOF try the following: root [1] gROOT->Proof("<master hostname>") root [2] gPROOF->Print() <shows information on the master and all active slave servers> root [3] .q FILES
<proofdir> The location of your PROOF data. In binary packages, like for Redhat LinuxI or Debian GNU/Linux, this will probably be /usr/share/root/proof. If you got a binary tar(1)-ball from the ROOT website, or a build it yourself without the static paths option, then this directory could be ROOTSYS/proof. However, you may set it to something else when starting your server. <proofdir>/etc This directory holds all the configuration files for your cluster(s). <proofdir>/etc/<cluster>.conf This is the cluster named <cluster> configuration file. See <proofdir>/etc/<cluster>.conf.sample for an example. <proofdir>/etc/motd This is Message-Of-The-Day file. See <proofdir>/etc/motd.sample for an example. <proofdir>/etc/noproof If this file is present, all PROOF services will be diabled. See <proofdir>/etc/noproof.sample for an example. <proofdir>/etc/proof.conf This is the PROOF configuration file. See <proofdir>/etc/proof.conf.sample for an example. ~/.rootnetrc.conf Configuration file for network access. Here you specify login names and pass word, so it MUST be read/write-able only by the user. See <proofdir>/etc/rootnetrc.conf.sample for an example. <proofdir>/log This directory holds the log files from the master and slaves. <proofdir>/log/proof.log Syslog(1) log file for PROOF. SEE ALSO
proofserv(1) , root(1) , rootd(1) More information can be found at the ROOT website: http://root.cern.ch <http://root.cern.ch> ORIGINAL AUTHORS
The ROOT team (see web page above): Rene Brun and Fons Rademakers COPYRIGHT
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as pub- lished by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foun- dation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA AUTHOR
This manual page was written by Christian Holm Christensen <cholm@nbi.dk>, for the Debian GNU/Linux system (but may be used by others). ROOT
Version 3 PROOFD(1)
All times are GMT -4. The time now is 02:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy