Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Micheal Patterson
- Original Message - From: Matt Cyber Dog LaPlante [EMAIL PROTECTED] To: 'Matthew Seaman' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, May 15, 2004 12:34 PM Subject: RE: FreeBSD 4.7 Syslogs I tried the logger command, but it didn't reach the messages file (which is still

Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Micheal Patterson
- Original Message - From: Matt Cyber Dog LaPlante [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, May 15, 2004 3:38 PM Subject: RE: FreeBSD 4.7 Syslogs snip You've got a pretty high number of max logs with pretty hefty file size limits. What's a df -k show on that system

Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Micheal Patterson
- Original Message - From: JJB [EMAIL PROTECTED] To: Matt Cyber Dog LaPlante [EMAIL PROTECTED]; 'Matthew Seaman' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, May 15, 2004 3:04 PM Subject: RE: FreeBSD 4.7 Syslogs Well since you are new to FBSD and since the syslogd -d

RE: FreeBSD 4.7 Syslogs

2004-05-16 Thread Sunil Sunder Raj
Hi, Just give 777 permissions to /var/log/messages Regards SSR From: Matt \Cyber Dog\ LaPlante [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: FreeBSD 4.7 Syslogs Date: Sat, 15 May 2004 16:38:54 -0400 /var/run/dmesg.boot: Copyright (c

Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Shaun T. Erickson
Sunil Sunder Raj wrote: Just give 777 permissions to /var/log/messages This is BAD advice, and you should NOT follow it. If you do, you will give anyone the ability to modify or delete your log entries, which yoou do NOT want. Find and fix the actual problem; don't bypass the symptom with

Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Mark
Sunil Sunder Raj wrote: Hi, Just give 777 permissions to /var/log/messages With all due respect, but that is rather bad advice. I have been running syslog on FreeBSD 4.7R for years, without problem; and never ever did I have to resort to making /var/log/messages world-writeable. Besides,

Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Sunil Sunder Raj
: Re: FreeBSD 4.7 Syslogs Date: Sun, 16 May 2004 09:47:01 -0400 Sunil Sunder Raj wrote: Just give 777 permissions to /var/log/messages This is BAD advice, and you should NOT follow it. If you do, you will give anyone the ability to modify or delete your log entries, which yoou do NOT want. Find

Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Shaun T. Erickson
Sunil Sunder Raj wrote: Hi, I did not mean to change the permissions to 777 permanently. Just to come to a conclusion on whether it is a permission problem. As 90% unix problems are related to permissions. Then you should have said so. But you did not - you simply told an admitted noob to set

RE: FreeBSD 4.7 Syslogs

2004-05-16 Thread JJB
: Sunday, May 16, 2004 5:04 AM To: Matt Cyber Dog LaPlante; 'Matthew Seaman'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: FreeBSD 4.7 Syslogs - Original Message - From: JJB [EMAIL PROTECTED] To: Matt Cyber Dog LaPlante [EMAIL PROTECTED]; 'Matthew Seaman' [EMAIL PROTECTED]; [EMAIL

RE: FreeBSD 4.7 Syslogs

2004-05-16 Thread Warren Block
On Sun, 16 May 2004, JJB wrote: Thanks for the additional info. I tested using this logger -p lpr.err test test There is no error message about logger not working. And I get nothing in the /var/log/lpr-errs log file. That would be /var/log/lpd-errs. This is so simple that the only

RE: FreeBSD 4.7 Syslogs

2004-05-16 Thread JJB
PROTECTED] Subject: RE: FreeBSD 4.7 Syslogs On Sun, 16 May 2004, JJB wrote: Thanks for the additional info. I tested using this logger -p lpr.err test test There is no error message about logger not working. And I get nothing in the /var/log/lpr-errs log file. That would be /var/log/lpd

RE: FreeBSD 4.7 Syslogs

2004-05-16 Thread JJB
no idea why it was hosed, but working now and that is all that matters. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of JJB Sent: Sunday, May 16, 2004 11:14 AM To: Warren Block Cc: Micheal Patterson; [EMAIL PROTECTED] Subject: RE: FreeBSD 4.7 Syslogs So I have

Re: FreeBSD 4.7 Syslogs

2004-05-16 Thread Micheal Patterson
- Original Message - From: JJB [EMAIL PROTECTED] To: Micheal Patterson [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, May 16, 2004 9:37 AM Subject: RE: FreeBSD 4.7 Syslogs Thanks for the additional info. I tested using this logger -p lpr.err test test There is no error

RE: FreeBSD 4.7 Syslogs

2004-05-16 Thread Cyber Dog
a PayPal account, I wouldn't mind sending over a little token of my appreciation. Thanks again, Matt -Original Message- From: JJB [mailto:[EMAIL PROTECTED] Sent: Saturday, May 15, 2004 10:42 PM To: Matt Cyber Dog LaPlante Subject: RE: FreeBSD 4.7 Syslogs Matt. You did not reboot system

Re: FreeBSD 4.7 Syslogs

2004-05-15 Thread Matthew Seaman
On Sat, May 15, 2004 at 01:51:40AM -0400, Matt Cyber Dog LaPlante wrote: I've inherited a FreeBSD 4.7 server as part of a system administration job.  Recently I noticed that the syslog files had stopped collecting data.  This includes /var/log/messages and /var/log/console among others.  Up

RE: FreeBSD 4.7 Syslogs

2004-05-15 Thread Matt \Cyber Dog\ LaPlante
- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Seaman Sent: Saturday, May 15, 2004 4:56 AM To: Matt Cyber Dog LaPlante Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD 4.7 Syslogs On Sat, May 15, 2004 at 01:51:40AM -0400, Matt Cyber Dog LaPlante wrote: I've inherited

RE: FreeBSD 4.7 Syslogs

2004-05-15 Thread JJB
, flags 4, from compname, msg syslogd: restart syslogd: restarted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Seaman Sent: Saturday, May 15, 2004 4:56 AM To: Matt Cyber Dog LaPlante Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD 4.7 Syslogs On Sat

RE: FreeBSD 4.7 Syslogs

2004-05-15 Thread Matt \Cyber Dog\ LaPlante
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JJB Sent: Saturday, May 15, 2004 4:04 PM To: Matt Cyber Dog LaPlante; 'Matthew Seaman'; [EMAIL PROTECTED] Subject: RE: FreeBSD 4.7 Syslogs Well since you are new to FBSD and since the syslogd -d commands shows that you do not have logging specified