Thanx Bill. I think it has something to do with the cloud and replicated
server images. Can I blow away all syslogs and restart logging?
Yup, I appear to be hosed. >>
root@Ubuntu0003:/var/log# ls -l |grep sys
-rw-r----- 1 root root 0 2012-03-20 02:12 syslog
-rw-r----- 1 root root 29616 2012-03-20 02:12 syslog.1
-rw-r----- 1 root root 9586 2012-03-14 00:40 syslog.2.gz
-rw-r----- 1 root root 7013 2012-03-09 19:02 syslog.3.gz
-rw-r----- 1 root root 5627 2012-03-08 18:56 syslog.4.gz
-rw-r----- 1 root root 25342 2012-03-07 19:02 syslog.5.gz
root@Ubuntu0003:/var/log# logger Testing syslog
root@Ubuntu0003:/var/log# ls -l |grep sys
-rw-r----- 1 root root 0 2012-03-20 02:12 syslog
-rw-r----- 1 root root 29616 2012-03-20 02:12 syslog.1
-rw-r----- 1 root root 9586 2012-03-14 00:40 syslog.2.gz
-rw-r----- 1 root root 7013 2012-03-09 19:02 syslog.3.gz
-rw-r----- 1 root root 5627 2012-03-08 18:56 syslog.4.gz
-rw-r----- 1 root root 25342 2012-03-07 19:02 syslog.5.gz
root@Ubuntu0003:/var/log#
--
Joe Golden /_\ www.Triangul.us /_\ websites with class
On 03/20/2012 11:48 PM, William Stearns wrote:
Good evening, Joe,
On Tue, 20 Mar 2012, joe golden wrote:
Hi All.
I find myself on an Ubuntu cloud server and I'm a Debian guy. It feels
comfortable, sort of, which could be dangerous ;-)
The default log settings on Debian are more verbose I think. Is syslog
supposed to be empty? That makes me nervous.
One quick way to test it is to run:
logger Testing syslog
And see if that shows up in one of the log files. If not, something's
definitely wrong.
Thanx.
--
Joe Golden /_\ www.Triangul.us /_\ websites with class
Cheers,
- Bill
---------------------------------------------------------------------------
"The cure for 1984 is 1776."
-- Anonymous
--------------------------------------------------------------------------
William Stearns ([email protected], tools and papers: www.stearns.org)
Top-notch computer security training at www.sans.org , www.giac.net
--------------------------------------------------------------------------
