From: Richard Adams <pa3gcu@zeelandnet.nl>
To: Chris Rose <offline@shaw.ca>, linux-newbie@vger.kernel.org
Subject: Re: Logging
Date: Wed, 10 Apr 2002 18:23:33 +0000 [thread overview]
Message-ID: <02041018233304.00302@unix.pa3gcu> (raw)
In-Reply-To: <5.1.0.14.0.20020410003520.0352ef78@shawmail.ed.shawcable.net>
On Wednesday 10 April 2002 06:36, Chris Rose wrote:
> >Why would one want to ue a fancy program to read a simple text file, the
> >program less allows the use of a search engine, hit the '/' key and a
> > slash will appier at the bottom left of the screen, type a word to look
> > for, then hit enter, to repeat hit the slash again and press enter or
> > simply hit the space bar, the found word is highlighted.
>
> i think you're missing the point - what i'm looking for is not, per se, the
> mechanism used to read the log, so much as i'm looking for the means to
> make sense of what i'm seeing, and also which log files/settings of the
> daemon will provide me with stats on uploads/downloads from my ftp site.
I dont think i am, i meant what i said, what i can tell you futher is that
proftp.log does not really reveal much infomation at all, its "xferlog" in
/var/log that tells all, 'man xferlog' will explain all there is to be known.
Just in case you may read my mail as being prudent here is what profftp log
shows.
Aug 05 15:16:02 unix.pa3gcu proftpd[3839]
Date and time i am sure we all now what that is, unix.pa3gcu = the server
name, proftpd[389] is the process number as would be shown by 'ps ax' when
the connection was presant. Further on the same line in the log one would see;
unix.pa3gcu.ampr.org (192.168.1.160[192.168.1.160]): USER pa3gcu: Login
successful
unix.pa3gcu.ampr.org is the fullservername (192.168.1.160[192.168.1.160]): is
the IP# of the remote computer who just opened the ftp connect,
USER: pa3gcu = the user who logged in, that could be ftp or guest when
anoymous is used, Login succesful means a valid passwd was used.
Any discrepancy's would be logged as well as the last entry on the line.
No more info is given, you now would refer to xferlog to get details of what
was done in that connection.
See 'man xferlog' to get all the details on those entries.
I trust i have not missed the point in your eyes this time...
>
>
> Chris Rose
> ==========
> 1952 - 2001 = 42
--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-04-10 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 5:46 Logging Chris Rose
2002-04-10 6:08 ` Logging Richard Adams
2002-04-10 6:36 ` Logging Chris Rose
2002-04-10 18:23 ` Richard Adams [this message]
2002-04-12 12:50 ` Compaq Armada 100S DFW II
2002-04-12 16:04 ` Brian Jung Myeng Lee
2002-04-14 20:18 ` DFW II
2002-04-15 6:17 ` Richard Adams
-- strict thread matches above, loose matches on Subject: below --
2003-12-29 22:43 logging John T. Williams
2003-12-30 2:39 ` logging caszonyi
2003-12-30 2:44 ` logging Ray Olszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02041018233304.00302@unix.pa3gcu \
--to=pa3gcu@zeelandnet.nl \
--cc=linux-newbie@vger.kernel.org \
--cc=offline@shaw.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox