Sponsored Content
Full Discussion: System info
Top Forums Programming System info Post 302265352 by kandrewo on Saturday 6th of December 2008 08:54:14 PM
Old 12-06-2008
that doesn't work for multiple systems, SunOS for example. And this requires using system tools. Is there possibility to implement such features as C code?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How do I find out general system info?

How can I find out what type of processor, and speed, along with memory info such as RAM and storage. Also how do I scrollup on the shell? (2 Replies)
Discussion started by: AllyJones
2 Replies

2. UNIX for Dummies Questions & Answers

Finding system info

Can someone tell me the command to display the info about the CPU? I need the CPI id.. of my SUN box. Solaris 8. It's some totally un-intuitive command, and i can't recall it. tnx. (3 Replies)
Discussion started by: ireeneek
3 Replies

3. Programming

Does anyone have example code for getting File System info on AIX

I'm looking for example C source of how to get file system information on AIX systems. Does anyone have anything? (3 Replies)
Discussion started by: StuBob
3 Replies

4. Solaris

collecting system harware info

I'm looking for commands I can run on Solaris (8 and 9) to collect information regarding the installed hardware, ie network cards, sizes of physical disks in system, sizes of physical disks in connected storage array, etc. (1 Reply)
Discussion started by: soliberus
1 Replies

5. UNIX for Advanced & Expert Users

The best way to skin a cat OR how do I get file system info on the most basic level?

Hi, We have an FTP server (vsftpd) running on Linux, that I've kinda built a "Data Management" system around. I could use some ideas as to the best way to handle/create "triggers" for file notifications. Internal users drag 'n drop files from their Windows boxes to the server via Samba... (2 Replies)
Discussion started by: mph
2 Replies

6. Shell Programming and Scripting

recommended perl modules for system info.

I am doing some bespoke nagios plugins. can anyone recommend any good perl modules for system checks. disks, memory, processes, load avgs, networks, etc etc. everything basically. they will need to perform on bsd, aix, solaris, linux. any recommendations? (2 Replies)
Discussion started by: bigearsbilly
2 Replies

7. UNIX for Dummies Questions & Answers

Basic System Info Template

If your boss ask you to create a template for all UNIX systems. Max 10 questions of the system. What would you put down? The system can be any UNIX flavor. Some examples: 1. system name 2. OS 3. ETC What would be for you the most important and relevants. (2 Replies)
Discussion started by: 300zxmuro
2 Replies

8. Solaris

How to find FC info on Sun x86 system?

Hi, we have a Sun x4150 server connecting to Brocade switches. I need to get all WWN on the Sun server. Here is the result: # fcinfo hba-port No Adapters Found. # prtconf -vp | grep -i wwn # luxadm probe ERROR: No Fibre Channel Adapters found. # luxadm -e port ERROR: No Fibre Channel... (2 Replies)
Discussion started by: aixlover
2 Replies

9. AIX

Successful user login, yet system claims invalid info

I have four AIX 6.1.7.4 systems freshly built and ready for our DBAs to do their work. Of the three one runs into an odd issue while logging in as himself, using Putty with ssh protocols. He logs in successfully, but also gets the following error message: : 3004-300 You entered an invalid login... (2 Replies)
Discussion started by: Mike Brendan
2 Replies
RESCUE(8)						    BSD System Manager's Manual 						 RESCUE(8)

NAME
rescue -- rescue utilities in /rescue DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition to a dynamically-linked root beginning with FreeBSD 5.2, there is a real possibility that the standard tools in /bin and /sbin may become non-functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do not have full use of the locale, pam(3), and nsswitch libraries. If your system fails to boot, and it shows a prompt similar to: Enter full pathname of shell or RETURN for /bin/sh: the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command: /rescue/mount -uw / The next step is to double-check the contents of /bin, /sbin, and /usr/lib, possibly mounting a FreeBSD rescue or ``live file system'' CD-ROM (e.g., disc2 of the officially released FreeBSD ISO images) and copying files from there. Once it is possible to successfully run /bin/sh, /bin/ls, and other standard utilities, try rebooting back into the standard system. The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. To build a FreeBSD system where space is critical, /rescue can be used as a replacement for the standard /bin and /sbin directories; simply change /bin and /sbin to be symbolic links pointing to /rescue. Since /rescue is statically linked, it should also be possible to dispense with much of /usr/lib in such an environment. In contrast to its predecessor /stand, /rescue is updated during normal FreeBSD source and binary upgrades. FILES
/rescue Root of the rescue hierarchy. SEE ALSO
crunchgen(1), crash(8) HISTORY
The rescue utilities first appeared in FreeBSD 5.2. AUTHORS
The rescue system was written by Tim Kientzle <kientzle@FreeBSD.org>, based on ideas taken from NetBSD. This manual page was written by Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>. BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added into the ncurses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr. BSD
July 23, 2003 BSD
All times are GMT -4. The time now is 04:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy