Vjylku

Why is quixotic not Quixotic (a proper adjective)?

Boss asked me to sign a resignation paper without a date on it along with my new contract

What did Putin say about a US deep state in his state-of-the-nation speech; what has he said in the past?

How can I differentiate duration vs starting time

How to achieve physical gender equality?

Sauna: Wood does not feel so hot

Is layered encryption more secure than long passwords?

Is there a way to pause a running process on Linux systems and resume later?

What does @ mean in a hostname in DNS configuration?

Was Opportunity's last message to Earth "My battery is low and it's getting dark"?

Is corrosion inhibitor paste conductive?

Manager has noticed coworker's excessive breaks. Should I warn him?

Is there any danger of my neighbor having my wife's signature?

Build ASCII Podiums

Why write a book when there's a movie in my head?

How to know if I am a 'Real Developer'

How to write painful torture scenes without being over-the-top

What dissuades people from lying about where they live in order to reduce state income taxes?

Why are `&array` and `array` pointing to the same address?

80-bit collision resistence because of 80-bit x87 registers?

Found a major flaw in paper from home university – to which I would like to return

Why do we divide Permutations to get to Combinations?

Why didn't Lorentz conclude that no object can go faster than light?

How can a kingdom keep the secret of a missing monarch from the public?

Last Reboot commands don't agree

13.04 reboot from terminalPC reboots randomly while powered onUbuntu 14.04 randomly freezes after long periods and fails to reboot automatically (crontab)Cannot reboot anymoreUnderstanding the output of last rebootRunning Ubuntu 16.04LTS hangs reboot not shutdownCannot reboot to Ubuntu from Microsoft17.10 long time to rebootUbuntu Terminal Freezes Commands Cannot Execute Until a RebootCan't reboot system

3

Different commands about showing last reboot have different opinions. Who is right?

# uptime

 10:05:31 up 90 days, 12:59,  2 users,  load average: 0.04, 0.02, 0.00



# who -b

             system boot  2018-11-22 21:05

# last reboot



wtmp begins Sat Feb  2 01:59:42 2019

reboot

share|improve this question

asked 6 hours ago

DimiDakDimiDak

1162

New contributor

DimiDak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

3

Different commands about showing last reboot have different opinions. Who is right?

# uptime

 10:05:31 up 90 days, 12:59,  2 users,  load average: 0.04, 0.02, 0.00



# who -b

             system boot  2018-11-22 21:05

# last reboot



wtmp begins Sat Feb  2 01:59:42 2019

reboot

share|improve this question

asked 6 hours ago

DimiDakDimiDak

1162

New contributor

DimiDak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

Different commands about showing last reboot have different opinions. Who is right?

# uptime

 10:05:31 up 90 days, 12:59,  2 users,  load average: 0.04, 0.02, 0.00



# who -b

             system boot  2018-11-22 21:05

# last reboot



wtmp begins Sat Feb  2 01:59:42 2019

reboot

share|improve this question

asked 6 hours ago

DimiDakDimiDak

1162

New contributor

DimiDak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

# uptime

 10:05:31 up 90 days, 12:59,  2 users,  load average: 0.04, 0.02, 0.00



# who -b

             system boot  2018-11-22 21:05

# last reboot



wtmp begins Sat Feb  2 01:59:42 2019

share|improve this question

asked 6 hours ago

DimiDakDimiDak

1162

New contributor

DimiDak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 6 hours ago

DimiDakDimiDak

1162

New contributor

DimiDak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 6 hours ago

DimiDakDimiDak

1162

New contributor

DimiDak is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 6 hours ago

DimiDakDimiDak

1162

2 Answers
2

active

oldest

votes

6

They are all correct.

• 
  uptime shows that the system has been up for 90 days and some
  hours.


• 
  who -b says the system was booted 2018-11-22 21:05 .. 90
  days and some hours ago.


• 
  last reboot says that the wtmp log file was rolled over or trunctaded at Sat Feb 2 01:59:42 2019, so it don't contain a reboot record.

share|improve this answer

answered 6 hours ago

Soren ASoren A

3,4041924

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanx, I didn't get the last one though..
  
  – DimiDak
  4 hours ago
  

  
  
  
  

add a comment | 

4

The uptime command is telling you the current time, followed by the length of time the system has been running. In your example this shows the system has been up for 90 days, 12 hours and 59 minutes.

who -b is giving you a date and time that corresponds to the same boot time. There's only a difference of seconds there, which I presume is the time taken between commands.

The last reboot command uses the /var/log/wtmp file to determine the last boot. This log file has been rotated since the last boot took place, so does not contain information about the last boot. There is likely an old version of wtmp, such as /var/log/wtmp.1 that you can also query with:

last reboot -f /var/log/wtmp.1

Unfortunately it's unlikely that will contain details of your last reboot either due to the time frame.

share|improve this answer

answered 6 hours ago

ArronicalArronical

13.5k84892

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanx, so what is "last reboot" good to use for?
  
  – DimiDak
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  It can tell you what the last reboot was, but it has to be recent enough that it's still available in the recent versions of the wtmp file. There must be a way to reconfigure how many wtmp files are saved. If you reboot your server now, then issue last reboot, it will show up in the output. The current output just means there are no recorded reboots in wtmp.
  
  – Arronical
  4 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

DimiDak is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120063%2flast-reboot-commands-dont-agree%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

6

They are all correct.

• 
  uptime shows that the system has been up for 90 days and some
  hours.


• 
  who -b says the system was booted 2018-11-22 21:05 .. 90
  days and some hours ago.


• 
  last reboot says that the wtmp log file was rolled over or trunctaded at Sat Feb 2 01:59:42 2019, so it don't contain a reboot record.

share|improve this answer

answered 6 hours ago

Soren ASoren A

3,4041924

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanx, I didn't get the last one though..
  
  – DimiDak
  4 hours ago
  

  
  
  
  

add a comment | 

6

They are all correct.

• 
  uptime shows that the system has been up for 90 days and some
  hours.


• 
  who -b says the system was booted 2018-11-22 21:05 .. 90
  days and some hours ago.


• 
  last reboot says that the wtmp log file was rolled over or trunctaded at Sat Feb 2 01:59:42 2019, so it don't contain a reboot record.

share|improve this answer

answered 6 hours ago

Soren ASoren A

3,4041924

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanx, I didn't get the last one though..
  
  – DimiDak
  4 hours ago
  

  
  
  
  

add a comment | 

They are all correct.

• 
  uptime shows that the system has been up for 90 days and some
  hours.


• 
  who -b says the system was booted 2018-11-22 21:05 .. 90
  days and some hours ago.


• 
  last reboot says that the wtmp log file was rolled over or trunctaded at Sat Feb 2 01:59:42 2019, so it don't contain a reboot record.

share|improve this answer

answered 6 hours ago

Soren ASoren A

3,4041924

share|improve this answer

answered 6 hours ago

Soren ASoren A

3,4041924

answered 6 hours ago

Soren ASoren A

3,4041924

answered 6 hours ago

Soren ASoren A

3,4041924

4

The uptime command is telling you the current time, followed by the length of time the system has been running. In your example this shows the system has been up for 90 days, 12 hours and 59 minutes.

who -b is giving you a date and time that corresponds to the same boot time. There's only a difference of seconds there, which I presume is the time taken between commands.

The last reboot command uses the /var/log/wtmp file to determine the last boot. This log file has been rotated since the last boot took place, so does not contain information about the last boot. There is likely an old version of wtmp, such as /var/log/wtmp.1 that you can also query with:

last reboot -f /var/log/wtmp.1

Unfortunately it's unlikely that will contain details of your last reboot either due to the time frame.

share|improve this answer

answered 6 hours ago

ArronicalArronical

13.5k84892

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanx, so what is "last reboot" good to use for?
  
  – DimiDak
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  It can tell you what the last reboot was, but it has to be recent enough that it's still available in the recent versions of the wtmp file. There must be a way to reconfigure how many wtmp files are saved. If you reboot your server now, then issue last reboot, it will show up in the output. The current output just means there are no recorded reboots in wtmp.
  
  – Arronical
  4 hours ago
  

  
  
  
  

add a comment | 

4

The uptime command is telling you the current time, followed by the length of time the system has been running. In your example this shows the system has been up for 90 days, 12 hours and 59 minutes.

who -b is giving you a date and time that corresponds to the same boot time. There's only a difference of seconds there, which I presume is the time taken between commands.

The last reboot command uses the /var/log/wtmp file to determine the last boot. This log file has been rotated since the last boot took place, so does not contain information about the last boot. There is likely an old version of wtmp, such as /var/log/wtmp.1 that you can also query with:

last reboot -f /var/log/wtmp.1

Unfortunately it's unlikely that will contain details of your last reboot either due to the time frame.

share|improve this answer

answered 6 hours ago

ArronicalArronical

13.5k84892

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanx, so what is "last reboot" good to use for?
  
  – DimiDak
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  It can tell you what the last reboot was, but it has to be recent enough that it's still available in the recent versions of the wtmp file. There must be a way to reconfigure how many wtmp files are saved. If you reboot your server now, then issue last reboot, it will show up in the output. The current output just means there are no recorded reboots in wtmp.
  
  – Arronical
  4 hours ago
  

  
  
  
  

add a comment | 

The uptime command is telling you the current time, followed by the length of time the system has been running. In your example this shows the system has been up for 90 days, 12 hours and 59 minutes.

who -b is giving you a date and time that corresponds to the same boot time. There's only a difference of seconds there, which I presume is the time taken between commands.

The last reboot command uses the /var/log/wtmp file to determine the last boot. This log file has been rotated since the last boot took place, so does not contain information about the last boot. There is likely an old version of wtmp, such as /var/log/wtmp.1 that you can also query with:

last reboot -f /var/log/wtmp.1

Unfortunately it's unlikely that will contain details of your last reboot either due to the time frame.

share|improve this answer

answered 6 hours ago

ArronicalArronical

13.5k84892

last reboot -f /var/log/wtmp.1

share|improve this answer

answered 6 hours ago

ArronicalArronical

13.5k84892

answered 6 hours ago

ArronicalArronical

13.5k84892

answered 6 hours ago

ArronicalArronical

13.5k84892