Sponsored Content
Full Discussion: Solaris 10 Slowness
Operating Systems Solaris Solaris 10 Slowness Post 302408306 by achenle on Monday 29th of March 2010 06:54:36 AM
Old 03-29-2010
The UltraSPARC III Cu CPU is from 2002 or so, IIRC.

How old is the Windows box you're running on? Is it 8 years old?
 

9 More Discussions You Might Find Interesting

1. Linux

slowness of Linux 8.0 server

Hi, I have a Linux 8.0 Redhat installed as a server. The samba configuration was done to allowed logging in to the server from windows workstations. I have a LAN, WAN connection. However, any time the workstation is trying to make a WAN connection it slow down all the systems on the network. Can... (0 Replies)
Discussion started by: kayode
0 Replies

2. SCO

Terminal Slowness

I have attempted to2find answers to this question: When logging into tty01 the system will take 5 to 10 seconds to display each character typed. Each other terminal will login correctly and display correctly2but not the first terminal. Rebooting was suggested on several sites and this has been... (2 Replies)
Discussion started by: ypanic
2 Replies

3. HP-UX

HP-UX Intermec Label Slowness

We recently moved from a Open VMS OS to HP-UX. When printing labels on Intermec 3400 printers we are seeing a delay of up to 3 minutes before labels print. We have printers going through a DEC Term servers and Jet Direct boxes. Any suggestions what might be causing this delay? (4 Replies)
Discussion started by: BIGJIM
4 Replies

4. Solaris

Login Slowness

Hi Folks My Sun Solaris servers are waiting for a long time after keying in the User-ID. There is a big delay in getting to the password prompt. But once the password is keyed in,it goes through in a second. The servers in which i am facing this issue is an NIS client. But i am facing this... (7 Replies)
Discussion started by: Hari_Ganesh
7 Replies

5. Solaris

NIS performance slowness

Hi I have a Solaris 10 NIS server and more than 250 NIS clients out of these there are 5 main application servers, and whenever there is any compilation happens on any of the application servers (which are acting as NIS clients) entire NIS performance will come down.Can some one help me to fix... (5 Replies)
Discussion started by: nithnara
5 Replies

6. Solaris

ssh slowness

Hi admins, After changing the ip address(temperorily) ssh to that server is very slow(exactly 25 sec).But from this new ip i can ssh to other servers without any delay problem. debug1: match: Sun_SSH_1.1.1 pat Sun_SSH_1.1.1* debug1: Enabling compatibility mode for protocol 2.0 debug1:... (2 Replies)
Discussion started by: newsol
2 Replies

7. Solaris

Java Application slowness with Xmanager

Hi! I have a m3000 server with solaris 10. Clients connecting to server using Xmanager. But when they open a Java based application its very slow and some times hanging. But when I tried with VNC it works fine. Is this a BUG in Xmanager? Or Is there any method to solve this? Thanks, Charith (3 Replies)
Discussion started by: charith.upendra
3 Replies

8. Solaris

Login slowness from LDOM to ZONE

Need assitance in troubleshooting steps . Below is the issue I have LDOM which has 4 zones on it . One zone logging into the server takes 13sec where as other zones are quick . Troubleshooting steps which I did - Checked /var/tmp . Not many files - We have LDAP but thought that wouldnt be... (7 Replies)
Discussion started by: ajayram_arya
7 Replies

9. AIX

Slowness issue

Oracle database is facing slowness issues frequently on AIX server. So can anybody suggest how to fix these issues from OS end? Do we need to tune any parameter in AIX to resolve this issue? Please post in an adequate forum! (1 Reply)
Discussion started by: vithal
1 Replies
as(1)																	     as(1)

NAME
as - assembler SYNOPSIS
SPARC as [-b] [-i] [ -K {pic,PIC}] [-L] [-m] [-n] [-o outfile] [-P] [-Dname] [-Dname=def] [-Ipath] [-Uname...] [-q] [-Qy | n] [-s] [ -S [a | b | c | l | A | B | C | L] ] [-T] [-V] [-xarch=v7 | -xarch=v8 | -xarch=v8a | -xarch=v8plus | -xarch=v8plusa | -xarch=v8plusb | -xarch=v9 | -xarch=v9a | -xarch=v9b ] [-xF] [-Y dirname] filename... as [-b] [-i] [ -K PIC] [-L] [-m] [-n] [-o outfile] [-P] [-Dname] [-Dname=def] [-Ipath] [-Uname...] [-Qy | n] [-s] [ -S [a | b | c | l | A | B | C | L] ] [-T] [-V] [ -xarch=generic64 | -xarch=amd64] [-Y dirname] [-xmodel= [ SMALL | KERNEL ]] filename... The as command creates object files from assembly language source files. Common Options The following flags are common to both SPARC and . They may be specified in any order: -b Generates extra symbol table information. -i Ignore line number information from preprocessor. -K pic | PIC Generates position-independent code. -L Saves all symbols, including temporary labels that are normally discarded to save space, in the ELF symbol table. -m Runs the m4(1) macro processor on the input to the assembler. -n Suppresses all the warnings while assembling. -o outfile Puts the output of the assembly in outfile. By default, the output file name is formed by removing the .s suffix, if there is one, from the input file name and appending a .o suffix. -P Runs cpp(1), the C preprocessor, on the files being assembled. The preprocessor is run separately on each input file, not on their con- catenation. The preprocessor output is passed to the assembler. -Dname -Dname=def When the -P option is in effect, these options are passed to the cpp(1) preprocessor without interpretation by the as command; other- wise, they are ignored. -Ipath When the -P option is in effect, this option is passed to the cpp(1) preprocessor without interpretation by the as command; otherwise, it is ignored. -Uname When the -P option is in effect, this option is passed to the cpp(1) preprocessor without interpretation by the as command; otherwise, it is ignored. -Qy | n If y is specified, this option produces the "assembler version" information in the comment section of the output object file. If n is specified, the information is suppressed. -s Places all stabs in the .stabs section. By default, stabs are placed in stabs.excl sections, which are stripped out by the static linker, ld(1), during final execution. When the -s option is used, stabs remain in the final executable because .stab sections are not stripped by the static linker. -S[a|b|c|l|A|B|C|L] Produces a disassembly of the emitted code to the standard output. Adding each of the following characters to the -S option produces: a disassembling with address b disassembling with ".bof" c disassembling with comments l disassembling with line numbers Capital letters turn the switch off for the corresponding option. -T This is a migration option for 4.x assembly files to be assembled on 5.x systems. With this option, the symbol names in 4.x assembly files will be interpreted as 5.x symbol names. -V Writes the version number of the assembler being run on the standard error output. -xF Allows function reordering by the Performance Analyzer. If you compile with the -xF option, and then run the Performance Analyzer, you can generate a map file that shows an optimized order for the functions. The subsequent link to build the executable file can be directed to use that map file by using the linker -M mapfile option. It places each function from the executable file into a separate section. -Y dirname Specify directory m4 and/or cm4def. Options for SPARC only -q Performs a quick assembly. When the -q option is used, many error checks are not performed. Note: This option disables many error checks. Use of this option to assemble handwritten assembly language is not recommended. -xarch=v7 This option instructs the assembler to accept instructions defined in the SPARC version 7 (V7) architecture. The resulting object code is in ELF format. -xarch=v8 This option instructs the assembler to accept instructions defined in the SPARC-V8 architecture, less the quad-precision floating-point instructions. The resulting object code is in ELF format. -xarch=v8a This option instructs the assembler to accept instructions defined in the SPARC-V8 architecture, less the quad-precision floating-point instructions and less the fsmuld instruction. The resulting object code is in ELF format. This is the default choice of the -xarch=options. -xarch=v8plus This option instructs the assembler to accept instructions defined in the SPARC-V9 architecture, less the quad-precision floating-point instructions. The resulting object code is in ELF format. It will not execute on a Solaris V8 system (a machine with a V8 processor). It will execute on a Solaris V8+ system. This combination is a SPARC 64-bit processor and a 32-bit OS. -xarch=v8plusa This option instructs the assembler to accept instructions defined in the SPARC-V9 architecture, less the quad-precision floating-point instructions, plus the instructions in the Visual Instruction Set (VIS). The resulting object code is in V8+ ELF format. It will not execute on a Solaris V8 system (a machine with a V8 processor). It will execute on a Solaris V8+ system -xarch=v8plusb This option enables the assembler to accept instructions defined in the SPARC-V9 architecture, plus the instructions in the Visual Instruction Set (VIS), with UltraSPARC-III extensions. The resulting object code is in V8+ ELF32 format. It executes only on an Ultra- SPARC-III processor. -xarch=v9 This option limits the instruction set to the SPARC-V9 architecture. The resulting .o object files are in 64-bit ELF format and can only be linked with other object files in the same format. The resulting executable can only be run on a 64-bit SPARC processor running 64-bit Solaris with the 64-bit kernel. -xarch=v9a This option limits the instruction set to the SPARC-V9 architecture, adding the Visual Instruction Set (VIS) and extensions specific to UltraSPARC processors. The resulting .o object files are in 64-bit ELF format and can only be linked with other object files in the same format. The resulting executable can only be run on a 64-bit SPARC processor running 64-bit Solaris with the 64-bit kernel. -xarch=v9b This option enables the assembler to accept instructions defined in the SPARC-V9 architecture, plus the Visual Instruction Set (VIS), with UltraSPARC-III extensions. The resulting .o object files are in ELF64 format and can only be linked with other V9 object files in the same format. The resulting executable can only be run on a 64-bit UltraSPARC-III pro cessor running a 64-bit Solaris operating environment with the 64-bit kernel. Options for Only --xarch=generic64 Limits the instruction set to AMD64. The resulting object code is in 64-bit ELF format. --xarch=amd64 Limits the instruction set to AMD64. The resulting object code is in 64-bit ELF format. -xmodel=[SMALL | KERNEL] For AMD64 only, generate R_X86_64_32S relocatable type for static data access under KERNEL. Otherwise, generate R_X86_64_32 under SMALL. SMALL is the default. The following operand is supported: filename Assembly language source file TMPDIR The as command normally creates temporary files in the directory /tmp. Another directory may be specified by setting the environment variable TMPDIR to the chosen directory. (If TMPDIR is not a valid directory, then as will use /tmp). By default, as creates its temporary files in /tmp. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsprot | +-----------------------------+-----------------------------+ cc(1B), cpp(1),ld(1), m4(1), nm(1), strip(1), tmpnam(3C), a.out(4), attributes(5) dbx and analyzer manual pages available with Sun Studio documentation. If the -m option, which invokes the m4(1) macro processor, is used, keywords for m4 cannot be used as symbols (variables, functions, labels) in the input file, since m4 cannot determine which keywords are assembler symbols and which keywords are real m4 macros. Whenever possible, access the assembler through a compilation system interface program such as cc(1B). All undefined symbols are treated as global. 16 Sep 2005 as(1)
All times are GMT -4. The time now is 07:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy