Re: Stopping Less from creating Log Files
Lowell Gilbert writes: The secure mode disables log files, but it also changes several other behaviours, so you may not find it to be an improvement. The code supports changing those secure features separately, but only by editing the source; if you go that way, it will probably be much easier to use the ports version of the program instead of the base system's. Very good.Thanks. I looked up what secure mode does and I see what you mean. I will just have to try it and see if I need the ports package or not. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stopping Less from creating Log Files
Date: Mon, 11 Apr 2011 11:36:37 -0500 From: Martin McCormick mar...@dc.cis.okstate.edu Subject: Stopping Less from creating Log Files This is a minor problem but I use more to read Email messages from nmh. If one forgets what screen one is in, it is possible to start typing and create a log file of the message in which ever mailbox directory one is reading out of. The man page for more is actually linked to less even though FreeBSD has /usr/bin/more and less. There is only one executable -- it has two hard links, thus giving the alternate names. I even tried in the .mh_profile to call more with -Oo/dev/null but if you hit a key, the logfile prompt appears and any subsequent key strokes are part of the new file name. This really is only a minor nuisance because it creates junk files that then have to be removed from the directory. So, if there is a way to make more or less not write anything, it would be more or less appreciated. It is said: For every fool-proof system, there exists a sufficiently-determined fool capable of breaking it. We have a winner! For the named programs, more or less, anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stopping Less from creating Log Files
This is a minor problem but I use more to read Email messages from nmh. If one forgets what screen one is in, it is possible to start typing and create a log file of the message in which ever mailbox directory one is reading out of. The man page for more is actually linked to less even though FreeBSD has /usr/bin/more and less. I even tried in the .mh_profile to call more with -Oo/dev/null but if you hit a key, the logfile prompt appears and any subsequent key strokes are part of the new file name. This really is only a minor nuisance because it creates junk files that then have to be removed from the directory. So, if there is a way to make more or less not write anything, it would be more or less appreciated. Many thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stopping Less from creating Log Files
On Mon, Apr 11, 2011 at 11:36:37AM -0500, Martin McCormick wrote: This is a minor problem but I use more to read Email messages from nmh. If one forgets what screen one is in, it is possible to start typing and create a log file of the message in which ever mailbox directory one is reading out of. The man page for more is actually linked to less even though FreeBSD has /usr/bin/more and less. I even tried in the .mh_profile to call more with -Oo/dev/null but if you hit a key, the logfile prompt appears and any subsequent key strokes are part of the new file name. I think 'more' is just a link to 'less' anyway. The binaries are the same according to dif and cmp. (not what you were asking, but...) jerry This really is only a minor nuisance because it creates junk files that then have to be removed from the directory. So, if there is a way to make more or less not write anything, it would be more or less appreciated. Many thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stopping Less from creating Log Files
On 04/11/11 18:36, Jerry McAllister wrote:
On Mon, Apr 11, 2011 at 11:36:37AM -0500, Martin McCormick wrote:
This is a minor problem but I use more to read Email messages
from nmh. If one forgets what screen one is in, it is possible
to start typing and create a log file of the message in which
ever mailbox directory one is reading out of.
The man page for more is actually linked to less even
though FreeBSD has /usr/bin/more and less. I even tried in the
.mh_profile to call more with -Oo/dev/null but if you hit a key,
the logfile prompt appears and any subsequent key strokes are
part of the new file name.
I think 'more' is just a link to 'less' anyway. The binaries are
the same according to dif and cmp.
(not what you were asking, but...)
arthur@fileserver ls -li /usr/bin/{more,less}
44019002 -r-xr-xr-x 2 root wheel 139128 Feb 25 16:40 /usr/bin/less
44019002 -r-xr-xr-x 2 root wheel 139128 Feb 25 16:40 /usr/bin/more
They're hard linked.
The OP should check out the section on environment variables in the man
page. LESS and LESS_IS_MORE might help him.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stopping Less from creating Log Files
Martin McCormick mar...@dc.cis.okstate.edu writes: This is a minor problem but I use more to read Email messages from nmh. If one forgets what screen one is in, it is possible to start typing and create a log file of the message in which ever mailbox directory one is reading out of. The man page for more is actually linked to less even though FreeBSD has /usr/bin/more and less. I even tried in the .mh_profile to call more with -Oo/dev/null but if you hit a key, the logfile prompt appears and any subsequent key strokes are part of the new file name. This really is only a minor nuisance because it creates junk files that then have to be removed from the directory. So, if there is a way to make more or less not write anything, it would be more or less appreciated. The secure mode disables log files, but it also changes several other behaviours, so you may not find it to be an improvement. The code supports changing those secure features separately, but only by editing the source; if you go that way, it will probably be much easier to use the ports version of the program instead of the base system's. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
newsyslog.conf and Apache log files
Hello, I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org http://www.netmusician.org j...@netmusician.org mailto:j...@netmusician.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
Joe Auty j...@netmusician.org writes: Hello, I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? Don't use wildcards in newsyslog.conf. What's happening is httperror_log.2.bz2 gets rotated into httperror_log.2.baz2.1.bz2, because it matches the filename glob you specified. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
On 10/7/10 7:26 PM, Joe Auty wrote: Hi Joe, Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? Like Lowell wrote, don't use wildcards in newsyslog.conf. :-) I just react to this, because I spent quite some time after a storage change on why my machine was hanging at bootup on the newsyslog trimming and creating logfiles line. There was no good Google result that pointed me in the direction, hence my post now. In my case I made the same mistake as you on my Asterisk logfiles (which also don't have any extention). So after troubleshooting NFS and filesystem problems, I ran truss on newsyslog and found out about the nice tree newsyslog had built on my Asterisk logfiles. It wasn't hanging afterall, it was quite busy. :-) I just wrote three lines with the three filenames I wanted to rotate and since then it's fine. /Robin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
Lowell Gilbert wrote: Joe Auty j...@netmusician.org writes: Hello, I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? Don't use wildcards in newsyslog.conf. What's happening is httperror_log.2.bz2 gets rotated into httperror_log.2.baz2.1.bz2, because it matches the filename glob you specified. Aha! That makes sense... What alternatives are there then so that I don't have to type in log file paths for each of my virtually hosted domains? How about: /var/log/httpd/*_log would this work? -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org http://www.netmusician.org j...@netmusician.org mailto:j...@netmusician.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
newsyslog.conf and Apache log files
Joe Auty writes: I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? My advice would be to not use syslog. It's bee a while since I fixed this problen, but I remember reading Apache has ... issues ... with rotating logs using syslog/newsyslog. Instead I use sysutils/cronolog with: ErrorLog |/usr/local/sbin/cronolog /var/log/httpd-errors.%Y-%m.log TransferLog |/usr/local/sbin/cronolog /var/log/httpd-access.%Y-%m.log in httpd.conf. This gets me: -rw-r--r-- 1 rootwheel 11504 Dec 28 2009 httpd-access.2009-12.log -rw-r--r-- 1 rootwheel6380 Feb 3 2010 httpd-access.2010-02.log -rw-r--r-- 1 rootwheel1390 Mar 11 2010 httpd-access.2010-03.log -rw-r--r-- 1 rootwheel1439 Apr 23 16:06 httpd-access.2010-04.log -rw-r--r-- 1 rootwheel 904451 May 30 10:52 httpd-access.2010-05.log -rw-r--r-- 1 rootwheel 20279 Jun 29 12:29 httpd-access.2010-06.log -rw-r--r-- 1 rootwheel 1586153 Jul 28 07:50 httpd-access.2010-07.log -rw-r--r-- 1 rootwheel 164305 Aug 31 18:51 httpd-access.2010-08.log -rw-r--r-- 1 rootwheel 14294 Sep 9 08:19 httpd-access.2010-09.log -rw-r--r-- 1 rootwheel 3093989 Sep 9 08:19 httpd-access.log -rw-r--r-- 1 rootwheel 71655 Oct 7 2009 httpd-error.log -rw-rw-r-- 1 rootwheel3574 Oct 7 2009 httpd-errors.2009-10.log -rw-r--r-- 1 rootwheel1827 Nov 30 2009 httpd-errors.2009-11.log -rw-r--r-- 1 rootwheel1827 Jan 17 2010 httpd-errors.2010-01.log -rw-r--r-- 1 rootwheel5027 Feb 3 2010 httpd-errors.2010-02.log -rw-r--r-- 1 rootwheel 10562 Mar 25 2010 httpd-errors.2010-03.log -rw-r--r-- 1 rootwheel5471 Apr 23 16:05 httpd-errors.2010-04.log -rw-r--r-- 1 rootwheel 332035 May 30 10:52 httpd-errors.2010-05.log -rw-r--r-- 1 rootwheel 10817 Jun 29 12:29 httpd-errors.2010-06.log -rw-r--r-- 1 rootwheel 569109 Jul 28 07:50 httpd-errors.2010-07.log -rw-r--r-- 1 rootwheel 59928 Aug 31 18:51 httpd-errors.2010-08.log -rw-r--r-- 1 rootwheel5198 Sep 9 08:19 httpd-errors.2010-09.log in /var/log. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
Joe Auty j...@netmusician.org writes: Lowell Gilbert wrote: Joe Auty j...@netmusician.org writes: Hello, I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? Don't use wildcards in newsyslog.conf. What's happening is httperror_log.2.bz2 gets rotated into httperror_log.2.baz2.1.bz2, because it matches the filename glob you specified. Aha! That makes sense... What alternatives are there then so that I don't have to type in log file paths for each of my virtually hosted domains? How about: /var/log/httpd/*_log would this work? I was going to say I didn't have time to figure it out, but it only took me a couple of minutes of looking at the source to be (*kind of*) sure that your suggestion *will* work. It shouldn't take more than ten minutes to try it out, anyway. If that doesn't work for you, you could always try generating the newsyslog.conf file from a script. Or try one of the several other logfile-rotating programs. But I think your idea should be good. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
On Thu, Oct 7, 2010 at 11:25 AM, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Joe Auty j...@netmusician.org writes: Hello, I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? Don't use wildcards in newsyslog.conf. What's happening is httperror_log.2.bz2 gets rotated into httperror_log.2.baz2.1.bz2, because it matches the filename glob you specified. One alternative might be to use newsyslog's -a option to put the archived logs in a separate directory, where the glob won't find them. Unfortunately there doesn't seem to be a way to define this on a per-file or per-directory basis, so it would apply to *all* your logs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
Robert Huff roberth...@rcn.com writes: Joe Auty writes: I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? My advice would be to not use syslog. It's bee a while since I fixed this problen, but I remember reading Apache has ... issues ... with rotating logs using syslog/newsyslog. Those problems were a race condition between (Apache) closing the log file and (newsyslog) opening it to start compression. *How* the log rotation is done isn't really relevant (unless one sends the logs through pipes), but the only safe way is to shut down the server while the rotation is being done. You don't compress your logs, so it wouldn't affect you anyway. Joe does, so it could be an issue for him; the Apache documentation covers a number of options. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
07.10.2010 20:26, Joe Auty wrote: Hello, I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? /var/log/httpd/*_log would suffice. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and Apache log files
--On Thursday, October 07, 2010 16:08:23 -0400 Robert Huff roberth...@rcn.com wrote: Joe Auty writes: I have the following entry for dealing with my Apache log files: /var/log/httpd/* 644 2 * $M1D0 GBJ /var/run/httpd.pid 30 Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? This is what I use: /var/log/httpd-access.log 640 5 *$W0D04 Z /var/run/httpd.pid /var/log/httpd-error.log640 5 *$W0D00 Z /var/run/httpd.pid /var/log/rewrite_log640 5 *$W0D00 Z /var/run/httpd.pid And this is the results: # ls -lsa /var/log/httpd-* 279520 -rw-r- 1 root wheel 286062450 Oct 7 16:09 /var/log/httpd-access.log 26352 -rw-r- 1 root wheel 26960261 Oct 3 04:00 /var/log/httpd-access.log.0.gz 26720 -rw-r- 1 root wheel 27332026 Sep 26 04:00 /var/log/httpd-access.log.1.gz 37984 -rw-r- 1 root wheel 38845050 Sep 19 04:00 /var/log/httpd-access.log.2.gz 25632 -rw-r- 1 root wheel 26214452 Sep 5 04:00 /var/log/httpd-access.log.3.gz 24800 -rw-r- 1 root wheel 25364090 Aug 29 04:00 /var/log/httpd-access.log.4.gz 23568 -rw-r- 1 root wheel 24116870 Aug 22 04:00 /var/log/httpd-access.log.5.gz 1472 -rw-r- 1 root wheel1477939 Oct 7 16:07 /var/log/httpd-error.log 122 -rw-r- 1 root wheel 124058 Oct 3 00:00 /var/log/httpd-error.log.0.gz 140 -rw-r- 1 root wheel 141619 Sep 26 00:00 /var/log/httpd-error.log.1.gz 224 -rw-r- 1 root wheel 198696 Sep 19 00:00 /var/log/httpd-error.log.2.gz 150 -rw-r- 1 root wheel 153353 Sep 5 00:00 /var/log/httpd-error.log.3.gz 138 -rw-r- 1 root wheel 139720 Aug 29 00:00 /var/log/httpd-error.log.4.gz 114 -rw-r- 1 root wheel 116124 Aug 22 00:00 /var/log/httpd-error.log.5.gz 80 -rw-r--r-- 1 root wheel 80066 Oct 6 18:47 /var/log/httpd-ssl_request.log # ls -lsa /var/log/rewrite_log* 194672 -rw-r- 1 root wheel 199225770 Oct 7 16:07 /var/log/rewrite_log 17856 -rw-r- 1 root wheel 18260862 Oct 3 00:00 /var/log/rewrite_log.0.gz 18448 -rw-r- 1 root wheel 18873604 Sep 26 00:00 /var/log/rewrite_log.1.gz 26288 -rw-r- 1 root wheel 26899244 Sep 19 00:00 /var/log/rewrite_log.2.gz 17536 -rw-r- 1 root wheel 17935781 Sep 5 00:00 /var/log/rewrite_log.3.gz 16896 -rw-r- 1 root wheel 17278330 Aug 29 00:00 /var/log/rewrite_log.4.gz 16048 -rw-r- 1 root wheel 16402215 Aug 22 00:00 /var/log/rewrite_log.5.gz Your problem appears to be caused by file globbing. Since you use httpd/*, every file will be rotated, even ones that were previously rotated. So, newsyslogd keeps appending more and more bzs to the end of the filenames, just as you've told it to do. My advice would be to not use syslog. It's bee a while since I fixed this problen, but I remember reading Apache has ... issues ... with rotating logs using syslog/newsyslog. Instead I use sysutils/cronolog with: None here, and I've been rotating apache logs since 1.3.1* (now at 2.2.16 with numerous upgrades in between) using newsyslog without every seeing the problem that you describe. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
On 09/21/2010 10:17 PM, Len Conrad wrote: -- Original Message -- From: Ed Flecko edfle...@gmail.com Date: Tue, 21 Sep 2010 12:56:13 -0700 According to the FreeBSD website (http://www.freebsd.org/doc/handbook/outgoing-only.html), the easiest way to send mail only is to install the mail/ssmtp port. Does anyone have an example of a script or other method (maybe a cron script?) that would e-mail my log files to me daily? log files can be (too) huge as smtp DATA. I zip mine and use the mpack port to send the .zip file as MIME attachment. Len You could install the logrotate port /usr/ports/sysutils/logrotate and switch the logfiles you want to this instead of newsyslog For webserver error logs I use something like this scripts which runs from cron #!/bin/sh cd /home/www LOGFILES=`ls */logfiles/errorlog.txt` for i in $LOGFILES do if [ -s $i ] then tail -r -n 100 $i |mail -s $i email_address fi done DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
From owner-freebsd-questi...@freebsd.org Wed Sep 22 00:32:52 2010 Date: Wed, 22 Sep 2010 06:33:20 +0100 From: Bruce Cran br...@cran.org.uk To: Adam Vande More amvandem...@gmail.com Cc: Ed Flecko edfle...@gmail.com, freebsd-questions@freebsd.org Subject: Re: Software to SEND log files only? On Tue, 21 Sep 2010 15:16:35 -0500 Adam Vande More amvandem...@gmail.com wrote: That's pretty silly article if you ask me, sendmail is setup to that by default. just add something like this to cron: uuencode /path/to/logfile logfile | mail -s logfile yourem...@example.com Most mail servers will block sendmail's connections from a dynamic IP: the advantage to ssmtp is that it forwards mail to the ISP's server. *ONE* line in the sendmail config file (smarthost), and sendmail does the same thing. grin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
On Wed, 22 Sep 2010 06:33:20 +0100, Bruce Cran br...@cran.org.uk wrote: Most mail servers will block sendmail's connections from a dynamic IP: the advantage to ssmtp is that it forwards mail to the ISP's server. That's sadly true (mostly because of the amounts of spam produced by ordinary PCs on dynamic IPs). But sendmail has a fine solution for that, erm, problem: define(`SMART_HOST', `mx.foo.bar') It's often useful to have the ISP's MX handle that problem, as it usually has a static IP and is widely accepted. :-) This workaround makes it possible again to use basic techniques of communications that were common in the good days, as it should be. This way plain sendmail can be used. Maybe masquerading envelope is also needed, but I'm not entirely sure. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Software to SEND log files only?
According to the FreeBSD website (http://www.freebsd.org/doc/handbook/outgoing-only.html), the easiest way to send mail only is to install the mail/ssmtp port. Does anyone have an example of a script or other method (maybe a cron script?) that would e-mail my log files to me daily? Thank you, Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
On Tue, Sep 21, 2010 at 2:56 PM, Ed Flecko edfle...@gmail.com wrote: According to the FreeBSD website (http://www.freebsd.org/doc/handbook/outgoing-only.html), the easiest way to send mail only is to install the mail/ssmtp port. Does anyone have an example of a script or other method (maybe a cron script?) that would e-mail my log files to me daily? That's pretty silly article if you ask me, sendmail is setup to that by default. just add something like this to cron: uuencode /path/to/logfile logfile | mail -s logfile yourem...@example.com -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
-- Original Message -- From: Ed Flecko edfle...@gmail.com Date: Tue, 21 Sep 2010 12:56:13 -0700 According to the FreeBSD website (http://www.freebsd.org/doc/handbook/outgoing-only.html), the easiest way to send mail only is to install the mail/ssmtp port. Does anyone have an example of a script or other method (maybe a cron script?) that would e-mail my log files to me daily? log files can be (too) huge as smtp DATA. I zip mine and use the mpack port to send the .zip file as MIME attachment. Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
Date: Tue, 21 Sep 2010 12:56:13 -0700
From: Ed Flecko edfle...@gmail.com
To: freebsd-questions@freebsd.org
Subject: Software to SEND log files only?
According to the FreeBSD website
(http://www.freebsd.org/doc/handbook/outgoing-only.html), the easiest
way to send mail only is to install the mail/ssmtp port.
Does anyone have an example of a script or other method (maybe a cron
script?) that would e-mail my log files to me daily?
'mailing a file' is as simple as mail -s {subject} {addressee} file
multiple files: cat file1 file3 file2 |mail {adressee}
the FM will provide other swiches that may be useful.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
On Tue, 21 Sep 2010 15:16:35 -0500 Adam Vande More amvandem...@gmail.com wrote: That's pretty silly article if you ask me, sendmail is setup to that by default. just add something like this to cron: uuencode /path/to/logfile logfile | mail -s logfile yourem...@example.com Most mail servers will block sendmail's connections from a dynamic IP: the advantage to ssmtp is that it forwards mail to the ISP's server. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Software to SEND log files only?
On Wed, Sep 22, 2010 at 12:33 AM, Bruce Cran br...@cran.org.uk wrote: Most mail servers will block sendmail's connections from a dynamic IP: the advantage to ssmtp is that it forwards mail to the ISP's server. A small few, not most will do this IME. The larger issue is/was that some providers blocked port 25 from dynamic IP's. Regardless, it's easier to config sendmail as a smarthost with authorization, than it is a add yet another port IMO. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0-RELEASE-p12 bind9 log files not found
Hello,
I have setup FreeBSD recently, can somebody help me with one interesting
thing - Bind9 slave DNS server, everything is works great, but I got a
problem with extended logging of xfer, etc.
Bind9 started in chroot:
root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23
/usr/sbin/named -t /var/named -u bind
Configuration of logging channels from named.conf:
logging
{
channel xfer
{
file /var/named/var/log/xfer.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel lame
{
file /var/named/var/log/lame.log versions 2 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel config
{
file /var/named/var/log/conf.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel security
{
file /var/named/var/log/security.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
category xfer-in { xfer; };
category xfer-out { xfer; };
category notify { xfer; };
category lame-servers { lame; };
category config { config; };
category security { security; };
category default { default_syslog; default_debug; };
};
Next, I've create files in /var/named/var/log and chown them to bind:wheel
(cause of -u bind is defined above):
[po...@mgork23-gw /var/named/var/log]$ ls -la
total 4
drwxr-xr-x 2 bind wheel 512 May 30 16:09 .
drwxr-xr-x 6 root wheel 512 May 21 19:16 ..
-rw-r--r-- 1 bind wheel0 May 30 14:54 conf.log
-rw-r--r-- 1 bind wheel0 May 30 14:55 lame.log
-rw-r--r-- 1 bind wheel0 May 30 14:55 security.log
-rw-r--r-- 1 bind wheel0 May 30 14:54 xfer.log
But I get following messages in /var/log/messages:
May 30 16:27:42 srv named[31139]: starting BIND 9.4.2 -t /var/named -u bind
May 30 16:27:42 srv named[31139]: command channel listening on 127.0.0.1#953
May 30 16:27:42 srv named[31139]: command channel listening on ::1#953
May 30 16:27:42 srv named[31139]: logging channel 'xfer' file
'/var/named/var/log/xfer.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'lame' file
'/var/named/var/log/lame.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'config' file
'/var/named/var/log/conf.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'security' file
'/var/named/log/security.log': file not found
May 30 16:27:42 srv named[31139]: running
May 30 16:27:42 srv named[31139]: isc_log_open '/var/named/var/log/xfer.log'
failed: file not found
Changing permissions and putting log-files in different places (with
changing paths in named.conf of course) has no effect. I see that problem is
pretty silly but searching info about this doesn't say something special - I
still got file not found in /var/messages.
Maybe Iam don't understand where files must be placed, so, thanks in advance
for everybody who can explain how it works :)
VP
v.prokof...@gmail.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 14:50:31 Prokofyev Vladislav wrote:
Bind9 started in chroot:
root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23
/usr/sbin/named -t /var/named -u bind
Configuration of logging channels from named.conf:
logging
{
channel xfer
{
file /var/named/var/log/xfer.log versions 3 size
10m;
The named running chrooted has no clue about /var/named. You can either use
ducttape:
cd /var/named/var sudo ln -s .. named
or just strip /var/named from your config file, hence use /var/log/xfer.log.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
Prokofyev Vladislav wrote: Hello, I have setup FreeBSD recently, can somebody help me with one interesting thing - Bind9 slave DNS server, everything is works great, but I got a problem with extended logging of xfer, etc. Bind9 started in chroot: root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23 /usr/sbin/named -t /var/named -u bind [snip] Changing permissions and putting log-files in different places (with changing paths in named.conf of course) has no effect. I see that problem is pretty silly but searching info about this doesn't say something special - I still got file not found in /var/messages. Maybe Iam don't understand where files must be placed, so, thanks in advance for everybody who can explain how it works :) Don't know if this will help, but took a quick look at my box here at home and have the following in my rc.conf - but I don't have logging turned on with this machine. Note the last line. So the logs should be in /var/named/var/log named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike After adding these options on my system, named didn't start at boot. Manully attempt to start it via '/etc/rc.d/named start' brought to the following error: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named Anyway, thank you for time you've spent to write an answer. Hope this thread will help somebody who is stuck with the same problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 17:01:17 Prokofyev Vladislav wrote: The named running chrooted has no clue about /var/named. You can either use ducttape: cd /var/named/var sudo ln -s .. named or just strip /var/named from your config file, hence use /var/log/xfer.log. -- Mel This helped, thank you a lot. So, if I think in a right way, /usr/sbin/named with -t start option don't effect on any symlinks etc. Erm, yes or ... no. I suggest you read up on chroot. The short answer is that relative symlinks within the chroot environment work while absolute ones should take into the account the new filesystem root. I didn't pay attention to this cause named(8) says: -t directory Chroot to directory after processing the command line arguments, but before reading the configuration file. and have a look at what /etc/namedb really is: # ls -l /etc/namedb lrwxr-xr-x 1 root wheel 21 May 21 06:24 /etc/namedb - /var/named/etc/namedb And this demonstrates chroot a bit: # cp /rescue/ls /var/named/ # chroot /var/named /ls -l /etc/namedb total 1 drwxr-xr-x 2 53 0512 Feb 28 05:57 dynamic drwxr-xr-x 2 0 0512 May 15 13:42 master -rw-r--r-- 1 0 0 11714 May 15 14:40 named.conf -rw-r--r-- 1 0 0 2956 May 15 13:42 named.root -rw--- 1 53 0 97 Apr 18 10:29 rndc.key drwxr-xr-x 2 53 0512 May 30 11:21 slave Warning: This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance security on most systems; the way chroot(2) is defined allows a process with root privileges to escape a chroot jail. And I thought that all actions for proper work are made by named :) They are, you just need reference the right path, the one without /var/named, or use relative paths where the working directory is /etc/namedb. So one would get to /var/log using: file ../../var/log/xfer; -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
newsyslog.conf and large numbers of Log Files
Can newsyslog be made to handle large numbers of log files such as all the *.collect.log files produced in our mrtg directory? Each device produces a log of the polling session and those logs get huge very quickly. There are 498 such files and putting a separate line in /etc/newsyslog.conf for each file is an absurd idea as we are always adding and removing devices from our network. The other alternative is a shell script to run that would compress each file after renaming it, etc. That is not a problem, but newsyslog already does that at least on single files. I did try path/*.collect.log and nothing happened. Thanks for any ideas. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: newsyslog.conf and large numbers of Log Files
Martin McCormick wrote: Can newsyslog be made to handle large numbers of log files such as all the *.collect.log files produced in our mrtg directory? newsyslog.conf(5): G indicates that the specified logfile_name is a shell pat- tern, and that newsyslog(8) should archive all filenames matching that pattern using the other options on this line. See glob(3) for details on syntax and matching rules. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: newsyslog.conf and large numbers of Log Files
Matthew Seaman writes: G indicates that the specified logfile_name is a shell pat- tern, and that newsyslog(8) should archive all filenames matching that pattern using the other options on this line. See glob(3) for details on syntax and matching rules. I am sorry. It looks like I didn't look closely enough. Many thanks. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Renaming log files while archiving - newsyslog?
Hi, I want to set up automatic archiving of logfiles and thought about using the standard newsyslog for it. My problem though is that during archiving the logs should be renamed to something like basename.YY-MM-DD-HH-MM-SS so the archived files should contain the date/time when they have been archived. For example an original file of cisco.log should give cisco.07-02-07-23-55-00.log. Does anybody out there know if newsyslog is capable of this? If not - is there another program that can archive/rename logfiles in such a way? Thanks much in advance for your help, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Renaming log files while archiving - newsyslog?
Ewald Jenisch [EMAIL PROTECTED] writes:
I want to set up automatic archiving of logfiles and thought about
using the standard newsyslog for it.
My problem though is that during archiving the logs should be renamed
to something like basename.YY-MM-DD-HH-MM-SS so the archived
files should contain the date/time when they have been archived. For
example an original file of cisco.log should give
cisco.07-02-07-23-55-00.log.
Does anybody out there know if newsyslog is capable of this?
It isn't.
If not - is there another program that can archive/rename logfiles in
such a way?
I'm sure there is, but I don't know any offhand. It's awfully easy to
roll your own. You can even let newsyslog do the rotation and rename
the files it puts out (using their mtime for your stamp).
For example, I run the following on a monthly basis:
cd ${HOME}/Mail
filename=`date -v-1d '+sentmail.%Y-%m'`
mv outgoing-mail archive/$filename
It should probably check for an error on the cd command, but basically
that's all you need.
Be well.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Are there any log files which shows who is logging to a FreeBSD box and when?
Hi Can anyone tell? Are there any log files which shows who is logging to a FreeBSD box and when? If yes, where can one find them? -- Thanks! BR / vj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Are there any log files which shows who is logging to a FreeBSD box and when?
VeeJay wrote: Hi Can anyone tell? Are there any log files which shows who is logging to a FreeBSD box and when? If yes, where can one find them? The file /var/log/auth.log should contain all the information you are looking for. man syslog.conf and man syslogd for more information on customizing what you are logging. Cheers, Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SV: Are there any log files which shows who is logging to a FreeBSD boxand when?
Hi, cat /var/log/auth.log or tail -f /var/log/auth.log Kind regards Tim Från: [EMAIL PROTECTED] genom VeeJay Skickat: fr 2007-01-12 20:10 Till: [EMAIL PROTECTED]; FreeBSD-Questions Ämne: Are there any log files which shows who is logging to a FreeBSD boxand when? Hi Can anyone tell? Are there any log files which shows who is logging to a FreeBSD box and when? If yes, where can one find them? -- Thanks! BR / vj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Are there any log files which shows who is logging to a FreeBSD box and when?
hi, have a look at /var/log/auth.log (and also on utmp) VeeJay wrote: Hi Can anyone tell? Are there any log files which shows who is logging to a FreeBSD box and when? If yes, where can one find them? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Are there any log files which shows who is logging to a FreeBSD box and when?
On Jan 12, 2007, at 11:10 AM, VeeJay wrote: Can anyone tell? Are there any log files which shows who is logging to a FreeBSD box and when? If yes, where can one find them? Yes, see the last command or man wtmp... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Are there any log files which shows who is logging to a FreeBSD box and when?
login errors and successful logins are going to be in /var/log/auth.log to see who is currently or has ever logged in from the command line, try: finger(1) last(1) w(1) who(1) -g On 12/01/07, VeeJay [EMAIL PROTECTED] wrote: Hi Can anyone tell? Are there any log files which shows who is logging to a FreeBSD box and when? If yes, where can one find them? -- Thanks! BR / vj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Greg Albrecht ([EMAIL PROTECTED]) An Indie, Hip Hop and IDM Podcast: The Letter G http://theletterg.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cleaning out log files?
I've noticed that my /var partition, on a machine being used as a desktop, is about 80% full and would like to know what in it can safely be deleted, or if there is some accepted way to trim log files down with a cron job, etc. Thanks! Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cleaning out log files?
On Sunday 26 November 2006 12:37, Oliver Iberien wrote: I've noticed that my /var partition, on a machine being used as a desktop, is about 80% full and would like to know what in it can safely be deleted, or if there is some accepted way to trim log files down with a cron job, etc. Thanks! Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Oliver, Take a look at /etc/newsyslog.conf as it is designed just for rotating and removing log files lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cleaning out log files?
On Sunday 26 November 2006 18:37, Oliver Iberien wrote: I've noticed that my /var partition, on a machine being used as a desktop, is about 80% full and would like to know what in it can safely be deleted, or if there is some accepted way to trim log files down with a cron job, etc. Thanks! Are you sure it's the log files, they should be rotated automatically. Try running running du -md1 /var (as root). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cleaning out log files?
Check /etc/newsyslog.conf All log-files you like to have rotated, should be mentioned there. System owned logs are in there per default. du -k /var will tell you where your space is being consumed. Maybe your /var/mail/root is growing... How big is your /var anyway? Armin -- PUBBOX Postmaster + spam-killer. Free email addresses at http://pubbox.net/ On Sun, Nov 26, 2006 at 10:37:18AM -0800, Oliver Iberien wrote: I've noticed that my /var partition, on a machine being used as a desktop, is about 80% full and would like to know what in it can safely be deleted, or if there is some accepted way to trim log files down with a cron job, etc. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cleaning out log files?
Thank you! I knew something like that had to exist. It turns out there was a core dump I had not noticed. I had the idea of running ls -SlhR /var/ /.../var_contents.txt and looking for anything huge. Oliver On Sunday 26 November 2006 10:54, you wrote: Check /etc/newsyslog.conf All log-files you like to have rotated, should be mentioned there. System owned logs are in there per default. du -k /var will tell you where your space is being consumed. Maybe your /var/mail/root is growing... How big is your /var anyway? Armin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cleaning out log files? [top-posting corrected]
On Sunday 26 November 2006 10:54, you wrote: Check /etc/newsyslog.conf All log-files you like to have rotated, should be mentioned there. System owned logs are in there per default. du -k /var will tell you where your space is being consumed. Maybe your /var/mail/root is growing... How big is your /var anyway? Armin Thank you! I knew something like that had to exist. It turns out there was a core dump I had not noticed. I had the idea of running ls -SlhR /var/ /.../var_contents.txt and looking for anything huge. Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cleaning out log files?
On Sunday 26 November 2006 19:21, Oliver Iberien wrote: Thank you! I knew something like that had to exist. It turns out there was a core dump I had not noticed. I had the idea of running ls -SlhR /var/ /.../var_contents.txt and looking for anything huge. FreeBSD has some useful periodic scripts for keeping this kind of thing under control - most of which are off by default. You can see the defaults in /etc/defaults/periodic.conf and override them in /etc/periodic.conf For example: # 100.clean-disks daily_clean_disks_enable=NO # Delete files daily daily_clean_disks_files=[#,]* .#* a.out *.core *.CKP .emacs_[0-9]* daily_clean_disks_days=3# If older than this daily_clean_disks_verbose=YES # Mention files deleted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cleaning out log files? [top-posting corrected]
Oliver Iberien writes: It turns out there was a core dump I had not noticed. I had the idea of running ls -SlhR /var/ /.../var_contents.txt and looking for anything huge. Try this instead: du /var | sort -nr | head -n 25 | sendmail you Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
new file format for log files in 5x tree ??
Hello, I just upgraded a server of mine to the 5.4 release noticed that maillogs cron logs are now being zipped into bz2 compressed files. I know this is a stupid question but what do use on the system to unpack these files ? so i cn look at logs ... thank you -- Brent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new file format for log files in 5x tree ??
bunzip2 - Original Message - From: Brent [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, May 02, 2006 9:56 AM Subject: new file format for log files in 5x tree ?? Hello, I just upgraded a server of mine to the 5.4 release noticed that maillogs cron logs are now being zipped into bz2 compressed files. I know this is a stupid question but what do use on the system to unpack these files ? so i cn look at logs ... thank you -- Brent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new file format for log files in 5x tree ??
Brent wrote: Hello, I just upgraded a server of mine to the 5.4 release noticed that maillogs cron logs are now being zipped into bz2 compressed files. I know this is a stupid question but what do use on the system to unpack these files ? so i cn look at logs ... thank you -- Brent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] bzcat filename | less -Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new file format for log files in 5x tree ??
Brent wrote: Hello, I just upgraded a server of mine to the 5.4 release noticed that maillogs cron logs are now being zipped into bz2 compressed files. I know this is a stupid question but what do use on the system to unpack these files ? so i cn look at logs ... thank you -- Brent The file command is your friend, bash-2.05b# file /usr/log/auth.log.0.bz2 /usr/log/auth.log.0.bz2: bzip2 compressed data, block size = 900k bash-2.05b# man bzip2 NAME bzip2, bunzip2 - a block-sorting file compressor, v1.0.2 bzcat - decompresses files to stdout bzip2recover - recovers data from damaged bzip2 files etc. Check out man apropos and man man Three times when I first started using FreeBSD I got a response to a posted question that consisted solely of man something from John Polstra (the name drop is on purpose, I didn't know who was being so kind to me at the time, he was very patient. I was fortunate). Then I wised up and I started every evening after dinner, running through /bin /sbin /usr/bin and /usr/sbin. Put each program name through man and read what it said. Then I started looking through /etc Learned a lot, not enough, but a lot. Most of what you need to know is already on a Unix system. DAve -- This message was checked by forty monkeys and found to not contain any SPAM whatsoever. Your monkeys may vary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd log files
On Friday 31 March 2006 08:25, Logan McNaughton wrote: What log file stors things like system shutdown notices and that, I want to run root-tail in my icewm background, and Im looking for the right log file to show, i tried /var/log/messages, but it doesnt show shutdown notices, can anyone help me out? thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hey! check out /etc/syslog.conf. You can specifiy what you want to log where. For example you could choose a console instead of a file. cheers, Ben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd log files
What log file stors things like system shutdown notices and that, I want to run root-tail in my icewm background, and Im looking for the right log file to show, i tried /var/log/messages, but it doesnt show shutdown notices, can anyone help me out? thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd log files
What log file stors things like system shutdown notices and that, I want to It may depend on your setting, in my /var/log/messages I see things like: Mar 23 11:07:00 machine reboot: rebooted by root Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
monitoring apache log files real-time
Hi there, No response on the apache list. I hoping there is some good knowledge that can be gathered from this list. I have apache-1.3.34 on FreeBSD running with about 50 virtual hosts. I am wanting to monitor how much each site is using bandwidth and even better have real time monitoring so I can see who is getting a lot of hits. I have apachetop installed but really its only good for reading a few files at a time. I would like to be able to look at the overall usage of my apache server at one single point in time - hopefully real-time. Is there a package out there that suits my needs? hopefully open=source? Thanks in advance. cheers, Noah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot remove old log files
Hello. I am currently moving to a new log administration policy, the problem is that there are some old logs that I would like to delete but I can't, the error is the typical Operation not permitted although I am trying to do this as root, the file's permissions are ok and there are no special file flag activated or anything, any ideas? suckea# uname -a FreeBSD suckea.com 5.3-SECURITY FreeBSD 5.3-SECURITY #0: Wed Jul 20 06:22:23 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 mybox# ls -lo [snip] -rwx-- 1 root wheel - 78 Dec 6 15:00 auth.log.zzpKVF1 -rwx-- 1 root wheel - 78 Jan 3 05:00 auth.log.zzr4dZD -rwx-- 1 root wheel - 78 Jan 4 17:00 auth.log.zzyP5R0 mybox# rm -rf auth.log.* [snip] rm: auth.log.zzr4dZD: Operation not permitted rm: auth.log.zzyP5R0: Operation not permitted mybox# uname -a FreeBSD suckea.com 5.3-SECURITY FreeBSD 5.3-SECURITY #0: Wed Jul 20 06:22:23 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Thanks for your time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot remove old log files
On 2006-01-08 21:57, Paulino Calderon [EMAIL PROTECTED] wrote: Hello. I am currently moving to a new log administration policy, the problem is that there are some old logs that I would like to delete but I can't, the error is the typical Operation not permitted although I am trying to do this as root, the file's permissions are ok and there are no special file flag activated or anything, any ideas? suckea# uname -a FreeBSD suckea.com 5.3-SECURITY FreeBSD 5.3-SECURITY #0: Wed Jul 20 06:22:23 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 mybox# ls -lo [snip] -rwx-- 1 root wheel - 78 Dec 6 15:00 auth.log.zzpKVF1 -rwx-- 1 root wheel - 78 Jan 3 05:00 auth.log.zzr4dZD -rwx-- 1 root wheel - 78 Jan 4 17:00 auth.log.zzyP5R0 mybox# rm -rf auth.log.* [snip] rm: auth.log.zzr4dZD: Operation not permitted rm: auth.log.zzyP5R0: Operation not permitted Is the partition mounted read-write? Can you run ktrace on this command and post the output? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Cron not deleting log files
On Tue, 8 Mar 2005, Richard Mcintyre wrote: Thank you very much for your sarcastic comment, however, you must have read that far then stopped. The problem is not with the number of extra log files, the problem is that I cannot delete them. AT ALL. As far as 'my home-grown non-working method' of managing my log files, it doesn't exist. In that I had not modified any of the initial settings of /etc/newsyslog.conf or any other conf files. the only commands I ran on the system were the long string of chmod commands I listed. That seems strange, because the file name format doesn't look anything like what newsyslog normally does. This is what log files look like on my 5.3-RELEASE-p5 system: $ ls -lrt /var/log [snip...] -rw-r- 1 rootwheel 728 Mar 5 03:06 sendmail.st.0 -rw--- 1 rootwheel 5959 Mar 5 17:00 cron.1.bz2 -rw-r- 1 rootwheel 778 Mar 6 00:00 maillog.3.bz2 -rw-r--r-- 1 rootwheel 30735 Mar 6 00:00 daemon.3.bz2 -rw-r--r-- 1 rootwheel 34760 Mar 6 00:00 all.log.3.bz2 -rw-r--r-- 1 rootwheel 49601 Mar 7 00:00 all.log.2.bz2 -rw-r- 1 rootwheel 645 Mar 7 00:00 maillog.2.bz2 -rw-r--r-- 1 rootwheel 46138 Mar 7 00:00 daemon.2.bz2 -rw-r--r-- 1 rootwheel 16217 Mar 7 19:45 console.log -rw-r--r-- 1 rootwheel 72179 Mar 7 19:45 messages -rw--- 1 rootwheel 13227 Mar 7 19:45 auth.log -rw-r- 1 rootwheel 642 Mar 8 00:00 maillog.1.bz2 -rw-r--r-- 1 rootwheel 31980 Mar 8 00:00 daemon.1.bz2 -rw-r--r-- 1 rootwheel 35479 Mar 8 00:00 all.log.1.bz2 -rw--- 1 rootwheel 5453 Mar 8 10:00 cron.0.bz2 -rw-r--r-- 1 rootwheel 36777 Mar 9 00:00 daemon.0.bz2 -rw-r--r-- 1 rootwheel 41041 Mar 9 00:00 all.log.0.bz2 -rw-r- 1 rootwheel 644 Mar 9 00:00 maillog.0.bz2 -rw-r- 1 rootwheel 728 Mar 9 03:06 sendmail.st -rw-r- 1 rootwheel 2124 Mar 9 03:06 maillog -rw--- 1 rootwheel 34519 Mar 9 08:05 cron -rw-r--r-- 1 rootwheel167201 Mar 9 08:06 all.log *something's* messing with your log files. That they're all the same size is pretty odd too. Look around in /var/log/messages or /var/log/cron and see if anything looks related. -- David Fleck [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Cron not deleting log files
Richard Mcintyre wrote: # rm cron.zzuL4BB rm: cron.zzuL4BB: Operation not permitted Of course, the classic answer is a question in itself... Are you doing this as root? Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with Cron not deleting log files
All, I am having a problem. Back in December I installed FreeBSD5.3 onto a server and have just recently found some new time to 'play' with the settings etc. I think I know what happened but I'm not sure how to fix it. I currently have a 'large number' of auth.log.x and cron.xx files under /var/log. When I first installed I remember reading some advice on 'securing' FreeBSD a little and ran the following commands: # echo root /var/cron/allow echo root /var/at/at.allow # chmod o= /etc/crontab chmod o= /usr/bin/crontab chmod o= /usr/bin/at chmod o= /usr/bin/atq chmod o= /usr/bin/atrm chmod o= /usr/bin/batch chmod o= /etc/fstab chmod o= /etc/ftpusers chmod o= /etc/group chmod o= /etc/hosts chmod o= /etc/hosts.allow chmod o= /etc/hosts.equiv chmod o= /etc/hosts.lpd chmod o= /etc/inetd.conf chmod o= /etc/login.access chmod o= /etc/login.conf chmod o= /etc/newsyslog.conf chmod o= /etc/rc.conf chmod o= /etc/ssh/sshd_config chmod o= /etc/sysctl.conf chmod o= /etc/syslog.conf chmod o= /etc/ttys chmod o= /var/log chflags sappnd /var/log chflags sappnd /var/log/* chmod o= /usr/bin/users chmod o= /usr/bin/w chmod o= /usr/bin/who chmod o= /usr/bin/lastcomm chmod o= /usr/sbin/jls chmod o= /usr/bin/last chmod o= /usr/sbin/lastlogin chmod ugo= /usr/bin/rlogin chmod ugo= /usr/bin/rsh I believe that for some reason the Cron daemon was unable to copy the files properly when it was trying to turn them over. Now when I try to remove the files I get an error. Below is a small sample... Thanks in advance for your help. ~REM # rm cron.zzuL4BB rm: cron.zzuL4BB: Operation not permitted FreeBSD tco1.iaminsane.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 -rwxr- 1 root wheel 75 Jan 12 02:00 auth.log.zzcek12 -rwxr- 1 root wheel 76 Feb 17 23:00 auth.log.zzhTnRK -rwxr- 1 root wheel 76 Feb 13 02:00 auth.log.zziSwsY -rwxr- 1 root wheel 76 Feb 19 01:00 auth.log.zzkW0uv -rwxr- 1 root wheel 76 Feb 11 08:00 auth.log.zzkwJcT -rwxr- 1 root wheel 76 Jan 4 13:00 auth.log.zzkzLR4 -rwxr- 1 root wheel 76 Jan 15 03:00 auth.log.zzpMZnk -rwxr- 1 root wheel 76 Feb 26 01:00 auth.log.zzqHHQF -rwxr- 1 root wheel 75 Jan 10 05:00 auth.log.zzsUDaP -rwxr- 1 root wheel 76 Jan 5 01:00 auth.log.zzyMumT -rwxr- 1 root wheel 76 Jan 7 02:00 auth.log.zzzLgvw -rw--- 1 root wheel3464472 Mar 8 17:15 cron -rwxr- 1 root wheel 919147 Dec 29 18:00 cron.0 -rwxr- 1 root wheel 76 Dec 9 14:00 cron.z01GcNu -rwxr- 1 root wheel 76 Dec 18 20:00 cron.z0smBRG -rwxr- 1 root wheel 76 Dec 28 03:00 cron.z1POYdD -rwxr- 1 root wheel 76 Dec 16 17:00 cron.zvh7LvG -rwxr- 1 root wheel 76 Dec 19 10:00 cron.zvmZm3L -rwxr- 1 root wheel 76 Dec 27 19:00 cron.zvnEACt -rwxr- 1 root wheel 76 Dec 23 22:00 cron.zw9E9HU -rwxr- 1 root wheel 76 Dec 21 09:00 cron.zwJmzq5 -rwxr- 1 root wheel 76 Dec 18 13:00 cron.zwTOEch -rwxr- 1 root wheel 76 Dec 8 16:00 cron.zwn8Fgs -rwxr- 1 root wheel 76 Dec 16 00:00 cron.zzSAEOg -rwxr- 1 root wheel 76 Mar 8 16:54 cron.zzuL4BB -rw--- 1 root wheel 68 Mar 8 14:28 debug.log -rwxr- 1 root wheel 5944 Dec 6 03:01 dmesg.today -rw-r--r-- 1 root wheel 28028 Dec 5 21:51 lastlog -rw-r--r-- 1 root wheel 0 Nov 4 20:27 lpd-errs -rw-r- 1 root wheel2018303 Mar 8 14:29 maillog -rwxr- 1 root wheel 6479 Dec 8 00:00 maillog.0 -rwxr- 1 root wheel 59 Dec 7 00:00 maillog.z4Bh3Oh -rwxr- 1 root wheel 59 Dec 6 00:00 maillog.zFWlD9W -rwxr- 1 root wheel 59 Dec 8 00:00 maillog.zcjrODo -rw-r--r-- 1 root wheel 46520 Mar 8 17:19 messages -rwxr- 1 root wheel192 Dec 6 03:01 mount.today -rwxr- 1 root wheel 0 Mar 8 14:24 newfile -rw-r- 1 root network0 Nov 4 20:27 ppp.log -rw--- 1 root wheel 0 Nov 4 20:27 security -rw-r- 1 root wheel 0 Nov 4 20:27 sendmail.st -rwxr- 1 root wheel 0 Dec 5 22:00 sendmail.st.0 -rwxr- 1 root wheel 0 Dec 5 22:00 sendmail.st.zJ24IkB -rwxr- 1 root wheel 3721 Dec 6 03:01 setuid.today -rw-r- 1 root network0 Nov 4 20:27 slip.log -rw--- 1 root wheel310 Feb 11 17:19 userlog drwxr- 2 root bin 512 Mar 8 13:57 webmin -rw-r--r-- 1 root wheel 3168 Mar 8 15:34 wtmp -rw--- 1 root wheel 0 Nov 4 20:27 xferlog ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to
Re: Problems with Cron not deleting log files
On Tue, Mar 08, 2005 at 05:22:08PM -0500, Richard Mcintyre wrote: All, I am having a problem. Back in December I installed FreeBSD5.3 onto a server and have just recently found some new time to 'play' with the settings etc. I think I know what happened but I'm not sure how to fix it. I currently have a 'large number' of auth.log.x and cron.xx files under /var/log. Use newsyslog(8) and /etc/newsyslog.conf to manage your log files instead of your home-grown non-working method. -- Jonathan Chen [EMAIL PROTECTED] -- Lots of folks confuse bad management with destiny - Kin Hubbard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Cron not deleting log files
Jonathan Chen wrote: On Tue, Mar 08, 2005 at 05:22:08PM -0500, Richard Mcintyre wrote: All, I am having a problem. Back in December I installed FreeBSD5.3 onto a server and have just recently found some new time to 'play' with the settings etc. I think I know what happened but I'm not sure how to fix it. I currently have a 'large number' of auth.log.x and cron.xx files under /var/log. Use newsyslog(8) and /etc/newsyslog.conf to manage your log files instead of your home-grown non-working method. Thank you very much for your sarcastic comment, however, you must have read that far then stopped. The problem is not with the number of extra log files, the problem is that I cannot delete them. AT ALL. As far as 'my home-grown non-working method' of managing my log files, it doesn't exist. In that I had not modified any of the initial settings of /etc/newsyslog.conf or any other conf files. the only commands I ran on the system were the long string of chmod commands I listed. Thanks again, ~REM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with Cron not deleting log files
Jonathan Chen wrote: On Tue, Mar 08, 2005 at 05:22:08PM -0500, Richard Mcintyre wrote: All, I am having a problem. Back in December I installed FreeBSD5.3 onto a server and have just recently found some new time to 'play' with the settings etc. I think I know what happened but I'm not sure how to fix it. I currently have a 'large number' of auth.log.x and cron.xx files under /var/log. Use newsyslog(8) and /etc/newsyslog.conf to manage your log files instead of your home-grown non-working method. Thank you very much for your sarcastic comment, however, you must have read that far then stopped. The problem is not with the number of extra log files, the problem is that I cannot delete them. AT ALL. As far as 'my home-grown non-working method' of managing my log files, it doesn't exist. In that I had not modified any of the initial settings of /etc/newsyslog.conf or any other conf files. the only commands I ran on the system were the long string of chmod commands I listed. The point is that newsyslog will delete them for you. Just get the configuration right. There is no need to use any other cron job for this and that would probably be more difficult to get right. If you are having trouble manually deleting the log files, I don't have the original post info to get an idea of what is going on. jerry Thanks again, ~REM ___ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Setting up a syslog server to store Fortigate log files
Danny [EMAIL PROTECTED] writes: I have a Fortigate firewall which allows me to direct the logs to a remote host (syslog server). I am running FreeBSD 4.9R -- do I simply point my firewall to the IP of my server and the logs will automagically appear in /var/log? Not quite; by default, FreeBSD runs syslogd in secure mode, which doesn't accept messages from remote machines. rc.conf(5) allows you to specify your own flags for syslogd(8). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Setting up a syslog server to store Fortigate log files
On 30 Jan 2005 10:24:23 -0500, Lowell Gilbert [EMAIL PROTECTED] wrote: Danny [EMAIL PROTECTED] writes: I have a Fortigate firewall which allows me to direct the logs to a remote host (syslog server). I am running FreeBSD 4.9R -- do I simply point my firewall to the IP of my server and the logs will automagically appear in /var/log? Not quite; by default, FreeBSD runs syslogd in secure mode, which doesn't accept messages from remote machines. rc.conf(5) allows you to specify your own flags for syslogd(8). So, in theory, after I find out what flags to set with syslogd, I would then specify them in my rc.conf, and I would be off to the races (of remote logging)? Or do I edit syslog.conf? Thank you, ...D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Setting up a syslog server to store Fortigate log files
I have a Fortigate firewall which allows me to direct the logs to a remote host (syslog server). I am running FreeBSD 4.9R -- do I simply point my firewall to the IP of my server and the logs will automagically appear in /var/log? The Fortigate is asking for the IP, port, and if I want to store as CSV (I know; personal preference; not important). Sadly, I have never done this before, so please be gentle. :) Thank you, ...D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
strange log files ..
there are so many my private ip name log files present on my system ... my network ip scheme is 10.0.0. why is that ? log.0.0.0.0 log.10.0.0.225 log.smbd.old log.10.0.0.1log.10.0.0.23 lpd-errs log.10.0.0.108 log.10.0.0.23.old maillog log.10.0.0.109 log.10.0.0.234 maillog.0.bz2 log.10.0.0.11 log.10.0.0.236 maillog.1.bz2 log.10.0.0.110 log.10.0.0.237 maillog.2.bz2 log.10.0.0.111 log.10.0.0.240 maillog.3.bz2 log.10.0.0.118 log.10.0.0.240.old maillog.4.bz2 log.10.0.0.125 log.10.0.0.242 maillog.5.bz2 log.10.0.0.127 log.10.0.0.248 messages log.10.0.0.134 log.10.0.0.249 messages.0.bz2 log.10.0.0.138 log.10.0.0.25 messages.1.bz2 log.10.0.0.146 log.10.0.0.254 messages.2.bz2 log.10.0.0.150 log.10.0.0.26 mount.today log.10.0.0.153 log.10.0.0.28 ppp.log log.10.0.0.157 log.10.0.0.3samba log.10.0.0.157.old log.10.0.0.30 scrollkeeper.log log.10.0.0.16 log.10.0.0.31 security log.10.0.0.162 log.10.0.0.43 sendmail.st log.10.0.0.168 log.10.0.0.46 sendmail.st.0 log.10.0.0.181 log.10.0.0.47 sendmail.st.1 log.10.0.0.181.old log.10.0.0.5 setuid.today log.10.0.0.183 log.10.0.0.51 slip.log log.10.0.0.186 log.10.0.0.52 userlog log.10.0.0.187 log.10.0.0.53 wtmp log.10.0.0.189 log.10.0.0.56 xferlog log.10.0.0.19 log.10.0.0.67 = *º¤., ¸¸,.¤º*¨¨¨*¤ Allah-hu-Akber*º¤., ¸¸,.¤º*¨¨*¤ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange log files ..
log.10.0.0.x files are samba log. Each smb clients that connects to your samba instance gets its own log file. Are you running DHCP? Are you restricting access to your sambe server? For example are you denying access from the internet to samba? faisal gillani schrieb: there are so many my private ip name log files present on my system ... my network ip scheme is 10.0.0. why is that ? log.0.0.0.0 log.10.0.0.225 log.smbd.old log.10.0.0.1log.10.0.0.23 lpd-errs log.10.0.0.108 log.10.0.0.23.old maillog log.10.0.0.109 log.10.0.0.234 maillog.0.bz2 log.10.0.0.11 log.10.0.0.236 maillog.1.bz2 log.10.0.0.110 log.10.0.0.237 maillog.2.bz2 log.10.0.0.111 log.10.0.0.240 maillog.3.bz2 log.10.0.0.118 log.10.0.0.240.old maillog.4.bz2 log.10.0.0.125 log.10.0.0.242 maillog.5.bz2 log.10.0.0.127 log.10.0.0.248 messages log.10.0.0.134 log.10.0.0.249 messages.0.bz2 log.10.0.0.138 log.10.0.0.25 messages.1.bz2 log.10.0.0.146 log.10.0.0.254 messages.2.bz2 log.10.0.0.150 log.10.0.0.26 mount.today log.10.0.0.153 log.10.0.0.28 ppp.log log.10.0.0.157 log.10.0.0.3samba log.10.0.0.157.old log.10.0.0.30 scrollkeeper.log log.10.0.0.16 log.10.0.0.31 security log.10.0.0.162 log.10.0.0.43 sendmail.st log.10.0.0.168 log.10.0.0.46 sendmail.st.0 log.10.0.0.181 log.10.0.0.47 sendmail.st.1 log.10.0.0.181.old log.10.0.0.5 setuid.today log.10.0.0.183 log.10.0.0.51 slip.log log.10.0.0.186 log.10.0.0.52 userlog log.10.0.0.187 log.10.0.0.53 wtmp log.10.0.0.189 log.10.0.0.56 xferlog log.10.0.0.19 log.10.0.0.67 = *º¤., ¸¸,.¤º*¨¨¨*¤ Allah-hu-Akber*º¤., ¸¸,.¤º*¨¨*¤ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange log files ..
yes exactly .. i am only allowing 2-3 systems on my network to access samba others are all denied acess .. so these are some kind of security log files ?\ is there a way to disable them ? i mean stop making these files .. --- Daniel S. Haischt [EMAIL PROTECTED] wrote: log.10.0.0.x files are samba log. Each smb clients that connects to your samba instance gets its own log file. Are you running DHCP? Are you restricting access to your sambe server? For example are you denying access from the internet to samba? faisal gillani schrieb: there are so many my private ip name log files present on my system ... my network ip scheme is 10.0.0. why is that ? log.0.0.0.0 log.10.0.0.225 log.smbd.old log.10.0.0.1log.10.0.0.23 lpd-errs log.10.0.0.108 log.10.0.0.23.old maillog log.10.0.0.109 log.10.0.0.234 maillog.0.bz2 log.10.0.0.11 log.10.0.0.236 maillog.1.bz2 log.10.0.0.110 log.10.0.0.237 maillog.2.bz2 log.10.0.0.111 log.10.0.0.240 maillog.3.bz2 log.10.0.0.118 log.10.0.0.240.old maillog.4.bz2 log.10.0.0.125 log.10.0.0.242 maillog.5.bz2 log.10.0.0.127 log.10.0.0.248 messages log.10.0.0.134 log.10.0.0.249 messages.0.bz2 log.10.0.0.138 log.10.0.0.25 messages.1.bz2 log.10.0.0.146 log.10.0.0.254 messages.2.bz2 log.10.0.0.150 log.10.0.0.26 mount.today log.10.0.0.153 log.10.0.0.28 ppp.log log.10.0.0.157 log.10.0.0.3 samba log.10.0.0.157.old log.10.0.0.30 scrollkeeper.log log.10.0.0.16 log.10.0.0.31 security log.10.0.0.162 log.10.0.0.43 sendmail.st log.10.0.0.168 log.10.0.0.46 sendmail.st.0 log.10.0.0.181 log.10.0.0.47 sendmail.st.1 log.10.0.0.181.old log.10.0.0.5 setuid.today log.10.0.0.183 log.10.0.0.51 slip.log log.10.0.0.186 log.10.0.0.52 userlog log.10.0.0.187 log.10.0.0.53 wtmp log.10.0.0.189 log.10.0.0.56 xferlog log.10.0.0.19 log.10.0.0.67 = *º¤., ¸¸,.¤º*¨¨¨*¤ Allah-hu-Akber*º¤., ¸¸,.¤º*¨¨*¤ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] = *º¤., ¸¸,.¤º*¨¨¨*¤ Allah-hu-Akber*º¤., ¸¸,.¤º*¨¨*¤ __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange log files ..
those logs are containing traces from the smbd and nmbd process. Do you ahve a line this in your smb.conf? hosts allow = 192.168.0., 192.168.120. Additionally you should should change the directory which holds your samba log files: log file = /var/log/samba/log.%m because you do have a samba directory in /var/log. -- Do all of you three systems receive their IP etc. via DHCP? Do you run a DHCP daemon or some kinda router with a builtin DHCP server? faisal gillani schrieb: yes exactly .. i am only allowing 2-3 systems on my network to access samba others are all denied acess .. so these are some kind of security log files ?\ is there a way to disable them ? i mean stop making these files .. --- Daniel S. Haischt [EMAIL PROTECTED] wrote: log.10.0.0.x files are samba log. Each smb clients that connects to your samba instance gets its own log file. Are you running DHCP? Are you restricting access to your sambe server? For example are you denying access from the internet to samba? faisal gillani schrieb: there are so many my private ip name log files present on my system ... my network ip scheme is 10.0.0. why is that ? log.0.0.0.0 log.10.0.0.225 log.smbd.old log.10.0.0.1log.10.0.0.23 lpd-errs log.10.0.0.108 log.10.0.0.23.old maillog log.10.0.0.109 log.10.0.0.234 maillog.0.bz2 log.10.0.0.11 log.10.0.0.236 maillog.1.bz2 log.10.0.0.110 log.10.0.0.237 maillog.2.bz2 log.10.0.0.111 log.10.0.0.240 maillog.3.bz2 log.10.0.0.118 log.10.0.0.240.old maillog.4.bz2 log.10.0.0.125 log.10.0.0.242 maillog.5.bz2 log.10.0.0.127 log.10.0.0.248 messages log.10.0.0.134 log.10.0.0.249 messages.0.bz2 log.10.0.0.138 log.10.0.0.25 messages.1.bz2 log.10.0.0.146 log.10.0.0.254 messages.2.bz2 log.10.0.0.150 log.10.0.0.26 mount.today log.10.0.0.153 log.10.0.0.28 ppp.log log.10.0.0.157 log.10.0.0.3 samba log.10.0.0.157.old log.10.0.0.30 scrollkeeper.log log.10.0.0.16 log.10.0.0.31 security log.10.0.0.162 log.10.0.0.43 sendmail.st log.10.0.0.168 log.10.0.0.46 sendmail.st.0 log.10.0.0.181 log.10.0.0.47 sendmail.st.1 log.10.0.0.181.old log.10.0.0.5 setuid.today log.10.0.0.183 log.10.0.0.51 slip.log log.10.0.0.186 log.10.0.0.52 userlog log.10.0.0.187 log.10.0.0.53 wtmp log.10.0.0.189 log.10.0.0.56 xferlog log.10.0.0.19 log.10.0.0.67 = *., ,.** Allah-hu-Akber*., ,.** __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] = *., ,.** Allah-hu-Akber*., ,.** __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange log files ..
yes i do use the host allow function .. no i dont use dhcp anywhere on my network .. i like static ip assingment , thanks for the reply sir --- Daniel S. Haischt [EMAIL PROTECTED] wrote: those logs are containing traces from the smbd and nmbd process. Do you ahve a line this in your smb.conf? hosts allow = 192.168.0., 192.168.120. Additionally you should should change the directory which holds your samba log files: log file = /var/log/samba/log.%m because you do have a samba directory in /var/log. -- Do all of you three systems receive their IP etc. via DHCP? Do you run a DHCP daemon or some kinda router with a builtin DHCP server? faisal gillani schrieb: yes exactly .. i am only allowing 2-3 systems on my network to access samba others are all denied acess .. so these are some kind of security log files ?\ is there a way to disable them ? i mean stop making these files .. --- Daniel S. Haischt [EMAIL PROTECTED] wrote: log.10.0.0.x files are samba log. Each smb clients that connects to your samba instance gets its own log file. Are you running DHCP? Are you restricting access to your sambe server? For example are you denying access from the internet to samba? faisal gillani schrieb: there are so many my private ip name log files present on my system ... my network ip scheme is 10.0.0. why is that ? log.0.0.0.0 log.10.0.0.225 log.smbd.old log.10.0.0.1log.10.0.0.23 lpd-errs log.10.0.0.108 log.10.0.0.23.old maillog log.10.0.0.109 log.10.0.0.234 maillog.0.bz2 log.10.0.0.11 log.10.0.0.236 maillog.1.bz2 log.10.0.0.110 log.10.0.0.237 maillog.2.bz2 log.10.0.0.111 log.10.0.0.240 maillog.3.bz2 log.10.0.0.118 log.10.0.0.240.old maillog.4.bz2 log.10.0.0.125 log.10.0.0.242 maillog.5.bz2 log.10.0.0.127 log.10.0.0.248 messages log.10.0.0.134 log.10.0.0.249 messages.0.bz2 log.10.0.0.138 log.10.0.0.25 messages.1.bz2 log.10.0.0.146 log.10.0.0.254 messages.2.bz2 log.10.0.0.150 log.10.0.0.26 mount.today log.10.0.0.153 log.10.0.0.28 ppp.log log.10.0.0.157 log.10.0.0.3 samba log.10.0.0.157.old log.10.0.0.30 scrollkeeper.log log.10.0.0.16 log.10.0.0.31 security log.10.0.0.162 log.10.0.0.43 sendmail.st log.10.0.0.168 log.10.0.0.46 sendmail.st.0 log.10.0.0.181 log.10.0.0.47 sendmail.st.1 log.10.0.0.181.old log.10.0.0.5 setuid.today log.10.0.0.183 log.10.0.0.51 slip.log log.10.0.0.186 log.10.0.0.52 userlog log.10.0.0.187 log.10.0.0.53 wtmp log.10.0.0.189 log.10.0.0.56 xferlog log.10.0.0.19 log.10.0.0.67 = *º¤., ¸¸,.¤º*¨¨¨*¤ Allah-hu-Akber*º¤., ¸¸,.¤º*¨¨*¤ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] = *º¤., ¸¸,.¤º*¨¨¨*¤ Allah-hu-Akber*º¤., ¸¸,.¤º*¨¨*¤ __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] = *º¤., ¸¸,.¤º*¨¨¨*¤ Allah-hu-Akber*º¤., ¸¸,.¤º*¨¨*¤ __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to processi log files before rotation.
2 questions ... 1. Where is the right, or standard place to save shell scripts that I want to use for administrative, or any other tasks. Some place on the path I suppose. 2. I'd like to process my maillog and maillog.*.gz files just before the maillog it is rotated into maillog.1.gz and maillog.7.gz is discarded. I've written a couple of simple scripts to process the files and report the number total number of messages blocked with the DNSBL filters for today and the last 7 days, as well as the numbers for each of the DNSBL lists that I use. It also processes the maillog file and produces a total number blocked for each user and emails that and a list of the messages blocked to that user so that the user can check to make sure that they are not missing good email. I'd like to schedule the DNSBL status scripts to run every night just before the maillog rotation happens. I've found where in the /etc/crontab the log file rotation is scheduled, but I don't know if there is a way to ensure that my status scripts start, and run to completion before the logfile rotation starts. As a test I added a couple of lines to run every 2 minutes to see what order they executed in and found that the order of the lines in crontab doesn't guarantee order of execution ... or at least completion of the commands. The commands I added were more or less as follows: */2 * * * * root /root/dnsblstat */2 * * * * root mail -s test line 1 my_email_addr */2 * * * * root mail -s test line 2 my_email_addr What I found was that the dnsblstat never completed before the two following email commands, and sometimes the test line 2 email came in before the test line 1. As a brute force approach, I could schedule the dnsblstat to run some number of minutes before midnight, to make sure it completed before the log files were rotated out from under it, but then I might miss a few discards, and I wanted to show each user every email that was discarded. A different approach would be to process the maillog.1.gz file after it is created, and to collect statistics for today and the last 6 days instead of today and the last 7 days. I sure this is a standard problem with a correct solution, so how do you guys handle it? Thanks, Cla. (sorry for the verbosity) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fw: Rewriting long URIs from viruses... shortening log files
Purl Gurl (in alt.apache.configuration) wrote: tz wrote: (snipped) Running Apache/1.3.27 (Unix) here. Excellent. Apache 1.3.27 is the best version of all Apache releases. Next two, .28 and .29 have some bugs. Is this true? I very much doubt it. Since I recently upgraded to 1.3.29 myself (on FreeBSD 4.9R-p3), it doesn't hurt to ask, though. Thanks, - Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fw: Rewriting long URIs from viruses... shortening log files
On Thu, Apr 08, 2004 at 10:50:33AM +, Mark wrote: Purl Gurl (in alt.apache.configuration) wrote: tz wrote: Running Apache/1.3.27 (Unix) here. Excellent. Apache 1.3.27 is the best version of all Apache releases. Next two, .28 and .29 have some bugs. Is this true? I very much doubt it. Since I recently upgraded to 1.3.29 myself (on FreeBSD 4.9R-p3), it doesn't hurt to ask, though. It's not in agreement with what it says on http://httpd.apache.org/. apache-1.3.29 is a security release, as well as being a bug fix release. The Apache Software Foundation is not shy about admitting mistakes or shortcomings: if they felt that an older release was substantially better for most people to run, that information would be plastered all over their front page. There is a bug to do with mod_usertrack and the CookieName directive which is a current issue in the latest versions of apache. However, it's something that will only affect a few apache users, and there's a simple work-around. It's not so significant they've produced a new release right away, nor is it anything like as important as the buffer overflow fixed with the release of 1.3.29, exploitation of which could allow an attacker to DoS your server or even run arbitrary code upon it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: apache log files rotation
Dave McCammon wrote: --- fbsd_user [EMAIL PROTECTED] wrote: Can apache logs be rotated by /etc/newsyslog.conf? If not, how is it normally done? ___ Here is the relevent portion of my newsyslog.conf /var/log/httpd-access.log 640 14*$D0 Z /var/run/httpd.pid /var/log/httpd-error.log 640 14*$D0 Z /var/run/httpd.pid man newsyslog for more info on the fields. Just a hint in case you plan on running a web statistics program over the access log: add 'B' to the flags column for 'httpd-access.log', resulting in 'BZ'. This will omit the 'logfile turned over due to ...' lines generated by 'newsyslog', which the statistics program may otherwise complain about. Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers [EMAIL PROTECTED] | http://www.escapebox.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
apache log files rotation
Can apache logs be rotated by /etc/newsyslog.conf? If not, how is it normally done? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apache log files rotation
* fbsd_user [EMAIL PROTECTED] [20040303 17:14]: wrote: Can apache logs be rotated by /etc/newsyslog.conf? If not, how is it normally done? You may need to send apache SIGUSR1 (signal 30) to tell it to reopen its logfiles. I do this with squid but haven't tried with apache.. There is no harm in trying, you know? It wouldn't blow your box ;) /path/to/logfile www:www 644 7 * @T00 J /path/to/apache/pid 30 -Wash http://www.netmeister.org/news/learn2quote.html -- +==+ |\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED] Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ One of the lessons of history is that nothing is often a good thing to do and always a clever thing to say. -- Will Durant ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apache log files rotation
--- fbsd_user [EMAIL PROTECTED] wrote: Can apache logs be rotated by /etc/newsyslog.conf? If not, how is it normally done? ___ Here is the relevent portion of my newsyslog.conf /var/log/httpd-access.log 640 14*$D0 Z /var/run/httpd.pid /var/log/httpd-error.log 640 14*$D0 Z /var/run/httpd.pid man newsyslog for more info on the fields. __ Do you Yahoo!? Yahoo! Search - Find what youre looking for faster http://search.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apache log files rotation
fbsd_user wrote: Can apache logs be rotated by /etc/newsyslog.conf? If not, how is it normally done? Hello, Apart from what has already been said, you might also want to check http://www.freebsddiary.org/rotatelogs.php for more details. Dejan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
log files
How can I find the path to my log files? I am on a windows xp client and I need to find the path to the log files on my freebsd 4.7 web server. We are both on the same network. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log files
On Fri, Feb 20, 2004 at 09:29:08AM -0800, Derek Burns / Bend-Pak wrote: How can I find the path to my log files? I am on a windows xp client and I need to find the path to the log files on my freebsd 4.7 web server. We are both on the same network. The logfile path for apache is configured in the httpd.conf - /usr/local/etc/apache/httpd.conf by default. You could check there. The default httpd-access|error logfiles are placed in /var/log/httpd-access|error.log for apache, although if you're running a vhost your custom logfile might be placed somewhere else. In short - ask the admin of the httpd server. :P -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ http://jez.hancock-family.com/ - Another FreeBSD Diary http://ipfwstats.sf.net/- ipfw peruser traffic logging ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log files
Derek Burns / Bend-Pak wrote: How can I find the path to my log files? I am on a windows xp client and I need to find the path to the log files on my freebsd 4.7 web server. We are both on the same network. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You indeed are on a Windows client; please wrap text at 80 characters for those on text-only MUA's. ;-) Most logs are in /var/log. Some configurations of Apache (you are running Apache?) store logs in other places --- you can check your httpd.conf file to see where. You have SSH access, I presume? (Seems like you asked about this recently.) Log in via SSH, and open your files in your editor of choice. For example: $ee /var/log/httpd-error.log ee could be pico, nano, vi, vim, whatever... HTH, Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
log files
Sorry, I know where the log files themselves are, What I am trying to do is get them to report the browsing info as well as the referrer info. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log files
On Fri, Feb 20, 2004 at 10:45:04AM -0800, Derek Burns / Bend-Pak wrote: Sorry, I know where the log files themselves are, What I am trying to do is get them to report the browsing info as well as the referrer info. You'll have better luck if you make your replies on a given topic in the same thread, rather than as a new thread. For those whose mail clients support threading it helps to organize things. If I understand your question, then you should take a look at: http://httpd.apache.org/docs/logs.html Specifically take a look at the LogFormat directive in the httpd.conf file. Nathan -- gpg --keyserver pgp.mit.edu --recv-keys D8527E49 pgp0.pgp Description: PGP signature
Re: Can't remember how to read binary log files
On Wed, Feb 05, 2003 at 08:40:07PM -0800, Nathan Kinkade wrote: On Wed, Feb 05, 2003 at 07:49:53PM -0500, Louis LeBlanc wrote: Sorry for the OT question, but how does one view the contents of the binary logfiles? I'm referring specifically to /var/log/sendmail.st and /var/log/wtmp. I've looked in the syslog manpages and can't seem to find it. Thanks Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ You can read: utmp with `w` or `who` wtmp with `last` not sure about sendmail.st. mailstats(8) Cheers, Matthew PS. Not to be confused with the mailstat command: % mailstat Most people don't type their own logfiles; but, what do I care? -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Can't remember how to read binary log files
# [EMAIL PROTECTED] / 2003-02-06 08:48:20 +: PS. Not to be confused with the mailstat command: % mailstat Most people don't type their own logfiles; but, what do I care? mailstat? what's that? I don't have it on any of my machines. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Can't remember how to read binary log files
On Thu, 6 Feb 2003, Roman Neuhauser wrote: # [EMAIL PROTECTED] / 2003-02-06 08:48:20 +: PS. Not to be confused with the mailstat command: % mailstat Most people don't type their own logfiles; but, what do I care? mailstat? what's that? I don't have it on any of my machines. You won't have it unless you've installed /usr/ports/mail/procmail. It's a script procmail uses to show which folders it has sorted your mail into. Dru To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Can't remember how to read binary log files
On 2003-02-05 20:40, Nathan Kinkade [EMAIL PROTECTED] wrote: On Wed, Feb 05, 2003 at 07:49:53PM -0500, Louis LeBlanc wrote: Sorry for the OT question, but how does one view the contents of the binary logfiles? I'm referring specifically to /var/log/sendmail.st and /var/log/wtmp. I've looked in the syslog manpages and can't seem to find it. You can read: utmp with `w` or `who` wtmp with `last` not sure about sendmail.st. Try running: # hoststat The documentation for hoststat is sendmail(8), and it's use/setup is explained in /usr/share/sendmail/cf/README. Look for the definition of STATUS_FILE in /usr/share/sendmail/cf/README and /usr/share/sendmail/cf/ostype/freebsd4.m4 for details. - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Can't remember how to read binary log files
Sorry for the OT question, but how does one view the contents of the binary logfiles? I'm referring specifically to /var/log/sendmail.st and /var/log/wtmp. I've looked in the syslog manpages and can't seem to find it. Thanks Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ From the moment I picked your book up until I put it down I was convulsed with laughter. Some day I intend reading it. -- Groucho Marx, from The Book of Insults To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Can't remember how to read binary log files
On Wed, Feb 05, 2003 at 07:49:53PM -0500, Louis LeBlanc wrote: Sorry for the OT question, but how does one view the contents of the binary logfiles? I'm referring specifically to /var/log/sendmail.st and /var/log/wtmp. I've looked in the syslog manpages and can't seem to find it. Thanks Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ You can read: utmp with `w` or `who` wtmp with `last` not sure about sendmail.st. Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc msg18197/pgp0.pgp Description: PGP signature
Re: log files
I think I made a boo boo. I deleted all the files from var/log thinking I would have clean logs. Well, I rebooted but some of the files never reapeared. I made a back up just in case. Can I expect any problems in the future? Problems like no logs being writen maybe. Some things take the absense of a log file as a signal to not write log entries. I doubt that anything critical does it that way. What is the best way to start off with new logs - I'm experimenting with different things? Thus, trying to get more in touch with my new friend. Some of the files reappeared. In general is this a good way of starting off from fresh? What we usually do is: first observe the ownership (UID and GID) and the permissions on the log file. Then mv(1) the file to an alternate name, usually with the date in the name and either touch(1) the file and fix up the owner and permissions or do something like cp(1) /dev/null to the name and fix up owners and permissions. I won't guarantee that will cover all situations, and maybe it is a little crude(??) but it seems to work. We have lots of things that roll over logs using this procedure by age or by size of the log file. We use a cron(8) job to check them periodically. I think some things also have built-in checks for log file size. jerry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
log files
I think I made a boo boo. I deleted all the files from var/log thinking I would have clean logs. Well, I rebooted but some of the files never reapeared. I made a back up just in case. Can I expect any problems in the future? What is the best way to start off with new logs - I'm experimenting with different things? Thus, trying to get more in touch with my new friend. Some of the files reappeared. In general is this a good way of starting off from fresh? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: log files
At 09:06 PM 7/21/2002 -0600, Grant Cooper wrote: I think I made a boo boo. I deleted all the files from var/log thinking I would have clean logs. Well, I rebooted but some of the files never reapeared. I made a back up just in case. Can I expect any problems in the future? You should touch all of the files, else syslog won't log to them when it is restarted. What is the best way to start off with new logs - I'm experimenting with different things? Thus, trying to get more in touch with my new friend. Some of the files reappeared. In general is this a good way of starting off from fresh? newsyslog(8) is designed to rotate your system logs. Man it and see. -- Christopher Schulte http://www.schulte.org/ Do not un-munge my @nospam.schulte.org email address. This address is valid. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
