Why do these 2 methods result in different outcomes? Post: 303021974

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

file transfer Methods

I would like to write shell script to transfer some ASCII files from HPUX server to Linux server or vice-versa. What options I have for file transfer Methods. 1) FTP 2) rcp 3) HTTP 4)Whatelse?

2. What is on Your Mind?

Predict Future Outcomes in Our Event Prediction Market

Folks love to predict the future, so we have enabled predicting the future for members. So, please enjoy placing your Forum Bits predicting future outcomes in our new Event Prediction Market. Current events you can predict include science, technology, M&A and other global events: Oracle...

3. Shell Programming and Scripting

Methods to SSH (Perl)...

Can anyone break down the different methods of using SSH in perl? I'm currently using Net::SSH::Expect, which allows me to login to a machine and execute multiple commands without having to ssh again. This feature of holding the session works well for me, but it's slow. If I set timeouts to 4...

4. UNIX for Advanced & Expert Users

yum provides methods

What is the difference between these yum provides and whatprovides methods? I know provides and whatprovides give the same results, but different methods of */ and \* give different results. Also whether you put */ and \* in front of the string or behind the string give different results. I have...

5. Solaris

Unix learning methods

I have recently completed Solaris 10 System Administration book by Bill Calkins. Now I want to learn more about UNIX. I have tried to research online but there is too much information and I am sort of overwhelmed and don't know where to start. Can anybody give some idea on how to pursue my learning...

6. Shell Programming and Scripting

Perl Methods Calling

Hello I am on my way to improve my wonderful Perl skills, I got an issue which I want to share with you all. I have a Perl module which looks like package Cocoa; require Exporter; @ISA = qw(Exporter); my $a=''; my $b=''; my $c=''; sub new { my $this = shift; # Create...

7. Shell Programming and Scripting

How to compare the current result with previous line result.?

Hi Gurus, I have requirement to compare current result with previous reuslt. The sample case is below. 1 job1 1 1 job2 2 1 job3 3 2 job_a1 1 2 job_a2 2 2 job_a3 3 3 job_b1 1 3 job_b2 2 for above sample file, GID is group ID, for input line, the job run...

8. Linux

Help with PAM Logging methods.

Hi Folks, Would like to understand if there exists any method to write the logs for LDAP authenticated users and Local Users separately in two different files. If not, then do I distinguish whether the user is LDAP or local without looking at passwd. Bye the way, I am trying this weird...

9. UNIX for Beginners Questions & Answers

One Line Command how to use pipe statements to execute and comment on multiple possible outcomes

Hello Forum, I'm looking to expand the following command: INACTIVE_KERNELS=$(python -mplatform | grep -qi red && rpm -qa | grep '^kernel-' |grep -vE `uname -r` | paste -sd \; || echo "Not Red Hat Server") Currently this command will check if my server is RedHat server using the grep -qi...

LEARN ABOUT FREEBSD

timecounters

TIMECOUNTERS(4) 					   BSD Kernel Interfaces Manual 					   TIMECOUNTERS(4)

NAME

     timecounters -- kernel time counters subsystem

SYNOPSIS

     The kernel uses several types of time-related devices, such as: real time clocks, time counters and event timers.	Real time clocks are
     responsible for tracking real world time, mostly when the system is down.	Time counters are responsible for tracking purposes, when the sys-
     tem is running.  Event timers are responsible for generating interrupts at a specified time or periodically, to run different time-based
     events.  This page is about the second.

DESCRIPTION

     Time counters are the lowest level of time tracking in the kernel.  They provide monotonically increasing timestamps with known width and
     update frequency.	They can overflow, drift, etc and so in raw form can be used only in very limited performance-critical places like the
     process scheduler.

     More usable time is created by scaling the values read from the selected time counter and combining it with some offset, regularly updated by
     tc_windup() on hardclock() invocation.

     Different platforms provide different kinds of timer hardware.  The goal of the time counters subsystem is to provide a unified way to access
     that hardware.

     Each driver implementing time counters registers them with the subsystem.	It is possible to see the list of present time counters, via the
     kern.timecounter sysctl(8) variable:

     kern.timecounter.choice: TSC-low(-100) HPET(950) i8254(0) ACPI-fast(900) dummy(-1000000)
     kern.timecounter.tc.ACPI-fast.mask: 16777215
     kern.timecounter.tc.ACPI-fast.counter: 13467909
     kern.timecounter.tc.ACPI-fast.frequency: 3579545
     kern.timecounter.tc.ACPI-fast.quality: 900
     kern.timecounter.tc.i8254.mask: 65535
     kern.timecounter.tc.i8254.counter: 62692
     kern.timecounter.tc.i8254.frequency: 1193182
     kern.timecounter.tc.i8254.quality: 0
     kern.timecounter.tc.HPET.mask: 4294967295
     kern.timecounter.tc.HPET.counter: 3013495652
     kern.timecounter.tc.HPET.frequency: 14318180
     kern.timecounter.tc.HPET.quality: 950
     kern.timecounter.tc.TSC-low.mask: 4294967295
     kern.timecounter.tc.TSC-low.counter: 4067509463
     kern.timecounter.tc.TSC-low.frequency: 11458556
     kern.timecounter.tc.TSC-low.quality: -100

     The output nodes are defined as follows:

     kern.timecounter.tc.X.mask is a bitmask, defining valid counter bits,

     kern.timecounter.tc.X.counter is a present counter value,

     kern.timecounter.tc.X.frequency is a counter update frequency,

     kern.timecounter.tc.X.quality is an integral value, defining the quality of this time counter compared to others.	A negative value means
     this time counter is broken and should not be used.

     The time management code of the kernel chooses one time counter from that list.  The current choice can be read and affected via the
     kern.timecounter.hardware tunable/sysctl.

SEE ALSO

     attimer(4), eventtimers(4), ffclock(4), hpet(4)

BSD
								  April 12, 2014							       BSD