Sponsored Content
Operating Systems Solaris Reboot, System is Frozen at setting interface for multicast HELP Post 302097956 by eyukins on Wednesday 29th of November 2006 08:26:07 PM
Old 11-29-2006
Your shot in the dark was not far off. Turns out there is a Linux server that it's mounted to, or somehow connected to for backup of data. That machine was down suffering from a bad power cord, making it unreachable.

Thanks for your reply.
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Intermitent System Reboot's

Hi all, Just started holidays (ya!) and Murphy's Law has kicked in already (doh!). I'm looking after (when at work) two SCO 5.0.5 Systems running on Netfinity 5500 Servers (Model # 8662-3RY). Every once and a while the production server just reboot's itself. There is no mention of a cause... (8 Replies)
Discussion started by: Cameron
8 Replies

2. Programming

Joining multicast group on IPADDR_ANY - which interface?

Hello all, I have the following question: if you join a multicast group (with setsockopt() and IP_ADD_MEMBERSHIP) and specify INADDR_ANY as network interface to join on, the kernel is supposed to choose which interface to use (if there are multiple network interfaces, of course). Does... (2 Replies)
Discussion started by: AlexI
2 Replies

3. UNIX for Dummies Questions & Answers

System Reboot Dates

Hi, Can someone advise me how to find the last system rebooted date(s)? Thanx N Regards, Hush (2 Replies)
Discussion started by: hush
2 Replies

4. AIX

IP setting changes after server reboot

I've recently changed my gateway setting using SMIT. Everything went fine except that the gateway setting kept reverting back to the old one everytime I reboot the server. I'm on AIX 5.2 running p-Series. Thanks for any info. (3 Replies)
Discussion started by: dereklow
3 Replies

5. Solaris

system self reboot

dear all, I have 2 T2000 with solaris 10 and oracle 10g installed on it. these two servers are rebooted by itself. could anyone help me investigate the cause. the message log is attached thanx, (3 Replies)
Discussion started by: fsmadi
3 Replies

6. Solaris

System Reboot Log

Hello Everyone , I am a new member to this forum and came to know about this from so many of my friends . I face one issue last day when suddenly the system got rebooted ( But don,t know why ) . Can someone please help me in investigating this issue as to why the system got rebooted and who... (4 Replies)
Discussion started by: gera_sachin125
4 Replies

7. Linux

xinetd @system reboot

Hi, Once again I came to get rescued in a situation where one of my workstations has this ierd thing that "xinetd" won't start at reboot or shutdown. I have done the follwoing but no change in results. chkconfig --list xinetd xinetd 0:off 1:off 2:on 3:on 4:on 5:on ... (2 Replies)
Discussion started by: harjitsingh
2 Replies

8. Solaris

system reboot procedure

Hi all, i want to know the procedure reboot the server through console if the system is completely down.Please help me if anybody knows this. I would really thanfull to all. regards Krishna Murthy (1 Reply)
Discussion started by: murthy76
1 Replies

9. UNIX for Dummies Questions & Answers

system is frozen

hi there. new problem for me!!! i have been using a Sabayon Linux 3.5 distribution and yesterday when i turned the system on it stopped responding, i mean it freeazed. i was listening to music on Audacious and suddenly the system is ice cold...baby. what to do. Since i've tried 'reiserfsck' the... (0 Replies)
Discussion started by: dvas83
0 Replies
cord(1) 						      General Commands Manual							   cord(1)

Name
       cord - rearranges procedures in an executable to facilitate better cache mapping.

Syntax
       cord [ -c cachesize ] [ -f ] [ -o outfile ] [ -p maxphases ] [ -v ] obj reorder

Description
       The  command rearranges procedures in an executable object to maximize efficiency in a machine's cache. By rearranging the procedures prop-
       erly, the instruction cache miss rate is reduced. The command does not attempt to determine the correct ordering, but is  given	a  reorder
       file containing the desired procedure order. The reorder file is generated by the program which in turn generates a reorder file from a set
       of profile feedback files (see ).

       Processed lines in the reorder file are called procedure lines.	Each procedure line must be on a separate source line. Each procedure line
       must  contain  the source name of the file, followed by a blank followed by a qualified procedure name (nested procedures need to be quali-
       fied x.y where x is the outer procedure). A newline or blank can follow the procedure name:
       foo.c bar >>i ignore this stuff<<

       Lines beginning with a pound sign (#) are comments.  Lines beginning with a dollar sign ($) are considered directive lines. The only direc-
       tive  currently	understood  is	$phase.  This directive will consider the rest of the file (until the end of file or next $phase) as a new
       phase of the program and will order the procedures accordingly. Procedures may appear in more than one phase, resulting in  more  than  one
       copy  of  it  in  the final binary.  The command will try to relocate references to a procedure to a copy in the requesting phase's list of
       procedures first and then a random copy if one is not found.

       You should use the -cord option to a compiler driver like rather than execute cord directly. Options to	can  be  specified  with  -Wz,cor-
       darg0,cordarg1,....   If  you have to run manually, you should run it once with the driver using the -v flag on a simple program to see the
       exact passes and their arguments involved in using

       The obj argument is an executable object with its relocation information intact. This can be achieved by passing the -r -z  -d  options	to
       the  linker, The -r linker option maintains relocation information in the object, but will not make it a ZMAGIC file (hence -z) nor will it
       allocate common variables (hence -d) as it would without the option.

Options
       -c cachesize   Specify the cachesize of the machine you want to execute on in bytes. This only affects the  -f  option.	If  not  specified
		      65536 is used.

       -f	      Flip  the  first cachepage size procedures. The assumption when was written was that procedures would be reordered by proce-
		      dure density (cycles/byte). This option ensures that the densest part of each page following the first cachepage would  con-
		      flict with least dense part of the first cachepage.

       -o outputfile  specifies the output file. If not specified, a.out is used.

       -p phasemax    Specifies the maximum number of phases allowed. The default is 20.

       -v	      Prints  verbose  information. This includes listing those procedures considered part of other procedures and cannot be rear-
		      ranged (these are basically assembler procedures that may contain relative branches to other procedures rather than relocat-
		      able ones). The listing also list those procedures in the flipped area (if any) and a mapping of old location to new.

Restrictions
       Since works from an input list of procedures generated from profile output, the resulting binary is data dependent.  In other words, it may
       only perform well on the same input data that generated the profile information and may perform worse than the  original  binary  on  other
       data.  Furthermore, if the hot areas in the cache don't fit well into one cachepage, performance can degrade.

See Also
       cc(1), ftoc(1), ld(1), prof(1)

								       RISC								   cord(1)
All times are GMT -4. The time now is 07:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy