Olha no código fonte que tem uma discussão sobre como é medido. Inclusive
sobre questão do swap entrar ou não na conta do load average.
./helio
On Thu, Jun 11, 2020, 13:42 Paulo wrote:
> Pessoal,
>
> Alguem tem alguma documentação que explique melhor como é medido o Uptime.
>
&
Pessoal,
Alguem tem alguma documentação que explique melhor como é medido o Uptime.
Pois parece que é uma ciência de foguetes, rss
Att,
Paulo Correia
Linkedin: http://br.linkedin.com/pub/paulo-correia/30/73a/604
<http://br.linkedin.com/pub/paulo-correia/30/73a/604>
GitHub:
> This function is made for the formatting of *dates*, not *time intervals.
>
> That would mean that you might get even funnier results if your uptime
> is more than (around) 30-31 days.
I did understand. For now my chromebook uptime is over 30 days, thanks!
Sincerely, Byung-Hee.
--
In Article <17430759904711630...@scdbackup.webframe.org>,
"Thomas Schmitt" writes:
> [...]
> (You should better compute the time interval days from the seconds
> difference. %d will probably rollover at 31.)
Thank you for good point, indeed;;;
Sincerely, Byung-Hee.
--
Hi,
Byung-Hee wrote:
> uptime = Time.at(uptime_data).utc.strftime("%d days %H:%M")
> Ruby: 28 days 09:23 (Tue Sep 26 15:19:58 +0900 2017)
> Bash: 00:43:33 up 27 days, 9:23, 0 users, load average: 0.01, 0.10, 0.21
Google sent me to
https://apidock.com/ruby/DateTime
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 24, 2017 at 12:50:03AM +0900, Byung-Hee HWANG (황병희, 黃炳熙) wrote:
> #+BEGIN_SRC ruby
> require "date"
>
> uptime_data = IO.read('/proc/uptime').split[0].to_i
> sboot = Time.now - uptime_data
>
> if upti
#+BEGIN_SRC ruby
require "date"
uptime_data = IO.read('/proc/uptime').split[0].to_i
sboot = Time.now - uptime_data
if uptime_data >= 86400
uptime = Time.at(uptime_data).utc.strftime("%d days %H:%M")
else
uptime = Time.at(uptime_data).utc.strftime("%
Having a long uptime is fine if you run a system not on the Internet.
If you are on the Internet, then a long uptime is like being proud of not
having read
a newspaper for that many days.
Uptime used to be significant over a decade ago, when some systems were
recommended to reboot periodically
I have a box running Etch that hasn't been rebooted in 1,589 days:
irp:~# uptime
12:09:06 up 1589 days, 18:23, 1 user, load average: 0.00, 0.01, 0.03
irp:~#
I swear this is real. :-)
On Sun, Apr 21, 2013 at 6:32 PM, Vincent Lefevre vinc...@vinc17.net wrote:
On 2013-04-20 19:24:00 -0600
On Wed, Apr 17, 2013 at 12:57:28PM +0100, Jonathan Dowland wrote:
My laptop is at 112 days. Of course it hasn't actually been on all
of those days.
My cat managed to trigger an emergency read-only remount of all
filesystems via sysrq, so I took this as an opportunity to update
the kernel and
I have a box at work that has an uptime of:
12:32:00 up 1971 days, 18:32, 1 user, load average: 1.00, 1.00, 1.00
On Fri, Apr 26, 2013 at 12:10 PM, David Parker dpar...@utica.edu wrote:
I have a box running Etch that hasn't been rebooted in 1,589 days:
irp:~# uptime
12:09:06 up 1589
On 2013-04-20 19:24:00 -0600, Bob Proulx wrote:
Vincent Lefevre wrote:
That's theory. In practice, old machines get no longer supported...
I submitted a bug report (and a patch), but AFAIK the bug has never
been fixed. I upgraded everything except the kernel, without being
sure I could
On 4/19/2013 8:59 AM, Jonathan Dowland wrote:
I'll accept that you intended to use the phrase in the meaning you suggest,
here, in the spirit of good faith, but I'm sure you are fully aware that
the phrase is more widely known and used in a different way which is
objectionable. It's therefore
On 4/19/2013 9:09 AM, Jonathan Dowland wrote:
On Thu, Apr 18, 2013 at 10:31:35PM -0500, Stan Hoeppner wrote:
Second, your methodology doesn't scale. For large scale operations
installing new kernel patches every few weeks simply isn't financially
feasible/responsible. Even a junior admin's
On 2013-04-18 10:56:53 -0600, Bob Proulx wrote:
I don't think uptime challenges are useful. It makes people want to
do something that they shouldn't want to do. When kernel security
upgrades come along just install them and reboot.
That's theory. In practice, old machines get no longer
On Wed, Apr 17, 2013 at 06:24:33PM +0200, Jochen Spieker wrote:
Lars Noodén:
Oracle hasn't been the best steward for the other FOSS projects […]
You are hereby given the Understatement of the Year Award!
And it's only April!! :-D
--
If you're not careful, the newspapers will have you
On Thu, Apr 18, 2013 at 08:18:15PM +0100, Kevin Chadwick wrote:
On the humor side though I rememeber a story about a guy who moved his
apartment. His machine was on a UPS. He determined a way to borrow a
second UPS and daisy chain them for more uptime and then drove like a
madman halfway
On Fri, Apr 19, 2013 at 09:45:21AM +0200, Helmut Wollmersdorfer wrote:
In 1992 I worked late after usual office hours on my laptop (an IBM
386) connected to the power supply and battery removed (to save
lifetime of the battery).
Then the cleaning woman stepped in and asked: May I vacuum
On Sat, Apr 20, 2013 at 01:00:01AM -0500, Stan Hoeppner wrote:
From now on I *will* use male genital analogies, using phallus,
phalli, and phallic, the academically correct words for describing
the sociological phenomenon. Then you can sit there and squirm in your
chair screaming loudly, as
On Wed, Apr 17, 2013 at 09:22:18PM +0100, Kevin Chadwick wrote:
OpenBSD has only had something like two holes in over a decade which is
nice for uptime.
Let's not get carried away here. I was under the impression that openbsd
was one of the best things since sliced bread ... then I read
OpenBSD has only had something like two holes in over a decade
which is nice for uptime.
Let's not get carried away here. I was under the impression that
openbsd was one of the best things since sliced bread ... then I read
this:
http://allthatiswrong.wordpress.com/2010/01/20
Chris Bannister wrote:
Over here in New Zealand, power switch up equals power off.
I noticed that behavior when visiting your beautiful country! But I
figured that since it was on the south side of the planet that the
switches pointed toward the south pole for off and toward the north
pole for
Vincent Lefevre wrote:
Bob Proulx wrote:
I don't think uptime challenges are useful. It makes people want to
do something that they shouldn't want to do. When kernel security
upgrades come along just install them and reboot.
That's theory. In practice, old machines get no longer
On Thu, Apr 18, 2013 at 10:31:35PM -0500, Stan Hoeppner wrote:
This isn't a manhood measurement contest.
Let's avoid alienating some debian-user readers with such language.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Am 18.04.2013 um 20:33 schrieb Bob Proulx:
Kevin Chadwick wrote:
Well I wouldn't go that far but I have taken the insert of a matchbox
cut a slot in it and stuck it over the power button so that when
reaching round the back there is no way of holding it down by
accident.
Protecting the
The security related flaws are typically in
subsystems that are not part of a minimalist kernel.
A reboot is an attackers best friend and potentially an attackers
enemy too.
However whilst your practice is right. I hope you are reviewing all bugs
as the kernel devs simply label them as bugs
On 4/19/2013 1:56 AM, Jonathan Dowland wrote:
On Thu, Apr 18, 2013 at 10:31:35PM -0500, Stan Hoeppner wrote:
This isn't a manhood measurement contest.
Let's avoid alienating some debian-user readers with such language.
Instead let's get you straightened out.
You obviously misread my
On 4/19/13, Jonathan Dowland j...@debian.org wrote:
On Thu, Apr 18, 2013 at 10:31:35PM -0500, Stan Hoeppner wrote:
This isn't a manhood measurement contest.
Let's avoid alienating some debian-user readers with such language.
Oh, c'mon! Grow some ovaries already...
:)
--
To UNSUBSCRIBE,
On Fri, Apr 19, 2013 at 04:57:50AM -0500, Stan Hoeppner wrote:
You obviously misread my statement, apparently because your mind is in
the gutter. It had nothing to do with male sexual organ size, as you
have obviously and incorrectly assumed. If your beef was instead
strictly with my use of
On Thu, Apr 18, 2013 at 10:31:35PM -0500, Stan Hoeppner wrote:
Second, your methodology doesn't scale. For large scale operations
installing new kernel patches every few weeks simply isn't financially
feasible/responsible. Even a junior admin's salary is better spent on
things other than
Whatever I see in all your comments is this:
Most of the people show a big uptime. 100 days, 400 days, 500 days, even more
than a 1000 days! So many people do this. It proves, how stable a good system
can be and it also shows the great work of the developers.
If I compare it to other
On Apr 19, 2013 8:11 PM, Hans-J. Ullrich hans.ullr...@loop.de wrote:
Whatever I see in all your comments is this:
Most of the people show a big uptime. 100 days, 400 days, 500 days, even
more
than a 1000 days! So many people do this. It proves, how stable a good
system
can be and it also
On 4/19/13, Zenaan Harkness z...@freedbms.net wrote:
On 4/19/13, Jonathan Dowland j...@debian.org wrote:
On Thu, Apr 18, 2013 at 10:31:35PM -0500, Stan Hoeppner wrote:
This isn't a manhood measurement contest.
Let's avoid alienating some debian-user readers with such language.
Oh, c'mon!
like two holes in over a decade which is
nice for uptime.
If i am not mistaken, The OpenBSD Team recommends a clean installation
every 6 month.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive
On Thu, 18 Apr 2013, agroconsultor0 wrote:
On 04/17/2013 01:22 PM, Kevin Chadwick wrote:
[snip]
OpenBSD has only had something like two holes in over a decade which is
nice for uptime.
If i am not mistaken, The OpenBSD Team recommends a clean installation every 6
month.
For users
On Wed, Apr 17, 2013 at 10:43:27PM +0200, Hans-J. Ullrich wrote:
It is interesting. Whenever I someone is telling of big uptime, the arguiment
is:
[cut]
2. Security issues
But a kernel can stay very, verry long time. On machines, where you do not
change hard or software (i.e. new
On 2013-04-17 17:22:32 +1030, John Elliot wrote:
$ uptime 16:51:12 up 1136 days, 17:01, 1 user, load average: 0.22, 0.12,
0.08
I got on 2012-11-01:
10:48:16 up 1150 days, 8:00, 1 user, load average: 0.83, 0.69, 0.31
But then there was a disk failure and the machine is no longer
Eduardo M KALINOWSKI wrote:
Not really. uptime reports the amount of time elapsed since the
system was booted, but I've noticed it is not paused for suspend
and hibernation.
Yes:
$ uprecords
# Uptime | System Boot up
On Wed, Apr 17, 2013 at 09:22:18PM +0100, Kevin Chadwick wrote:
OpenBSD has only had something like two holes in over a decade which is
nice for uptime.
Two holes in the default install, which is a very different thing to two
holes in the entire distribution.
--
To UNSUBSCRIBE, email
Darac Marjal wrote at 2013-04-18 04:05 -0500:
On Wed, Apr 17, 2013 at 10:43:27PM +0200, Hans-J. Ullrich wrote:
Security issues, which affect modules, but not the kernel itself, may not
cause
the need of a new kernel. When people lik me and others on this list, are
using a very small
Am Mittwoch, 17. April 2013 schrieb Jonathan Dowland:
My laptop is at 112 days. Of course it hasn't actually been on all
of those days.
Had about 200 days on a hibernating workstation at work.
And its nice in Juni or July to type who and see 18 Apr as login time for
display :0 :)
Ciao,
--
Am Mittwoch, 17. April 2013 schrieb Stan Hoeppner:
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
22:35:31 up 412 days, 10:05, 1 user, load average: 1.18, 0.97, 0.44
mondschein:~ uprecords
# Uptime | System Boot up
Am Donnerstag, 18. April 2013 schrieb Vincent Lefevre:
On 2013-04-17 17:22:32 +1030, John Elliot wrote:
$ uptime 16:51:12 up 1136 days, 17:01, 1 user, load average: 0.22,
0.12, 0.08
I got on 2012-11-01:
10:48:16 up 1150 days, 8:00, 1 user, load average: 0.83, 0.69, 0.31
On Thursday 18 April 2013 14:33:51 green wrote:
Darac Marjal wrote at 2013-04-18 04:05 -0500:
On Wed, Apr 17, 2013 at 10:43:27PM +0200, Hans-J. Ullrich wrote:
Security issues, which affect modules, but not the kernel itself, may
not cause the need of a new kernel. When people lik me and
Martin Steigerwald wrote:
Am Donnerstag, 18. April 2013 schrieb Vincent Lefevre:
On 2013-04-17 17:22:32 +1030, John Elliot wrote:
$ uptime 16:51:12 up 1136 days, 17:01, 1 user, load average: 0.22,
0.12, 0.08
I got on 2012-11-01:
10:48:16 up 1150 days, 8:00, 1 user, load
On Thu, Apr 18, 2013 at 10:56:53AM -0600, Bob Proulx wrote:
I don't think uptime challenges are useful. It makes people want to
do something that they shouldn't want to do. When kernel security
upgrades come along just install them and reboot. Human made
machines of all types have been
OpenBSD has only had something like two holes in over a decade which is
nice for uptime.
Two holes in the default install, which is a very different thing to two
holes in the entire distribution.
It is but you can see the erratas for the whole base system at
openbsd.org/errata.html
On the humor side though I rememeber a story about a guy who moved his
apartment. His machine was on a UPS. He determined a way to borrow a
second UPS and daisy chain them for more uptime and then drove like a
madman halfway to his new place where he had previously scouted and
found
Kevin Chadwick wrote:
Well I wouldn't go that far but I have taken the insert of a matchbox
cut a slot in it and stuck it over the power button so that when
reaching round the back there is no way of holding it down by accident.
Protecting the power switch from accidentally switching off is
://www.openbsd.org/faq/faq5.html#Flavors
So that would tend to limit the uptime.
Regards,
/Lars
Yes and No. Supported (help you in case of problems) certainly as the
man power simply isn't there to back port and all the devs run current.
However things such as firewalls is no problem and even advocated
On 4/18/2013 11:56 AM, Bob Proulx wrote:
I don't think uptime challenges are useful. It makes people want to
do something that they shouldn't want to do.
Uptime is about continuous availability and reliability of
infrastructure, systems, and software, with least disruption to users
On Tue, 2013-04-16 at 22:59 -0500, Stan Hoeppner wrote:
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
22:35:31 up 412 days, 10:05, 1 user, load average: 1.18, 0.97, 0.44
So you are over a year behind in installing security updates for the
kernel. (I know, if your
Am Mittwoch, 17. April 2013 schrieb Tixy:
On Tue, 2013-04-16 at 22:59 -0500, Stan Hoeppner wrote:
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
22:35:31 up 412 days, 10:05, 1 user, load average: 1.18, 0.97, 0.44
So you are over a year behind in installing
$ uptime 16:51:12 up 1136 days, 17:01, 1 user, load average: 0.22, 0.12, 0.08
From: hans.ullr...@loop.de
To: debian-user@lists.debian.org
Subject: Re: what's your Debian uptime?
Date: Wed, 17 Apr 2013 07:58:31 +0200
Am Mittwoch, 17. April 2013 schrieb Stan Hoeppner:
Linux greer 3.2.6 #1 SMP
On 4/17/2013 1:10 AM, Hans-J. Ullrich wrote:
Am Mittwoch, 17. April 2013 schrieb Tixy:
On Tue, 2013-04-16 at 22:59 -0500, Stan Hoeppner wrote:
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
22:35:31 up 412 days, 10:05, 1 user, load average: 1.18, 0.97, 0.44
So you
Hello hans,
Am Mittwoch, 17. April 2013 schrieb Stan Hoeppner:
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
22:35:31 up 412 days, 10:05, 1 user, load average: 1.18, 0.97, 0.44
Great, but beat this! More than 500 days. At about 650 days uptime I rebooted
My laptop is at 112 days. Of course it hasn't actually been on all
of those days.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130417115728.GE19117@debian
On Wed, 17 Apr 2013 09:59:45 +
Bonno Bloksma b.blok...@tio.nl wrote:
Hello Bonno,
Now I applaud a long uptime but... After a kernel upgrade or a Debian
point release one must or should do a reboot or the updates are not
applied so..
ksplice can be used for security patching the kernel
On 4/17/13 3:12 PM, Brad Rogers wrote:
[snip]
ksplice can be used for security patching the kernel.
[snip]
What's the status of ksplice in Debian? Oracle hasn't been the best
steward for the other FOSS projects and it's been a while since ksplice
was in the news.
Regards,
/Lars
--
To
Lars Noodén:
Oracle hasn't been the best steward for the other FOSS projects […]
You are hereby given the Understatement of the Year Award!
J.
--
I have been manipulated and permanently distorted.
[Agree] [Disagree]
http://www.slowlydownward.com/NODATA/data_enter2.html
On Wed, 17 Apr 2013 17:41:12 +0300 (EEST)
Lars Noodén lars.noo...@gmail.com wrote:
Hello Lars,
What's the status of ksplice in Debian? Oracle hasn't been the best
TBH, I don't know. It's in testing at v0.9.9-4. How that compares with
upstream, I'm not sure, as the Oracle web site seems
On Wed, 17 Apr 2013 18:24:33 +0200
Jochen Spieker m...@well-adjusted.de wrote:
Hello Jochen,
Lars Noodén:
Oracle hasn't been the best steward for the other FOSS projects […]
You are hereby given the Understatement of the Year Award!
:-))
--
Regards _
/ ) The blindingly
On Wed, 17 Apr 2013, Brad Rogers wrote:
On Wed, 17 Apr 2013 17:41:12 +0300 (EEST)
Lars Noodén lars.noo...@gmail.com wrote:
Hello Lars,
What's the status of ksplice in Debian? Oracle hasn't been the best
TBH, I don't know. It's in testing at v0.9.9-4. How that compares with
Jonathan Dowland wrote:
My laptop is at 112 days. Of course it hasn't actually been on all
of those days.
If that is the kernel reported uptime then I think it has been on all
of those reported uptime days. I believe linux only accrues uptime
when it is on and running. Suspended it will pause
On Qua, 17 Abr 2013, Bob Proulx wrote:
I believe linux only accrues uptime
when it is on and running. Suspended it will pause the uptime.
Resumed it will start ticking again.
Not really. uptime reports the amount of time elapsed since the system
was booted, but I've noticed it is not paused
in over a decade which is
nice for uptime.
--
___
'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'
(Doug McIlroy
It is interesting. Whenever I someone is telling of big uptime, the arguiment
is:
Your server can not be secure! You have an old kernel! You MUST install/update
the newest kernel and of course reboot.
But this is not correct. For which reason a new kernel is necessary?
1
is somewhere around 700 days, just short of 2 years.
Then we had a power outage that burned through the UPS and the laptop
battery...
On Wed, Apr 17, 2013 at 4:43 PM, Hans-J. Ullrich hans.ullr...@loop.dewrote:
It is interesting. Whenever I someone is telling of big uptime, the
arguiment
Eduardo M KALINOWSKI wrote:
On Qua, 17 Abr 2013, Bob Proulx wrote:
I believe linux only accrues uptime
when it is on and running. Suspended it will pause the uptime.
Resumed it will start ticking again.
Not really. uptime reports the amount of time elapsed since the system
was booted
On Wed, 17 Apr 2013 04:02:45 -0500
Stan Hoeppner s...@hardwarefreak.com wrote:
On 4/17/2013 1:10 AM, Hans-J. Ullrich wrote:
Am Mittwoch, 17. April 2013 schrieb Tixy:
On Tue, 2013-04-16 at 22:59 -0500, Stan Hoeppner wrote:
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
Linux STRUMMER 2.6.26-2-amd64 #1 SMP Wed Sep 21 03:36:44 UTC 2011 x86_64
GNU/Linux
22:46:24 up 272 days, 14:08, 2 users, load average: 1.00, 1.10, 1.07
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
22:35:31 up 412 days, 10:05, 1 user, load average: 1.18, 0.97, 0.44
--
Stan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am Mittwoch, 17. April 2013 schrieb Stan Hoeppner:
Linux greer 3.2.6 #1 SMP Mon Feb 20 17:05:10 CST 2012 i686 GNU/Linux
22:35:31 up 412 days, 10:05, 1 user, load average: 1.18, 0.97, 0.44
Great, but beat this! More than 500 days. At about 650 days uptime I rebooted
accidentlly.
See
On Sun, Mar 17, 2013 at 03:21:29PM +0100, nicolas.patr...@gmail.com wrote:
Si tu as installé uptimed, lance uprecords à chaque redémarrage et
cumule le dernier.
Même pas besoin :
uprecords |grep up|grep since
up 828 days, 13:57:40 | since Sat Dec 25
Le 19-03-2013, à 10:09:22 +0100, Yves Rutschle a écrit :
On Sun, Mar 17, 2013 at 03:21:29PM +0100, nicolas.patr...@gmail.com wrote:
Si tu as installé uptimed, lance uprecords à chaque redémarrage et
cumule le dernier.
Même pas besoin :
uprecords |grep up|grep since
up
Question très générale d'un dimanche après-midi pluvieux
Est-ce qu'il y a une moyen (± simple) d'obtenir le uptime cumulé depuis la
première mise sous tension (d'une Debian) ?
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists
Pour vous DESABONNER
On Sun, 17 Mar 2013 14:16:36 +0100
steve dl...@bluewin.ch wrote:
Question très générale d'un dimanche après-midi pluvieux
à Nantes on a un bôôô soleil :)
Est-ce qu'il y a une moyen (± simple) d'obtenir le uptime cumulé
depuis la première mise sous tension (d'une Debian) ?
Non, pas à ma
(± simple) d'obtenir le uptime cumulé
depuis la première mise sous tension (d'une Debian) ?
Non, pas à ma connaissance, mais rien n'empêche d'écrire un
script qui ira faire un append d'uptime dans un fichier texte
lors d'un shutdown.
Clair. Je pensais plutôt à un truc hardware, genre une
On Sun, 17 Mar 2013 14:49:20 +0100
steve dl...@bluewin.ch wrote:
Alors qu'est-ce que tu fais devant ton ordinateur ? :)
J'écris la part #3 d'une nouvelle érotique et je sèche
un peu, mais tu as raison je viens de voir que la
température était à 11°C, ptêt un ch'tit tour d'ici une heure.
…
Le 17/03/2013 14:16:36, steve a écrit :
Question très générale d'un dimanche après-midi pluvieux
Est-ce qu'il y a une moyen (± simple) d'obtenir le uptime cumulé
depuis la première mise sous tension (d'une Debian) ?
Si tu as installé uptimed, lance uprecords à chaque redémarrage et
cumule
Le 17/03/2013 15:19:25, nicolas.patr...@gmail.com a écrit :
Si tu as installé uptimed, lance uprecords à chaque redémarrage et
cumule le dernier.
Même pas besoin :
uprecords |grep up|grep since
up 828 days, 13:57:40 | since Sat Dec 25
12:21:11 2010
nicolas
On Tue, Sep 22, 2009 at 10:24:25AM -0300, Federico Juarez wrote:
Antes que nada Saludos a todos,
Estimados recurro a uds luego de mucho navegar, para ver si alguien sabe
o se le ocurre alguna pista, necesito saber el tiempo de uptime de mis
placas ethN, no el uptime del equipo, sino desde
Antes que nada Saludos a todos,
Estimados recurro a uds luego de mucho navegar, para ver si alguien sabe
o se le ocurre alguna pista, necesito saber el tiempo de uptime de mis
placas ethN, no el uptime del equipo, sino desde la ultima vez que
negociaron link, es posible saber este dato
El día 22 de septiembre de 2009 10:24, Federico Juarez
v...@vafe.com.ar escribió:
Antes que nada Saludos a todos,
Estimados recurro a uds luego de mucho navegar, para ver si alguien sabe
o se le ocurre alguna pista, necesito saber el tiempo de uptime de mis
placas ethN, no el uptime del
Gonzalo Rivero escribió:
El día 22 de septiembre de 2009 10:24, Federico Juarez
v...@vafe.com.ar escribió:
Antes que nada Saludos a todos,
Estimados recurro a uds luego de mucho navegar, para ver si alguien sabe
o se le ocurre alguna pista, necesito saber el tiempo de uptime de mis
pista, necesito saber el tiempo de uptime de mis
placas ethN, no el uptime del equipo, sino desde la ultima vez que
negociaron link, es posible saber este dato?.
no se si ifconfig mostrará esa información. Pero en dmesg pone un
cartelito indicando cuando estuvo conectada (link up) y
pytanie wiąże się z programem
uptime. Standardowo pokazuje on czas jak długo system jest włączony. Czy
istnieje w repo Debiana jakiś program który służy do tego samego, tylko zlicza
łączny czas. Podam na przykładzie o co mi tutaj chodzi:
poniedziałek 5h
wtorek 3h
środa 9h
czwartek 9h
piątek 7h
sobota
konfiguracja klawiszy oprócz strzałek
(najlepiej od razu po instalacji)? Drugie moje pytanie wiąże się z programem
uptime.
z tego co wiem to nie ma takiej mozliwosci
Standardowo pokazuje on czas jak długo system jest włączony. Czy istnieje w
repo Debiana jakiś program który służy do tego
uptime-records powinno zwrocic nazwe programu)
Jak problemy z GRUBem rozwiążę to poszukam tego softu... może to jest to czego
szukam.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Wojciech Ziniewicz wrote:
z tego co wiem to nie ma takiej mozliwosci
Prośba do wszystkich - jeśli nie jesteście pewni, nie piszcie bzdur,
wprowadza to jedynie zamieszanie.
Wracając do tematu; ^ - do góry, v - w dół.
Inne przydatne klawisze to, np. c - linia poleceń, Esc - powrót do menu wyboru.
W dniu 2 października 2008 20:14 użytkownik Rafal Czlonka
[EMAIL PROTECTED] napisał:
Wojciech Ziniewicz wrote:
z tego co wiem to nie ma takiej mozliwosci
Prośba do wszystkich - jeśli nie jesteście pewni, nie piszcie bzdur,
wprowadza to jedynie zamieszanie.
dziekuje
--
Wojciech Ziniewicz
Dnia 2008-10-02, o godz. 04:41:02
anakin_wolf [EMAIL PROTECTED] napisał(a):
Mianowicie z tego co wiem do wyboru systemu który ma
zostać uruchomiony używa się Gruba. W nim należy wybrać za pomocą
strzałek góra/dół i entera. Niestety u mnie w laptopie strzałki są
uszkodzone i nie działają.
Dnia 2008-10-02, o godz. 04:41:02
anakin_wolf [EMAIL PROTECTED] napisał(a):
Mianowicie z tego co wiem do wyboru systemu który ma
zostać uruchomiony używa się Gruba. W nim należy wybrać za pomocą
strzałek góra/dół i entera. Niestety u mnie w laptopie strzałki są
uszkodzone i nie działają.
Pessoal
Existe algum comando ou em algum lugar do log de
sistema que me informe em que momento meu servidor foi
desligado??
Com o comando uptime ele apenas exibe o tempo
decorrido desde que o sistema foi ligado.
Grato a todos,
Abra sua conta no Yahoo! Mail, o único sem limite de
Adriano escreveu:
Existe algum comando ou em algum lugar do log de
sistema que me informe em que momento meu servidor foi
desligado??
Adriano, você pode procurar por shutdown nos arquivos /var/log/syslog*.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
comando uptime ele apenas exibe o tempo
decorrido desde que o sistema foi ligado.
Grato a todos,
Abra sua conta no Yahoo! Mail, o único sem limite de espaço para
armazenamento!
http://br.mail.yahoo.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lost butler wrote:
Hi Folks,
The other day, I had posted message about sar/top misreporting idle
times. I came across the command procinfo which gives this info.
The idle time seems wrong. It is almost 4 times the uptime which
doesn't make
Hi Folks,
The other day, I had posted message about sar/top misreporting idle
times. I came across the command procinfo which gives this info.
The idle time seems wrong. It is almost 4 times the uptime which
doesn't make sense to me.
sysutils: 1.3.8.5.1
sysstat 5.0.6
sarge
I would appreciate
On 08/06/06 22:28 PM, Bryan Fr?chette wrote:
Hi i would like to know if anyone has a php app that can show bandwidth
and uptime graphs or ping graphs on a website, if anyone has an idea,
thank you
http://cricket.sf.net and http://www.cacti.net/ are two more rrdtool
based packages.
Mitch
On Mon, Aug 07, 2006 at 11:58:48AM +0800, shell wrote:
Bryan Frchette ??:
Hi i would like to know if anyone has a php app that can show bandwidth
and uptime graphs or ping graphs on a website, if anyone has an idea,
thank you
Bryan Frechette
try mrtg or ntop package.
You might
1 - 100 of 210 matches
Mail list logo