that will catch MOST logs. Some apps may have specific log file locations and log outside of syslog/rsyslog - apache and many mail system spring to mind. Those need to be individually configured in their own config files.
You would also need to look at the logrotate utility (/etc/logrotate.d/*)
But perhaps the easiest thing is to mount a bit of spinning rust or something less fragile on /var, or /var/log
well he was a Cnut all right. However capitalism is not the opposite of socialism, unless you take Marx's weird paranoid views as gospel.
And even in his views, neither can exist without the other.
>
--
New Socialism consists essentially in being seen to have your heart in
the right place whilst your head is in the clouds and your hand is in
someone else's pocket.
Op Mon, 20 Jul 2015 23:00:49 +0000 (UTC) schreef Martin Gregorie:
Next to VNC I can open a ssh console with putty *) or cygwin, but what how can I monitor a file that does not exist? What is AS corruption? Nothing to do with assembler I presume?
*) As I have Vista, there were problems with Putty 064.
065 pre-release works.
AS corruption was meant to be SD corruption. Since this thread mentioned (always?) corrupting the SD card when attempting to issue a 'shutdown -h' [1] command from VNC I wondered if that was why you couldn't see the log file.
My other typo was to misname it: I meant /var/log/messages. I just fired up mine to check: using the default logging parameters it is writing the messages logfile as I'd expected, so the command
sudo less /var/log/messages
should show the last shut down followed by the current boot up sequence if you run it after a restart. My log shows:
Jul 17 20:05:22 rpi shutdown[2362]: shutting down for system halt
after I ran 'sudo halt' last time. Alternatively, if you ran:
sudo tail -f /var/log/messages
from a second VNC or SSH console window and then shut the RPi down, you should see everything that got logged between issuing the shutdown command and the point when the kernel stops tail or the network connection (whichever is stopped first - probably tail.
Not a problem here: I just ssh into my RPi from this laptop, which is running the Fedora 22 release of Red Hat Linux. I haven't used Windows seriously since 2004.
[1] If the poster who complained about 'shutdown -h' not working under VNC really ran just 'shutdown -h' instead of 'shutdown -h now' then I'm not surprised his RPi didn't halt, because 'shutdown -h' just slaps your wrist and tells you to use valid parameters.
This may be a RaspberryPi special because Fedora 22 still uses the traditional shut down procedure: 'shutdown -h' is equivalent to 'shutdown -h 1', IOW it broadcasts a message about imminent shutdown and waits 1 minute before shutting down. This allows for finger trouble because the command 'shutdown -c' can be used to cancel the pending shutdown.
--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.