Sponsored Content
Full Discussion: Need help from E280R owners
Operating Systems Solaris Need help from E280R owners Post 75365 by Don.Key on Friday 17th of June 2005 07:40:05 AM
Old 06-17-2005
Question Need help from E280R owners

Hello,

I have recently aquired an E280R chassis, that is one of the first E280R chassis so it still features old fan block from 420R (540-4434).

Unfortunately I have 900Mhz X7009A CPUs to go into this machine and those need a better fan block (540-5088) because they do overheat Smilie.

Could someone who currently owns a E280R with 540-5088 fan cage tell me which fans are used there? It is easely visible if you open the top cover.

Many, many thanks ahead.

Don
 

4 More Discussions You Might Find Interesting

1. AIX

Identifying Semaphore Owners

Hi, I have an AIX server which has a number of root owned semaphores. Is there a way of identifying which processes/threads own these processes so that they can be removed. I there also a way to remove shared memory segments in a similar way Thanks. \ (1 Reply)
Discussion started by: backslash
1 Replies

2. Shell Programming and Scripting

Find only files/directories with different permissions/owners

My git post-update has the following lines in it to make sure the permissions are set right: find /usr/local/apache/htdocs -type d -print0 | xargs -0 chmod 755 find /usr/local/apache/htdocs -type f -print0 | xargs -0 chmod 644 chown -R apache:apache /usr/local/apache/htdocsThe only problem is... (5 Replies)
Discussion started by: dheian
5 Replies

3. UNIX for Dummies Questions & Answers

Awk/script to list the owners of files

I have to list the files in a directory and along with that, list the owner of each of those files. Can someone please help me with a way to get this info please? Gayathri (2 Replies)
Discussion started by: ggayathri
2 Replies

4. HP-UX

Script execution is very slow when trying to find all files and their owners on HP-UX box

Hi, I have a HP-UX server were I need to list all the files in the entire file system, their directory path, last modified date, owner and group. I do not need to search the file contents. I created the script given below and I am excluding directories and files of type tmp, temp and log. The... (4 Replies)
Discussion started by: Adyan Faruqi
4 Replies
MACHINE-INFO(5) 						   machine-info 						   MACHINE-INFO(5)

NAME
machine-info - Local machine information file SYNOPSIS
/etc/machine-info DESCRIPTION
The /etc/machine-info file contains machine metadata. The basic file format of machine-info is a newline-separated list of environment-like shell-compatible variable assignments. It is possible to source the configuration from shell scripts, however, beyond mere variable assignments no shell features are supported, allowing applications to read the file without implementing a shell compatible execution engine. /etc/machine-info contains metadata about the machine that is set by the user or administrator. Depending on the operating system other configuration files might be checked for machine information as well, however only as fallback. You may use hostnamectl(1) to change the settings of this file from the command line. OPTIONS
The following machine metadata parameters may be set using /etc/machine-info: PRETTY_HOSTNAME= A pretty human-readable UTF-8 machine identifier string. This should contain a name like "Lennart's Laptop" which is useful to present to the user and does not suffer by the syntax limitations of internet domain names. If possible, the internet hostname as configured in /etc/hostname should be kept similar to this one. Example: if this value is "Lennart's Computer" an Internet hostname of "lennarts-computer" might be a good choice. If this parameter is not set, an application should fall back to the Internet host name for presentation purposes. ICON_NAME= An icon identifying this machine according to the XDG Icon Naming Specification[1]. If this parameter is not set, an application should fall back to "computer" or a similar icon name. CHASSIS= The chassis type. Currently, the following chassis types are defined: "desktop", "laptop", "convertible", "server", "tablet", "handset", "watch", and "embedded", as well as the special chassis types "vm" and "container" for virtualized systems that lack an immediate physical chassis. Note that many systems allow detection of the chassis type automatically (based on firmware information or suchlike). This setting (if set) shall take precedence over automatically detected information and is useful to override misdetected configuration or to manually configure the chassis type where automatic detection is not available. DEPLOYMENT= Describes the system deployment environment. One of the following is suggested: "development", "integration", "staging", "production". LOCATION= Describes the system location if applicable and known. Takes a human-friendly, free-form string. This may be as generic as "Berlin, Germany" or as specific as "Left Rack, 2nd Shelf". EXAMPLE
PRETTY_HOSTNAME="Lennart's Tablet" ICON_NAME=computer-tablet CHASSIS=tablet DEPLOYMENT=production SEE ALSO
systemd(1), os-release(5), hostname(5), machine-id(5), hostnamectl(1), systemd-hostnamed.service(8) NOTES
1. XDG Icon Naming Specification http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html systemd 237 MACHINE-INFO(5)
All times are GMT -4. The time now is 05:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy