10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello Team .
I am working a health check script ( bash) to run on linux server ( RedHat) and requirements are
1. The o/p of script need to be send to two diff files . I am testing with tee command . But I am not successful yet , any recommendations if that is the right approach ?
2. The same... (2 Replies)
Discussion started by: Varja
2 Replies
2. Shell Programming and Scripting
Hi Guys
I have a Solaris 10 server running Oracle database most of the sessions are slow when forking resource/processes on the O/S.
How can I resolve this issue or how do I see the time it takes to fork a process from the O/S?
Thanks
Pleasse help!!! (3 Replies)
Discussion started by: Phuti
3 Replies
3. Shell Programming and Scripting
Hi friends,,,
I am running one server on Ubuntu 12.04 LTS 32-bit, some times my pc restarts automatically, with no reason, I have a script to start server which requires root password. in this directory
/myserver/start_server.sh
How can I do this ?
and some scripts I am having that I... (1 Reply)
Discussion started by: Akshay Hegde
1 Replies
4. UNIX and Linux Applications
I would like to call a function called CIRCLE which is further beind called by other function but in a loop that CIRCLE fuction is being called. And this CIRCLE function starts another process which takes 3 hours to complete again, if i put that process in nohup &, I can go to the next command... (2 Replies)
Discussion started by: venugopalsmartb
2 Replies
5. Shell Programming and Scripting
Hi All,
Sorry to bother you all if my query is silly. Can you please clarify my doubts on defunct processes.
Actually coming to the scenario, i have a server which is under cluster environment. Server B is having problems with the defunct process. There was a cron scheduled on Server B which... (0 Replies)
Discussion started by: reddybs
0 Replies
6. Shell Programming and Scripting
Hey everybody, this is my first post so be gentle. I have two Sun 5220's running Solaris 10 that are directly connected with a cross-over cable at Gig. One of these boxes is my production Oracle server which generates a 50GB dump file every evening at 10:50. The other Solaris is a devolopment... (8 Replies)
Discussion started by: Countificus
8 Replies
7. UNIX for Advanced & Expert Users
Hi,
we reboot our Linux server yesterday and since then (specialy last night) no job from crontab has run. Any idea ? What should I look for to investigate?
Many thanks. (5 Replies)
Discussion started by: big123456
5 Replies
8. Linux
Hi all,
i have a script in /etc/init.d directory.
-rwxr-xr-x 1 root root 26 Mar 28 16:00 myscript
I need it to run when my linux reboots/startup. However is it not being executed. Do i need to put in in the rc.local directory? (1 Reply)
Discussion started by: new2ss
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
Would like to ask the experts if anyone knows how to run a script like this:
dtterm -title shell1
run process1 on shell1
dtterm -title shell2
run process2 on shell2
cheers!
p/s: sorry if i used the wrong forum, quite concussed after watching world cup for several nights; but I... (2 Replies)
Discussion started by: mochi
2 Replies
10. UNIX for Advanced & Expert Users
Hi,
My server runnning on SUN Solaris rel.5.5.1. I have been facing this issues for years. I have some Xbase databases running on the server. User is using emulation software to telnet to server for accessing application. If user logout application abnormally - by closing windows session, then... (2 Replies)
Discussion started by: lowtaiwah
2 Replies
platform(4) File Formats platform(4)
NAME
platform - directory of files specifying supported platforms
SYNOPSIS
.platform
DESCRIPTION
The Solaris operating environment release includes the .platform directory, a new directory on the Solaris CD image. This directory con-
tains files (created by Sun and Solaris OEMs) that define platform support. These files are generically referred to as platform definition
files. They provide a means to map different platform types into a platform group.
Platform definition files in the .platform directory are used by the installation software to ensure that software appropriate for the
architecture of the system will be installed.
Sun provides a platform definition file named .platform/Solaris . This file is the only one that can define platform groups to which other
platform definition files can refer. For example, an OEM platform definition file can refer to any platform group specified in the Solaris
platform definition file.
Other platform definition files are delivered by OEMs. To avoid name conflicts, OEMs will name their platform definition file with an OEM-
unique string. OEMs should use whatever string they use to make their package names unique. This unique string is often the OEM's stock
symbol.
Comments are allowed in a platform definition file. A "#" begins a comment and can be placed anywhere on a line.
Platform definition files are composed of keyword-value pairs, and there are two kinds of stanzas in the file: platform group definitions
and platform identifications.
o Platform group definitions:
The keywords in a platform group definition stanza are:
PLATFORM_GROUP The PLATFORM_GROUP keyword must be the first keyword in the platform group definition stanza. The value
assigned to this keyword is the name of the platform group, for example:
PLATFORM_GROUP=sun4c
The PLATFORM_GROUP name is an arbitrary name assigned to a group of platforms. However, PLATFORM_GROUP typi-
cally equals the output of the uname -m command. PLATFORM_GROUP value cannot have white space and is limited
to 256 ASCII characters.
INST_ARCH The instruction set architecture of all platforms in the platform group, for example:
INST_ARCH=sparc
The INST_ARCH keyword value must be the value returned by the uname -p command on all platforms in the plat-
form group.
o Platform identifications:
The keywords in a platform identification stanza are:
PLATFORM_NAME The PLATFORM_NAME keyword must be the first keyword in the platform identification stanza. The PLAT-
FORM_NAME is the name assigned to the platform, for example:
PLATFORM_NAME=SUNW,SPARCstation-5
Typically, this name is the same as the value returned by the uname -icommand on the machine, but it need
not be the same.
The PLATFORM_NAME value cannot have white space and is limited to 256 ASCII characters. If it contains
parentheses, it must contain only balanced parentheses. For example. the string "foo(bar)foo" is a valid
value for this keyword, but "foo(bar" is not.
The other keywords in the platform identification stanza can be in any order, as long as the PLATFORM_NAME
keyword is first.
PLATFORM_ID The value returned by the uname -i command on the machine, for example:
PLATFORM_ID=SUNW,SPARCstation-5
MACHINE_TYPE The value returned by the uname -m command on the machine, for example:
MACHINE_TYPE=sun4c
IN_PLATFORM_GROUP The platform group of which the platform is a member, for example:
IN_PLATFORM_GROUP=sun4c
The platform group name must be specified in the same file as the platform identification stanza or in the
platform definition file with the name .platform/Solaris .
The IN_PLATFORM_GROUP keyword is optional. A platform doesn't have to belong to a platform group. If a
platform is not explicitly assigned to a platform group, it essentially forms its own platform group, where
the platform group name is the PLATFORM_NAME value. The IN_PLATFORM_GROUP value typically equals the output
of the uname -m command. IN_PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII char-
acters.
INST_ARCH The instruction set architecture of the platform, for example:
INST_ARCH=sparc
This field is only required if the platform does not belong to a platform group. The INST_ARCH keyword
value must be the value returned by the uname -i command on all platforms in the platform group.
COMPATIBILITY
The installation program will remain compatible with the old Solaris CD format. If a Solaris CD image does not contain any platform defini-
tion files, the installation and upgrade programs will select the packages to be installed based on machine type, that is, the value
returned by the uname -p command.
EXAMPLES
Example 1 Platform Group Definitions
The following example shows platform group definitions from the .platform/Solaris platform definition file.
#
PLATFORM_GROUP=sun4u
INST_ARCH=sparc
Example 2 Platform Identification Stanzas
The following example shows platform identification stanzas, which define systems that belong in a platform group, from the .plat-
form/Solaris platform definition file.
#
PLATFORM_NAME=SUNW,SunFire
PLATFORM_ID=SUNW,SunFire
IN_PLATFORM_GROUP=sun4u
PLATFORM_NAME=SUNW,Ultra-80
PLATFORM_ID=SUNW,Ultra-80
IN_PLATFORM_GROUP=sun4u
#
PLATFORM_NAME=SUNW,SunFire
PLATFORM_ID=SUNW,SunFire
IN_PLATFORM_GROUP=sun4u
#
PLATFORM_NAME=SUNW,Ultra-80
PLATFORM_ID=SUNW,Ultra-80
IN_PLATFORM_GROUP=sun4u
FILES
The .platform directory must reside as /cd_image/Solaris_vers/.platform, where
cd_image Is the path to the mounted Solaris CD (/cdrom/cdrom0/s0 by default) or the path to a copy of the Solaris CD on a disk.
Solaris_vers Is the version of Solaris, for example, Solaris_2.9.
NOTES
Typically, a platform identification stanza contains either a PLATFORM_ID or a MACHINE_TYPE stanza, but not both.
If both are specified, both must match for a platform to be identified as this platform type. Each platform identification stanza must con-
tain either a PLATFORM_ID value or a MACHINE_TYPE value. If a platform matches two different platform identification stanzas--one which
matched on the value of PLATFORM_ID and one which matched on the value of MACHINE_TYPE , the one that matched on PLATFORM_ID will take
precedence.
The .platform directory is part of the Solaris CD image, whether that be the Solaris CD or a copy of the Solaris CD on a system's hard
disk.
SunOS 5.11 19 Nov 2002 platform(4)