How do I check if last shutdown was clean?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
How can tell that my last shutdown was properly done in Ubuntu 11.10 or if the machine was powered off before shutting down the OS?
shutdown log power-management
add a comment |
How can tell that my last shutdown was properly done in Ubuntu 11.10 or if the machine was powered off before shutting down the OS?
shutdown log power-management
2
Take a look at /var/log/syslog.0
– Gigili
Feb 10 '12 at 12:20
add a comment |
How can tell that my last shutdown was properly done in Ubuntu 11.10 or if the machine was powered off before shutting down the OS?
shutdown log power-management
How can tell that my last shutdown was properly done in Ubuntu 11.10 or if the machine was powered off before shutting down the OS?
shutdown log power-management
shutdown log power-management
edited Feb 10 '12 at 12:39
Bruno Pereira
60.7k26181209
60.7k26181209
asked Feb 10 '12 at 11:27
VikramjeetVikramjeet
2,05592740
2,05592740
2
Take a look at /var/log/syslog.0
– Gigili
Feb 10 '12 at 12:20
add a comment |
2
Take a look at /var/log/syslog.0
– Gigili
Feb 10 '12 at 12:20
2
2
Take a look at /var/log/syslog.0
– Gigili
Feb 10 '12 at 12:20
Take a look at /var/log/syslog.0
– Gigili
Feb 10 '12 at 12:20
add a comment |
3 Answers
3
active
oldest
votes
If the machine was shutdown properly then there must be a shutdown log logged in kern.log
file in /var/log
directory. After a shutdown whenever a normal boot occurs the OS writes the log for the same in kern.log. Hence every boot log must be preceded by a shutdown log if the booting and shutdown process was normal.
Whenever a normal shutdown occurs "Kernel logging (proc) stopped."
is written in kern.log.
Similarly whenever a boot occurs "imklog 5.8.1, log source = /proc/kmsg started."
is written in kern.log
These two messages should be in the order if the shutdown was normal rather than abrupt power off. There should be no "imklog 5.8.1, log source = /proc/kmsg started." message without the "Kernel logging (proc) stopped." message if the previous shutdown was normal. The both message should always occur in pair in log.
Just type in terminal :-
gedit /var/log/kern.log
and check for the shutdown and boot log pairs. If they are found not in pairs anywhere
that shutdown must have been abrupt.
1
replace gedit with your default text editor.
– Vikramjeet
Feb 28 '12 at 17:08
my kern.log is empty
– Nade
Oct 27 '13 at 18:29
1
@Nade trykern.log.1
.
– a different ben
Oct 27 '13 at 22:50
2
neither of those phrases are in my log. Not even part of them. I really need to know if my computer's being shutdown properly b/c I believe I have a kid who's simply holding down the power button.
– KI4JGT
Dec 28 '13 at 4:44
as of Ubunutu 16.04 this seems no longer correct. i.e. I don't getcat /var/log/syslog | grep -i "stopped"
(and similar. also sanity-tested the contrary), despite that this was clearly part of the previous shutdown messages... (the visible log stuff, when pressing ESC to kill the splash screen while shutting down) - anyone got an update?
– Frank Nocke
Oct 27 '16 at 3:41
add a comment |
As of Ubuntu 16.04, a clean shutdown followed by a proper reboot will write these 2 lines one after the other in /var/log/syslog
Mar 9 14:14:06 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1086" x-info="http://www.rsyslog.com"] exiting on signal 15.
Mar 9 15:23:42 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1069" x-info="http://www.rsyslog.com"] start
add a comment |
Hi you can run a script to check if the last shutdown was proper or not.
Just put the following lines in a bash script and run it after a system boot up.
#!/bin/bash
B="1"
touch data_file
echo $(($(grep -nr "$(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | grep $(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | cut -d' ' -f3 | sort -k1 -r | sort --unique --stable -k2,3))" /var/log/kern.log | awk '{printf $1}' | grep -oE "[[:digit:]]{1,}")-$B)) > data_file
if [[
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $6}') == "Kernel") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $7}') == "logging") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $8}') == "(proc)") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $9}') == "stopped.")
]]; then
echo Last Shutdown-proper
else
echo Last Shutdown_not proper
fi
rm data_file
NOTE: Please be in a root user to run the script. It won't harm your system :)
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f103015%2fhow-do-i-check-if-last-shutdown-was-clean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
If the machine was shutdown properly then there must be a shutdown log logged in kern.log
file in /var/log
directory. After a shutdown whenever a normal boot occurs the OS writes the log for the same in kern.log. Hence every boot log must be preceded by a shutdown log if the booting and shutdown process was normal.
Whenever a normal shutdown occurs "Kernel logging (proc) stopped."
is written in kern.log.
Similarly whenever a boot occurs "imklog 5.8.1, log source = /proc/kmsg started."
is written in kern.log
These two messages should be in the order if the shutdown was normal rather than abrupt power off. There should be no "imklog 5.8.1, log source = /proc/kmsg started." message without the "Kernel logging (proc) stopped." message if the previous shutdown was normal. The both message should always occur in pair in log.
Just type in terminal :-
gedit /var/log/kern.log
and check for the shutdown and boot log pairs. If they are found not in pairs anywhere
that shutdown must have been abrupt.
1
replace gedit with your default text editor.
– Vikramjeet
Feb 28 '12 at 17:08
my kern.log is empty
– Nade
Oct 27 '13 at 18:29
1
@Nade trykern.log.1
.
– a different ben
Oct 27 '13 at 22:50
2
neither of those phrases are in my log. Not even part of them. I really need to know if my computer's being shutdown properly b/c I believe I have a kid who's simply holding down the power button.
– KI4JGT
Dec 28 '13 at 4:44
as of Ubunutu 16.04 this seems no longer correct. i.e. I don't getcat /var/log/syslog | grep -i "stopped"
(and similar. also sanity-tested the contrary), despite that this was clearly part of the previous shutdown messages... (the visible log stuff, when pressing ESC to kill the splash screen while shutting down) - anyone got an update?
– Frank Nocke
Oct 27 '16 at 3:41
add a comment |
If the machine was shutdown properly then there must be a shutdown log logged in kern.log
file in /var/log
directory. After a shutdown whenever a normal boot occurs the OS writes the log for the same in kern.log. Hence every boot log must be preceded by a shutdown log if the booting and shutdown process was normal.
Whenever a normal shutdown occurs "Kernel logging (proc) stopped."
is written in kern.log.
Similarly whenever a boot occurs "imklog 5.8.1, log source = /proc/kmsg started."
is written in kern.log
These two messages should be in the order if the shutdown was normal rather than abrupt power off. There should be no "imklog 5.8.1, log source = /proc/kmsg started." message without the "Kernel logging (proc) stopped." message if the previous shutdown was normal. The both message should always occur in pair in log.
Just type in terminal :-
gedit /var/log/kern.log
and check for the shutdown and boot log pairs. If they are found not in pairs anywhere
that shutdown must have been abrupt.
1
replace gedit with your default text editor.
– Vikramjeet
Feb 28 '12 at 17:08
my kern.log is empty
– Nade
Oct 27 '13 at 18:29
1
@Nade trykern.log.1
.
– a different ben
Oct 27 '13 at 22:50
2
neither of those phrases are in my log. Not even part of them. I really need to know if my computer's being shutdown properly b/c I believe I have a kid who's simply holding down the power button.
– KI4JGT
Dec 28 '13 at 4:44
as of Ubunutu 16.04 this seems no longer correct. i.e. I don't getcat /var/log/syslog | grep -i "stopped"
(and similar. also sanity-tested the contrary), despite that this was clearly part of the previous shutdown messages... (the visible log stuff, when pressing ESC to kill the splash screen while shutting down) - anyone got an update?
– Frank Nocke
Oct 27 '16 at 3:41
add a comment |
If the machine was shutdown properly then there must be a shutdown log logged in kern.log
file in /var/log
directory. After a shutdown whenever a normal boot occurs the OS writes the log for the same in kern.log. Hence every boot log must be preceded by a shutdown log if the booting and shutdown process was normal.
Whenever a normal shutdown occurs "Kernel logging (proc) stopped."
is written in kern.log.
Similarly whenever a boot occurs "imklog 5.8.1, log source = /proc/kmsg started."
is written in kern.log
These two messages should be in the order if the shutdown was normal rather than abrupt power off. There should be no "imklog 5.8.1, log source = /proc/kmsg started." message without the "Kernel logging (proc) stopped." message if the previous shutdown was normal. The both message should always occur in pair in log.
Just type in terminal :-
gedit /var/log/kern.log
and check for the shutdown and boot log pairs. If they are found not in pairs anywhere
that shutdown must have been abrupt.
If the machine was shutdown properly then there must be a shutdown log logged in kern.log
file in /var/log
directory. After a shutdown whenever a normal boot occurs the OS writes the log for the same in kern.log. Hence every boot log must be preceded by a shutdown log if the booting and shutdown process was normal.
Whenever a normal shutdown occurs "Kernel logging (proc) stopped."
is written in kern.log.
Similarly whenever a boot occurs "imklog 5.8.1, log source = /proc/kmsg started."
is written in kern.log
These two messages should be in the order if the shutdown was normal rather than abrupt power off. There should be no "imklog 5.8.1, log source = /proc/kmsg started." message without the "Kernel logging (proc) stopped." message if the previous shutdown was normal. The both message should always occur in pair in log.
Just type in terminal :-
gedit /var/log/kern.log
and check for the shutdown and boot log pairs. If they are found not in pairs anywhere
that shutdown must have been abrupt.
edited Feb 15 at 10:28
d a i s y
3,40782444
3,40782444
answered Feb 28 '12 at 17:07
VikramjeetVikramjeet
2,05592740
2,05592740
1
replace gedit with your default text editor.
– Vikramjeet
Feb 28 '12 at 17:08
my kern.log is empty
– Nade
Oct 27 '13 at 18:29
1
@Nade trykern.log.1
.
– a different ben
Oct 27 '13 at 22:50
2
neither of those phrases are in my log. Not even part of them. I really need to know if my computer's being shutdown properly b/c I believe I have a kid who's simply holding down the power button.
– KI4JGT
Dec 28 '13 at 4:44
as of Ubunutu 16.04 this seems no longer correct. i.e. I don't getcat /var/log/syslog | grep -i "stopped"
(and similar. also sanity-tested the contrary), despite that this was clearly part of the previous shutdown messages... (the visible log stuff, when pressing ESC to kill the splash screen while shutting down) - anyone got an update?
– Frank Nocke
Oct 27 '16 at 3:41
add a comment |
1
replace gedit with your default text editor.
– Vikramjeet
Feb 28 '12 at 17:08
my kern.log is empty
– Nade
Oct 27 '13 at 18:29
1
@Nade trykern.log.1
.
– a different ben
Oct 27 '13 at 22:50
2
neither of those phrases are in my log. Not even part of them. I really need to know if my computer's being shutdown properly b/c I believe I have a kid who's simply holding down the power button.
– KI4JGT
Dec 28 '13 at 4:44
as of Ubunutu 16.04 this seems no longer correct. i.e. I don't getcat /var/log/syslog | grep -i "stopped"
(and similar. also sanity-tested the contrary), despite that this was clearly part of the previous shutdown messages... (the visible log stuff, when pressing ESC to kill the splash screen while shutting down) - anyone got an update?
– Frank Nocke
Oct 27 '16 at 3:41
1
1
replace gedit with your default text editor.
– Vikramjeet
Feb 28 '12 at 17:08
replace gedit with your default text editor.
– Vikramjeet
Feb 28 '12 at 17:08
my kern.log is empty
– Nade
Oct 27 '13 at 18:29
my kern.log is empty
– Nade
Oct 27 '13 at 18:29
1
1
@Nade try
kern.log.1
.– a different ben
Oct 27 '13 at 22:50
@Nade try
kern.log.1
.– a different ben
Oct 27 '13 at 22:50
2
2
neither of those phrases are in my log. Not even part of them. I really need to know if my computer's being shutdown properly b/c I believe I have a kid who's simply holding down the power button.
– KI4JGT
Dec 28 '13 at 4:44
neither of those phrases are in my log. Not even part of them. I really need to know if my computer's being shutdown properly b/c I believe I have a kid who's simply holding down the power button.
– KI4JGT
Dec 28 '13 at 4:44
as of Ubunutu 16.04 this seems no longer correct. i.e. I don't get
cat /var/log/syslog | grep -i "stopped"
(and similar. also sanity-tested the contrary), despite that this was clearly part of the previous shutdown messages... (the visible log stuff, when pressing ESC to kill the splash screen while shutting down) - anyone got an update?– Frank Nocke
Oct 27 '16 at 3:41
as of Ubunutu 16.04 this seems no longer correct. i.e. I don't get
cat /var/log/syslog | grep -i "stopped"
(and similar. also sanity-tested the contrary), despite that this was clearly part of the previous shutdown messages... (the visible log stuff, when pressing ESC to kill the splash screen while shutting down) - anyone got an update?– Frank Nocke
Oct 27 '16 at 3:41
add a comment |
As of Ubuntu 16.04, a clean shutdown followed by a proper reboot will write these 2 lines one after the other in /var/log/syslog
Mar 9 14:14:06 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1086" x-info="http://www.rsyslog.com"] exiting on signal 15.
Mar 9 15:23:42 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1069" x-info="http://www.rsyslog.com"] start
add a comment |
As of Ubuntu 16.04, a clean shutdown followed by a proper reboot will write these 2 lines one after the other in /var/log/syslog
Mar 9 14:14:06 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1086" x-info="http://www.rsyslog.com"] exiting on signal 15.
Mar 9 15:23:42 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1069" x-info="http://www.rsyslog.com"] start
add a comment |
As of Ubuntu 16.04, a clean shutdown followed by a proper reboot will write these 2 lines one after the other in /var/log/syslog
Mar 9 14:14:06 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1086" x-info="http://www.rsyslog.com"] exiting on signal 15.
Mar 9 15:23:42 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1069" x-info="http://www.rsyslog.com"] start
As of Ubuntu 16.04, a clean shutdown followed by a proper reboot will write these 2 lines one after the other in /var/log/syslog
Mar 9 14:14:06 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1086" x-info="http://www.rsyslog.com"] exiting on signal 15.
Mar 9 15:23:42 *YOUR-HOSTNAME* rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1069" x-info="http://www.rsyslog.com"] start
answered Mar 9 '18 at 15:08
VictorvgVictorvg
412
412
add a comment |
add a comment |
Hi you can run a script to check if the last shutdown was proper or not.
Just put the following lines in a bash script and run it after a system boot up.
#!/bin/bash
B="1"
touch data_file
echo $(($(grep -nr "$(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | grep $(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | cut -d' ' -f3 | sort -k1 -r | sort --unique --stable -k2,3))" /var/log/kern.log | awk '{printf $1}' | grep -oE "[[:digit:]]{1,}")-$B)) > data_file
if [[
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $6}') == "Kernel") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $7}') == "logging") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $8}') == "(proc)") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $9}') == "stopped.")
]]; then
echo Last Shutdown-proper
else
echo Last Shutdown_not proper
fi
rm data_file
NOTE: Please be in a root user to run the script. It won't harm your system :)
add a comment |
Hi you can run a script to check if the last shutdown was proper or not.
Just put the following lines in a bash script and run it after a system boot up.
#!/bin/bash
B="1"
touch data_file
echo $(($(grep -nr "$(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | grep $(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | cut -d' ' -f3 | sort -k1 -r | sort --unique --stable -k2,3))" /var/log/kern.log | awk '{printf $1}' | grep -oE "[[:digit:]]{1,}")-$B)) > data_file
if [[
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $6}') == "Kernel") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $7}') == "logging") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $8}') == "(proc)") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $9}') == "stopped.")
]]; then
echo Last Shutdown-proper
else
echo Last Shutdown_not proper
fi
rm data_file
NOTE: Please be in a root user to run the script. It won't harm your system :)
add a comment |
Hi you can run a script to check if the last shutdown was proper or not.
Just put the following lines in a bash script and run it after a system boot up.
#!/bin/bash
B="1"
touch data_file
echo $(($(grep -nr "$(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | grep $(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | cut -d' ' -f3 | sort -k1 -r | sort --unique --stable -k2,3))" /var/log/kern.log | awk '{printf $1}' | grep -oE "[[:digit:]]{1,}")-$B)) > data_file
if [[
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $6}') == "Kernel") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $7}') == "logging") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $8}') == "(proc)") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $9}') == "stopped.")
]]; then
echo Last Shutdown-proper
else
echo Last Shutdown_not proper
fi
rm data_file
NOTE: Please be in a root user to run the script. It won't harm your system :)
Hi you can run a script to check if the last shutdown was proper or not.
Just put the following lines in a bash script and run it after a system boot up.
#!/bin/bash
B="1"
touch data_file
echo $(($(grep -nr "$(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | grep $(cat /var/log/kern.log | grep "$(date -d $(who -b | awk '{printf $3}') '+%b %-d')" | grep imklog | cut -d' ' -f3 | sort -k1 -r | sort --unique --stable -k2,3))" /var/log/kern.log | awk '{printf $1}' | grep -oE "[[:digit:]]{1,}")-$B)) > data_file
if [[
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $6}') == "Kernel") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $7}') == "logging") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $8}') == "(proc)") &&
($(sed -n $(cat data_file)p /var/log/kern.log | awk '{print $9}') == "stopped.")
]]; then
echo Last Shutdown-proper
else
echo Last Shutdown_not proper
fi
rm data_file
NOTE: Please be in a root user to run the script. It won't harm your system :)
edited Apr 2 '17 at 7:17
Rockhorse Park
75
75
answered Jun 20 '14 at 3:30
SidSid
2116
2116
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f103015%2fhow-do-i-check-if-last-shutdown-was-clean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Take a look at /var/log/syslog.0
– Gigili
Feb 10 '12 at 12:20