YHBT YHL HND - I was too
leny2010 said:
> Read the links in my last two posts and you will find where the shutdown &
boot messages are stored on disk.
> Nothing meaningful to your diagnosis occurs after the disks are umounted in
shutdown.
OK; I tried [sudo find /var/log -type f -print0 | xargs -0 sudo zgrep
In a similar vein perhaps worth trying issudo shutdown -H
(Note the H is capitalized!)
I remember that a fix to some computers not powering off after you tell them
to shut down is to add a acpi_osi=X parameter to Linux in grub.
Apparently X can be *leave blank*, Linux, Windows.
Remember to update-grub after you change the config.
Perhaps we could induce this condition.
Read the links in my last two posts and you will find where the shutdown &
boot messages are stored on disk. Nothing meaningful to your diagnosis
occurs after the disks are umounted in shutdown.
Following the suggestion to video the action, I managed to capture several
different sets of shutdown blinkies, to wit:
1. Press to continue K98mdadm/etc/rc0.d/K98mdadm-waitidle.bak: 16 : read:
arg count
Could not acquire the 'org.freedesktop.ModemManager1" service name
2.
"So the shutdown blinkies remain as elusive as ever."
I don't know why you say that: From what you've describe this all seems very
standard to me. If you recall one of the things that happens during shutdown
is all running processes are sent SIGTERM (To quote from the GNU C Library
manual:
"my video camera won't stay focused on the screen."
Try turning off automatic focus. Focus it manually first, and then do a shut
down once the focus is perfect.
"Something in the system is trying to tell me what's going on just before
shutdown"
No, it's not trying to tell you something. It's not alive. :) Rather, it is
executing it's pre-programmed steps for brining the system down which
involves things like SIGTERM to running processes (the
Following leny2010's lead, hitting the ESC key during shutdown/restart does
indeed lift the Plymouth veil from the ephemeral shutdown messages, but
they're still displayed unacceptably briefly. If only there was another key
to pause that shutdown.
you are wrong jxself. **he** is alive.
DDG: 'Where are the ubuntu boot messages
https://askubuntu.com/questions/91286/how-to-see-log-to-find-a-boot-problem
DDG: 'Where are the ubuntu shutdown messages
https://askubuntu.com/questions/58625/where-is-the-shutdown-log
And
man service
e.g.
sudo service --status-all
Should be what
But meddle with the Trisquel boot process rather than running services AT
YOUR OWN RISK.
Trying to have it both ways ?:
Criticism #1. I didn't look it up before complaining ...
Criticism #2. I'm complaining because I can't look it up ...
Nevertheless, here's my wish: Something in the system is trying to tell me
what's going on just before shutdown, but the messages that indicate
1. Those messages are as Magic Banana says in the file /var/log/messages ,
look at them with
sudo less /var/log/messages
in Terminal
2. If you want more detailed messages use either of the commands apt-get or
aptitude with the appropriate parameters. Again from Terminal. You might
find
1. Shutdown messages:
Four years ago, Magic Banana replied in
http://trisquel.info/en/forum/trisquel-45-messages-shutdown:
> Indeed, taking a look at /var/log/messages (which is timestamped) is a good
idea.
> You can read the logs from a graphical utility in the System/Administration
menu.
1. leny2010 and Magic Banana suggested looking in /var/log/messages, but
there is no such file in my Trisquel 7 installation; is "dmesg" another word
for "messages" ? Anyway, dmesg doesn't capture those shutdown blinkies,
either.
2. I tried "sudo script -c "shutdown -h now"
A DDG search on 'Where is /var/log/messages in ubuntu trusty' turns up
https://askubuntu.com/questions/51265/where-is-var-log-messages
Which says it all goes to syslog, always did just htere's no longer any
/v/l/messages. Obviously, until the disks are umounted as Magic Banana says.
What
Whenever Johny Carson did his raincoat-flashing routine on late night TV, he
always turned away from the camera ...
Recently I've been pleading for the following logs:
1. A shutdown log. It's no longer a bunch of benign messages that appear for
fractions of a second; they might be helpful,
19 matches
Mail list logo
