Sponsored Content
Full Discussion: AT&T UNIX PC won't boot
Special Forums Hardware AT&T UNIX PC won't boot Post 302634661 by ThomasMcA on Thursday 3rd of May 2012 04:11:19 PM
Old 05-03-2012
Is the fuse in the PC, or in the building? If it's in the PC, then the power supply for the PC may be bad. If it's for the building, it could just be an overloaded electrical circuit.
 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris (9) won't boot!

Hi, I've just bought an Ultra 60 running solaris 9 (or so I've been led to believe). When I start up, it looks for a (presumably) domain/network to hook up to and the following messages are displayed: Boot device: net file and args: Network link setup failed Please check cable and try... (3 Replies)
Discussion started by: alarmcall
3 Replies

2. AIX

server won't boot

Hi all , i was trying to upgrade firmware on machine 7028-6E4 and it failed . Now machine does not boot anymore , i can not get SMC menu either ... What are my options ? Thanks, Rahim (1 Reply)
Discussion started by: rahim
1 Replies

3. Solaris

nfsd won't start at boot up

Hi Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say... (19 Replies)
Discussion started by: dcshungu
19 Replies

4. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

5. Solaris

Cloned drive won't boot ?

Solaris system version 6 I cloned the drive using the DD command. Using the format command and examining the partitions, all looks the same as the original drive. Problem: When I attach the cloned drive as the master, and only drive in system, it will not boot. Error messages: ... (9 Replies)
Discussion started by: HikerLT
9 Replies

6. Solaris

Ultra 60 won't boot

I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies

7. UNIX for Dummies Questions & Answers

Linux won't boot

I'm trying to install Fedora 9 on a Dell OptiPlex GX300 machine. The instalation runs properly, but when the computer restarts after the instalation, it simply won't boot, like there's no OS installed. I tried diffrent Linux distributions, but nothing works. This are the partitions, maybe it's... (12 Replies)
Discussion started by: teis
12 Replies

8. AIX

won't mount /usr...won't boot fully

Hello: NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies

9. SCO

SCO UNIX Won't Boot

Our system is not booting up properly. It keeps going to this screen: Enter Run Level (0-6, s or S): I tried to hit all nos# 0-6 is just goes to hung state. Tried s or S & it brings me to single user mode. I've checked the file systems & found out that all three had 98%. I tried to... (86 Replies)
Discussion started by: jedimaster
86 Replies

10. UNIX for Dummies Questions & Answers

New kernel won't boot

I compiled new kernel in linux 10.04 called linux-2.6.26.8-xenomai, it runs alongside the other kernel, but when I want to boot it I get an error message saying: Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sda5 does not exist. After making the modules and headers I made the... (4 Replies)
Discussion started by: mdop
4 Replies
PG_CONFIG(1)						  PostgreSQL 9.1.9 Documentation					      PG_CONFIG(1)

NAME
pg_config - retrieve information about the installed version of PostgreSQL SYNOPSIS
pg_config [option...] DESCRIPTION
The pg_config utility prints configuration parameters of the currently installed version of PostgreSQL. It is intended, for example, to be used by software packages that want to interface to PostgreSQL to facilitate finding the required header files and libraries. OPTIONS
To use pg_config, supply one or more of the following options: --bindir Print the location of user executables. Use this, for example, to find the psql program. This is normally also the location where the pg_config program resides. --docdir Print the location of documentation files. --htmldir Print the location of HTML documentation files. --includedir Print the location of C header files of the client interfaces. --pkgincludedir Print the location of other C header files. --includedir-server Print the location of C header files for server programming. --libdir Print the location of object code libraries. --pkglibdir Print the location of dynamically loadable modules, or where the server would search for them. (Other architecture-dependent data files might also be installed in this directory.) --localedir Print the location of locale support files. (This will be an empty string if locale support was not configured when PostgreSQL was built.) --mandir Print the location of manual pages. --sharedir Print the location of architecture-independent support files. --sysconfdir Print the location of system-wide configuration files. --pgxs Print the location of extension makefiles. --configure Print the options that were given to the configure script when PostgreSQL was configured for building. This can be used to reproduce the identical configuration, or to find out with what options a binary package was built. (Note however that binary packages often contain vendor-specific custom patches.) See also the examples below. --cc Print the value of the CC variable that was used for building PostgreSQL. This shows the C compiler used. --cppflags Print the value of the CPPFLAGS variable that was used for building PostgreSQL. This shows C compiler switches needed at preprocessing time (typically, -I switches). --cflags Print the value of the CFLAGS variable that was used for building PostgreSQL. This shows C compiler switches. --cflags_sl Print the value of the CFLAGS_SL variable that was used for building PostgreSQL. This shows extra C compiler switches used for building shared libraries. --ldflags Print the value of the LDFLAGS variable that was used for building PostgreSQL. This shows linker switches. --ldflags_ex Print the value of the LDFLAGS_EX variable that was used for building PostgreSQL. This shows linker switches used for building executables only. --ldflags_sl Print the value of the LDFLAGS_SL variable that was used for building PostgreSQL. This shows linker switches used for building shared libraries only. --libs Print the value of the LIBS variable that was used for building PostgreSQL. This normally contains -l switches for external libraries linked into PostgreSQL. --version Print the version of PostgreSQL. If more than one option is given, the information is printed in that order, one item per line. If no options are given, all available information is printed, with labels. NOTES
The option --includedir-server was added in PostgreSQL 7.2. In prior releases, the server include files were installed in the same location as the client headers, which could be queried with the option --includedir. To make your package handle both cases, try the newer option first and test the exit status to see whether it succeeded. The options --docdir, --pkgincludedir, --localedir, --mandir, --sharedir, --sysconfdir, --cc, --cppflags, --cflags, --cflags_sl, --ldflags, --ldflags_sl, and --libs were added in PostgreSQL 8.1. The option --htmldir was added in PostgreSQL 8.4. The option --ldflags_ex was added in PostgreSQL 9.0. In releases prior to PostgreSQL 7.1, before pg_config came to be, a method for finding the equivalent configuration information did not exist. EXAMPLE
To reproduce the build configuration of the current PostgreSQL installation, run the following command: eval ./configure `pg_config --configure` The output of pg_config --configure contains shell quotation marks so arguments with spaces are represented correctly. Therefore, using eval is required for proper results. PostgreSQL 9.1.9 2013-04-01 PG_CONFIG(1)
All times are GMT -4. The time now is 06:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy