03-09-2013
Your output shows its already up and running and you told ip is pingable then what else you are looking for?
If still any problem, just unplumb and plumb again and do all the configuration again.
This User Gave Thanks to prashant2507198 For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi
I'm having a big trouble running a configuration tool (ftamtool) which uses xview on sunos 5.8, it refuses to start and says: XView error: could not load font 'FONT_FAMILY_SANS_SERIF...
How to force the program to use installed fonts and where are fonts installed available to use ?
... (0 Replies)
Discussion started by: andryk
0 Replies
2. IP Networking
I'm trying to plumb a new interface bge1 on my machine:
root@obms2-com-indianapolis-in:/root# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet... (3 Replies)
Discussion started by: R37ribution
3 Replies
3. Shell Programming and Scripting
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies
4. Programming
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies
5. Solaris
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (2 Replies)
Discussion started by: rgilan01
2 Replies
6. Solaris
Hi all,
I encounter some problem with my e1000g interface running on sol 10. I can't permanently change the auto-nego to disable, if i use ndd commands, it will only stay until the next reboot.
But i can't change the link speed either is set to /etc/init.d/nddconfig or using ndd commands.
... (1 Reply)
Discussion started by: mailbox80
1 Replies
7. Solaris
hi frineds
in sunfire 6800 server for one domain when ever i am giving ifconfig -a interface names like hme0,hme1.......are not showing.Actually in the server hme0,hme1,qfe are showing .when i was tried with the cat /etc/path_to_intstshowing tphysical interfcace names .
after giving the... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
8. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
9. Solaris
on both of my T2000 I am seeing same values of 100Mbps for e1000g0 ethernet port.
i know all four ethernet ports on T2000 are gigabit ports so why is my first link showing as 100Mbps and how can i correct it?
# dladm show-dev
e1000g0 link: up speed: 100 Mbps ... (1 Reply)
Discussion started by: aliyesami
1 Replies
10. Solaris
Hi All,
Please let me know the step by step process to set the e1000g0 interface speed to 1000mbps with full duplex from 100fdx and how to disable the auto negotiation with switch?.
Thanks and Regards,
Ganesh. (7 Replies)
Discussion started by: gsrungav
7 Replies
LEARN ABOUT DEBIAN
torrus_schedulerinfo
TORRUS_SCHEDULERINFO(8) torrus TORRUS_SCHEDULERINFO(8)
NAME
schedulerinfo - Displays extended scheduler tasks information.
SYNOPSIS
torrus schedulerinfo --tree=TREENAME [options...]
DESCRIPTION
This utility displays the extended scheduler tasks information for tree TREENAME on standard output. This might be useful for scheduler
planning and analysis.
OPTIONS
--config
Reports scheduler's configuration. The values are explained below.
Total collector/monitor leaves: N
Total number of datasources being processed by collector or monitor daemon.
Scheduled leaves by type
Torrus supports arbitrary number of collector types, and this report shows how many datasources belong to every type. Currently
the monitor leaves are not divided into types.
Least common period: N seconds
The report below shows how the tasks are distributed across the time line, and the least common period shows the period of this
time line.
Tasks execution timeline
This report tells which task and how many datasources are involved in each task startup event, and how these events are
dispersed across the time. The column Interval shows the time interval from each task execution event to the next event on the
timeline.
--runtime
Reports scheduler's runtime statistics, such as running cycle times, late starts etc. The meaning of the output values is as follows.
Values that have zero values are usually not printed.
Task: Name, Period: N seconds, Offset: M seconds
Each scheduler task is characterized by its name (usually Collector or Monitor), period, and timeoffset. Fore example, if
period is set to 300 seconds, and offset is 14 seconds, then the task would be executed at 00:00:14, 00:05:14, 00:10:14, and so
on for every hour in a day.
N running cycles passed
How many times the task was executed since last reset. The counter is normally reset after torrus_compilexml(8) successfully
compiles the configuration.
N late starts
How many times the task has started with a delay from its normal schedule.
N too long runs
How many times the task execution time was longer than its period.
N overrun periods
How many periods have been missed because of too long executions.
N missed periods
How many periods were missed because of any reason (such as other tasks delaying).
Min, Max, Average, Exp Average
The time values are displayed in four columns: Mimimum, Maximum and Average values since last reset, and Exponential decay
value, which may be interpreted as the average for last several values. With defaults defined in torrus-config.pl, 95% of the
average is calculated from last 3 values.
Running Time
How long the task executes each period.
Late Start
How long the task start was delayed.
Too Long
How much time the too long run took.
RRD Queue
In a multithreaded environment, the RRD files are writen in a background thread. This value shows the length of the RRD update
queue at the beginning of each update cycle.
--help
Displays a help message.
SEE ALSO
torrus(8), torrus_compilexml(8)
NOTES
See more documentation at Torrus home page: http://torrus.org
AUTHOR
Stanislav Sinyagin <ssinyagin@yahoo.com>
torrus 2.03 2013-07-26 TORRUS_SCHEDULERINFO(8)