You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(13) |
Jul
(5) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: chiluveru s. <csn...@gm...> - 2013-03-16 14:50:11
|
Hi, I've just learned about the water crisis and would be grateful if you could spend a few minutes to help solve it: https://waterforward.charitywater.org/AMmPol6c Thanks, chiluveru -- the charity: water team WaterForward, 387 Tehama Street, San Francisco, CA 94103, USA. Click here to unsubscribe: https://waterforward.charitywater.org/opt_out?token=AMmPol6c&email=twincling-tacos%40lists.sourceforge.net |
From: Dropbox <no-...@dr...> - 2010-06-16 14:07:18
|
We're excited to let you know that Snehith Chiluveru has invited you to Dropbox! Snehith Chiluveru has been using Dropbox to sync and share files online and across computers, and thought you might want it too. Visit http://www.dropbox.com/link/20.mb-SzsXFbI/NjIyMjU5NzMxNw to get started. - The Dropbox Team ____________________________________________________ To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/73c424a388ad/twincling-tacos%40lists.sourceforge.net |
From: Chiluveru S. <csn...@gm...> - 2009-09-02 16:16:53
|
Hello I am creating a birthday calendar for myself. Can you please click on the link below and enter your birthday for me? http://www.birthdayalarm.com/bd2/80006071a12201696b1478366349c573738767d1386 Chiluveru |
From: Saifi K. <sai...@tw...> - 2009-08-05 06:39:57
|
Hi Yashwanth / Snehith: there is no need for any database. you'll process the input from the log files and write out a single file. If you need to do staging anywhere, it should either be . in memory datastructures (eg hash) . on-disk staging file Hope this helps. thanks Saifi. http://twitter.com/saifikhan |
From: Saifi K. <sai...@tw...> - 2009-08-04 15:35:03
|
On Tue, 4 Aug 2009, chiluveru snehith wrote: > hi saifi > > For finding unique number of clients in a particular log file ,We have to > find unique IP address in a particular log . > is there any need of using database to store the > variables in our LOGANALYSER project. > We have to store all IP addresses and then find the unique one's. > if we have to use a database which one do you suggest. > > thanks > snehith > Why do you need a database ? thanks Saifi. http://twitter.com/saifikhan |
From: Siddu <sid...@gm...> - 2009-07-16 15:41:27
|
Hi all, Before i start to write i would be glad to know if there is any pattern followed in presenting MOM . Incase if there is any please let me know . Below i present the mom about the Twincling PPPConfigurator discussion happened on sunday 12/07/09 at tiwari's The list of objectives involved in building Twincling PPPConfigurator are listed below Design and Develop a Tacos PERL module that provides the following functionality. 1. List the active interfaces (ACM - Abstract Control Machine (Linux), BSD ). 2. Detect the available connected modems. 3. Create ppp configuration for a given connection. 4. Validate existing ppp settings. 5. test (connect/disconnect) ppp settings for a connection. 6. Validate wvdial.conf 7. Migrate wvdial.conf to ppp settings. 8. Display connection statistics 9. Generate report (Service provider - modem - connection - statistics) 10. Must work with FreeBSD kernel 7.2+ and 8.0 11. Must work with Linux kernel 2.6.16+. 12. First set of devices to target are those available in Indian market - TataIndicom Plug2Surf, Photon+, Reliance ZTE, Cellphone as a modem. Currently myself will be focusing on action items 1, 2 ,10 and 11 . (ie) able to list active interfaces and detect the available connected modems on both BSD kernel 7.2+ and 8.0 and Linux Kernel 2.6.16+ Technologies involved 1. Perl :) 2. Compile and Build Linux (2.6.16+) Kernel in case if you are having old one 3. Install FREE BSD having 7.2+ kernel 4. Should have some experience tweaking around your USB modems This is verf brief MOM which i could think of and would like to know if this way of presenting suffices or do i need to add or remove anything extra ? On Tue, Jul 14, 2009 at 9:22 AM, Saifi Khan <sai...@tw...>wrote: > Hi Siddu: > > Can you post the minutes of the meeting (mom) for > PPPConfigurator project ? > > The first meeting was held on Sunday, 12/7. > > thanks > Saifi. > -- Thanks & Regards, _sid_ -- Regards, ~Sid~ http://sidsenclave.blogspot.com |
From: Siddu <sid...@gm...> - 2009-07-16 11:35:25
|
Hello Team, I am ok with the time . i will be available at 21.00 hrs On Thu, Jul 16, 2009 at 4:56 PM, Saifi Khan <sai...@tw...>wrote: > On Thu, 16 Jul 2009, Raghavendran Vasudevan wrote: > > > Hello team, > > > > 2100 hours IST sounds good to me. > > > > Cheers, > > Ragha > > > > On Thu, Jul 16, 2009 at 2:21 PM, Saifi Khan <sai...@tw... > >wrote: > > > > > Hi PPPConfigurator team: > > > > > > Suggest that we have a quick IRC at 2100 hrs IST (GMT+0530) for about > 30 > > > minutes. > > > > > > Required attendees: > > > . Raghavendran > > > . Siddu > > > . Saifi. > > > > > > Let me know if that works for you guys. > > > > > > > > > thanks > > > Saifi. > > > > > #twincling-tacos is the IRC channel for the Tacos team on > freenode.net > > The objective of the meeting is to get the PPPConfigurator team > together and help understand the deliverables. > > > thanks > Saifi. > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > twincling-tacos mailing list > twi...@li... > https://lists.sourceforge.net/lists/listinfo/twincling-tacos > -- Regards, ~Sid~ http://sidsenclave.blogspot.com |
From: Saifi K. <sai...@tw...> - 2009-07-16 11:27:51
|
On Thu, 16 Jul 2009, Raghavendran Vasudevan wrote: > Hello team, > > 2100 hours IST sounds good to me. > > Cheers, > Ragha > > On Thu, Jul 16, 2009 at 2:21 PM, Saifi Khan <sai...@tw...>wrote: > > > Hi PPPConfigurator team: > > > > Suggest that we have a quick IRC at 2100 hrs IST (GMT+0530) for about 30 > > minutes. > > > > Required attendees: > > . Raghavendran > > . Siddu > > . Saifi. > > > > Let me know if that works for you guys. > > > > > > thanks > > Saifi. > > #twincling-tacos is the IRC channel for the Tacos team on freenode.net The objective of the meeting is to get the PPPConfigurator team together and help understand the deliverables. thanks Saifi. |
From: Raghavendran V. <sur...@gm...> - 2009-07-16 10:21:23
|
Hello team, 2100 hours IST sounds good to me. Cheers, Ragha On Thu, Jul 16, 2009 at 2:21 PM, Saifi Khan <sai...@tw...>wrote: > Hi PPPConfigurator team: > > Suggest that we have a quick IRC at 2100 hrs IST (GMT+0530) for about 30 > minutes. > > Required attendees: > . Raghavendran > . Siddu > . Saifi. > > Let me know if that works for you guys. > > > thanks > Saifi. > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > twincling-tacos mailing list > twi...@li... > https://lists.sourceforge.net/lists/listinfo/twincling-tacos > |
From: Saifi K. <sai...@tw...> - 2009-07-16 08:53:08
|
Hi PPPConfigurator team: Suggest that we have a quick IRC at 2100 hrs IST (GMT+0530) for about 30 minutes. Required attendees: . Raghavendran . Siddu . Saifi. Let me know if that works for you guys. thanks Saifi. |
From: chiluveru s. <csn...@gm...> - 2009-06-23 15:13:37
|
From: yashwanth r. <yas...@gm...> - 2009-06-23 13:12:28
|
hi stars, here are the web server log formats that we are going to deal in our LOGANALYSER project. 1. NCSA - ELF (Extended Log Format) - CLF (Common Log Format) - XLF The NCSA Common log format contains only basic HTTP access information. The NCSA Common Log, sometimes referred to as the Access Log, The Common log format can also be thought of as the NCSA Combined<http://publib.boulder.ibm.com/tividd/td/ITWSA/ITWSA_info45/en_US/HTML/guide/c-logs.html#combined>log format without the referral and user agent. The Common log contains the requested resource and a few other pieces of information, but does not contain referral, user agent, or cookie information. The information is contained in a single file. *>COMMON LOG FORMAT* LogFormat "%h %l %u %t \"%r\" %>s %b" common CustomLog logs/access_log common The fields in the Common log file format are: *host rfc931 username date:time request statuscode bytes * The following example shows these fields populated with values in a common log file record: ------------------------------ 125.125.125.125 - dsmith [10/Oct/1999:21:15:05 +0500] "GET /index.html HTTP/1.0" 200 1043 ------------------------------ The following is a description of the fields in the fields in the Common log format: *host*(%h) ( (125.125.125.125 in the example) The IP address or host/subdomain name of the HTTP client that made the HTTP resource request. *rfc931* (%l) ("-" in the example) The identifier used to identify the client making the HTTP request. If no value is present, a "-" is substituted. *username* (%u) (dsmith in the example) The username, (or user ID) used by the client for authentication. If no value is present, a "-" is substituted. *date:time timezone * (%t)* * ([10/Oct/1999:21:15:05 +0500] in the example) The date and time stamp of the HTTP request. The fields in the date/time field are: [dd/MMM/yyyy:hh:mm:ss +-hhmm] where the fields are defined as follow: *dd* is the day of the month *MMM* is the month *yyy* is the year *:hh* is the hour *:mm* is the minute *:ss* is the seconds *+-hhmm* is the time zone(GMT) In practice, the day is typically logged in two-digit format even for single-digit days. For example, the second day of the month would be represented as 02. However, some HTTP servers do log a single digit day as a single digit. When parsing log records, you should be aware of both possible day representations. *request* (\"%r\") ("GET /index.html HTTP/1.0" in the example) The HTTP request. The request field contains three pieces of information. The main piece is the requested resource (index.html). The request field also contains the HTTP method (GET) and the HTTP protocol version (1.0). *statuscode* (%>s) (200 in the example) The status is the numeric code indicating the success or failure of the HTTP request. *bytes* (%b) (1043 in the example) The bytes field is a numeric field containing the number of bytes of data transferred as part of the HTTP request, not including the HTTP header. *>Extended/Combined Log Format* (ELF) LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" All the fields in extended log format are same as that of common log format with addition of two extra fields* Referer agent and user-agent * The access log under this format will look like: 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 *"http://www.example.com/start.html" "Mozilla/4.08 [en] (Win98; I ;Nav)"* The additional fields are: "http://www.example.com/start.html" (\"%{Referer}i\")The "Referer" (sic) HTTP request header. This gives the site that the client reports having been referred from. (This should be the page that links to or includes /apache_pb.gif). "Mozilla/4.08 [en] (Win98; I ;Nav)" (\"%{User-agent}i\")The User-Agent HTTP request header. This is the identifying information that the client browser reports about itself. >XLF Some bespoke format based on extended log format + some junk at the end: "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" %j where %j is .* in regex-speak. *2.W3C* This log file format is used by used by Microsoft Internet Information Server (IIS) 4.0 and 5.0. A log file in the extended format contains a sequence of *lines* containing ASCII characters. Each line may contain either a *directive* or an *entry*. Entries consist of a sequence of *fields* relating to a single HTTP transaction. Fields are separated by white space. If a field is unused in a particular entry dash "-" marks the omitted field. Directives record information about the logging process itself. Lines beginning with the *#* character contain directives. The following directives are defined in the W3C Extended format: Directives defined Extended Log File Format*Version*: *<integer>*.*<integer>* The version of the extended log file format used. This draft defines version 1.0. *Fields*: [*<specifier>*...] Specifies the fields recorded in the log. *Software*: * string* Identifies the software which generated the log. *Start-Date*: * <date>* *<time>* The date and time at which the log was started. *End-Date*: *<date>* *<time>* The date and time at which the log was finished. *Date*:* <date>* *<time>* The date and time at which the entry was added. *Remark*: * <text>* Comment information. Data recorded in this field should be ignored by analysis tools. Extended Log File FThe directives Version and Fields are required and should precede all entries in the log. The Fields directive specifies the data recorded in the fields of each entry. as shown below #Version: 1.0 #Date: 12-Jan-1996 00:00:00 #Fields: time cs-method cs-uri 00:34:23 GET /foo/bar.html 12:21:16 GET /foo/bar.html 12:45:52 GET /foo/bar.html 12:57:34 GET /foo/bar.html in the above example fields directive specifies the data recorded in the form of *time (identifier)* := time at which transaction has completed. *cs-method(prefix-identifier)* := method in the request sent by the client to the server *cs-uri(prefix-identifier)* :=uri specified by the client to server For more on identifier ,prefix -identifier refer below. Extended Log File FormatFields The #Fields directive lists a sequence of *field identifiers* specifying the information recorded in each entry. Field identifiers may have one of the following forms: *identifier* Identifier relates to the transaction as a whole. *prefix*-* identifier* Identifier relates to information transfer between parties defined by the value *prefix*. *prefix*(*header*) Identifies the value of the HTTP header field *header* for transfer between parties defined by the value *prefix*. Fields specified in this manner always have the value <string>. The following prefixes are defined: c Client s Server r Remote cs Client to Server. sc Server to Client. sr Server to Remote Server, this prefix is used by proxies. rs Remote Server to Server, this prefix is used by proxies. x Application specific identifier. The identifier cs-method thus refers to the method in the request sent by the client to the server while sc(Referer) refers to the referer: field of the reply. The identifier c-ip refers to the client's ip address. Identifiers. The following identifiers do not require a prefix date Date at which transaction completed, field has type <date> time Time at which transaction completed, field has type <time> time-taken Time taken for transaction to complete in seconds, field has type <fixed> bytes bytes transferred, field has type <integer> cached Records whether a cache hit occurred, field has type <integer> 0 indicates a cache miss. The following identifiers require a prefix ip IP address and port, field has type <address> dns DNS name, field has type <name> status Status code, field has type <integer> comment Comment returned with status code, field has type <text> method Method, field has type <name> uri URI, field has type <uri> uri-stem Stem portion alone of URI (omitting query), field has type <uri> uri-query Query portion alone of URI, field has type <uri> |
From: yashwanth r. <yas...@gm...> - 2009-06-23 12:11:11
|
---------- Forwarded message ---------- From: yashwanth reddy <yas...@gm...> Date: Tue, Jun 23, 2009 at 4:47 PM Subject: Brief Summary Of various Log Formats To: twi...@li... hi stars, here are the web server log formats that we are going to deal in our LOGANALYSER project. 1. NCSA - ELF (Extended Log Format) - CLF (Common Log Format) - XLF The NCSA Common log format contains only basic HTTP access information. The NCSA Common Log, sometimes referred to as the Access Log, The Common log format can also be thought of as the NCSA Combined<http://publib.boulder.ibm.com/tividd/td/ITWSA/ITWSA_info45/en_US/HTML/guide/c-logs.html#combined>log format without the referral and user agent. The Common log contains the requested resource and a few other pieces of information, but does not contain referral, user agent, or cookie information. The information is contained in a single file. *>COMMON LOG FORMAT* LogFormat "%h %l %u %t \"%r\" %>s %b" common CustomLog logs/access_log common The fields in the Common log file format are: *host rfc931 username date:time request statuscode bytes * The following example shows these fields populated with values in a common log file record: ------------------------------ 125.125.125.125 - dsmith [10/Oct/1999:21:15:05 +0500] "GET /index.html HTTP/1.0" 200 1043 ------------------------------ The following is a description of the fields in the fields in the Common log format: *host*(%h) ( (125.125.125.125 in the example) The IP address or host/subdomain name of the HTTP client that made the HTTP resource request. *rfc931* (%l) ("-" in the example) The identifier used to identify the client making the HTTP request. If no value is present, a "-" is substituted. *username* (%u) (dsmith in the example) The username, (or user ID) used by the client for authentication. If no value is present, a "-" is substituted. *date:time timezone * (%t)* * ([10/Oct/1999:21:15:05 +0500] in the example) The date and time stamp of the HTTP request. The fields in the date/time field are: [dd/MMM/yyyy:hh:mm:ss +-hhmm] where the fields are defined as follow: *dd* is the day of the month *MMM* is the month *yyy* is the year *:hh* is the hour *:mm* is the minute *:ss* is the seconds *+-hhmm* is the time zone(GMT) In practice, the day is typically logged in two-digit format even for single-digit days. For example, the second day of the month would be represented as 02. However, some HTTP servers do log a single digit day as a single digit. When parsing log records, you should be aware of both possible day representations. *request* (\"%r\") ("GET /index.html HTTP/1.0" in the example) The HTTP request. The request field contains three pieces of information. The main piece is the requested resource (index.html). The request field also contains the HTTP method (GET) and the HTTP protocol version (1.0). *statuscode* (%>s) (200 in the example) The status is the numeric code indicating the success or failure of the HTTP request. *bytes* (%b) (1043 in the example) The bytes field is a numeric field containing the number of bytes of data transferred as part of the HTTP request, not including the HTTP header. *>Extended/Combined Log Format* (ELF) LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" All the fields in extended log format are same as that of common log format with addition of two extra fields* Referer agent and user-agent * The access log under this format will look like: 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 *"http://www.example.com/start.html" "Mozilla/4.08 [en] (Win98; I ;Nav)"* The additional fields are: "http://www.example.com/start.html" (\"%{Referer}i\")The "Referer" (sic) HTTP request header. This gives the site that the client reports having been referred from. (This should be the page that links to or includes /apache_pb.gif). "Mozilla/4.08 [en] (Win98; I ;Nav)" (\"%{User-agent}i\")The User-Agent HTTP request header. This is the identifying information that the client browser reports about itself. >XLF Some bespoke format based on extended log format + some junk at the end: "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" %j where %j is .* in regex-speak. *2.W3C* This log file format is used by used by Microsoft Internet Information Server (IIS) 4.0 and 5.0. A log file in the extended format contains a sequence of *lines* containing ASCII characters. Each line may contain either a *directive* or an *entry*. Entries consist of a sequence of *fields* relating to a single HTTP transaction. Fields are separated by white space. If a field is unused in a particular entry dash "-" marks the omitted field. Directives record information about the logging process itself. Lines beginning with the *#* character contain directives. The following directives are defined in the W3C Extended format: Directives defined *Version*: *<integer>*.*<integer>* The version of the extended log file format used. This draft defines version 1.0. *Fields*: [*<specifier>*...] Specifies the fields recorded in the log. *Software*: *string* Identifies the software which generated the log. *Start-Date*: *<date>* *<time>* The date and time at which the log was started. *End-Date*:*<date>* *<time>* The date and time at which the log was finished. *Date*:*<date>* *<time>* The date and time at which the entry was added. *Remark*: *<text>* Comment information. Data recorded in this field should be ignored by analysis tools. The directives Version and Fields are required and should precede all entries in the log. The Fields directive specifies the data recorded in the fields of each entry. as shown below #Version: 1.0 #Date: 12-Jan-1996 00:00:00 #Fields: time cs-method cs-uri 00:34:23 GET /foo/bar.html 12:21:16 GET /foo/bar.html 12:45:52 GET /foo/bar.html 12:57:34 GET /foo/bar.html in the above example fields directive specifies the data recorded in the form of *time (identifier)* := time at which transaction has completed. *cs-method(prefix-identifier)* := method in the request sent by the client to the server *cs-uri(prefix-identifier)* :=uri specified by the client to server For more on identifier ,prefix -identifier refer below. Fields The #Fields directive lists a sequence of *field identifiers* specifying the information recorded in each entry. Field identifiers may have one of the following forms: *identifier* Identifier relates to the transaction as a whole. *prefix*-* identifier* Identifier relates to information transfer between parties defined by the value *prefix*. *prefix*(*header*) Identifies the value of the HTTP header field *header* for transfer between parties defined by the value *prefix*. Fields specified in this manner always have the value <string>. The following prefixes are defined: c Client s Server r Remote cs Client to Server. sc Server to Client. sr Server to Remote Server, this prefix is used by proxies. rs Remote Server to Server, this prefix is used by proxies. x Application specific identifier. The identifier cs-method thus refers to the method in the request sent by the client to the server while sc(Referer) refers to the referer: field of the reply. The identifier c-ip refers to the client's ip address. Identifiers. The following identifiers do not require a prefix date Date at which transaction completed, field has type <date> time Time at which transaction completed, field has type <time> time-taken Time taken for transaction to complete in seconds, field has type <fixed> bytes bytes transferred, field has type <integer> cached Records whether a cache hit occurred, field has type <integer> 0 indicates a cache miss. The following identifiers require a prefix ip IP address and port, field has type <address> dns DNS name, field has type <name> status Status code, field has type <integer> comment Comment returned with status code, field has type <text> method Method, field has type <name> uri URI, field has type <uri> uri-stem Stem portion alone of URI (omitting query), field has type <uri> uri-query Query portion alone of URI, field has type <uri> |
From: yashwanth r. <yas...@gm...> - 2009-06-23 11:23:29
|
From: Saifi K. <sai...@tw...> - 2009-06-21 06:08:16
|
Hi all: Take a look at this X Window Howto http://tldp.org/HOWTO/XWindow-User-HOWTO/index.html Please read Chap 2, 3, 4, 5, 6 in the first go ! thanks Saifi. |
From: Saifi K. <sai...@tw...> - 2009-06-21 05:58:48
|
Hi all: A brief introduction on the 'X window system' is available at http://www.linfo.org/x.html X Server concept is discussed at http://www.linfo.org/x_server.html thanks Saifi. |
From: Saifi K. <sai...@tw...> - 2009-06-11 02:59:34
|
On Wed, 10 Jun 2009, yashwanth reddy wrote: > hi saifi > for NCSA and W3C log format > http://www.loganalyzer.net/log-analyzer/apache-custom-log.html > http://www.w3.org/TR/WD-logfile.html > > > > regards > yashwanth > > > On Wed, Jun 10, 2009 at 10:48 PM, Saifi Khan <sai...@tw...>wrote: > > > On Wed, 10 Jun 2009, yashwanth reddy wrote: > > > > > hi saifi, > > > we have seen NCSA and W3C log formats and understood fields in > > > common log format.Right now we are going through perl and apache web > > server. > > > > > > > > > regards, > > > yashwanth > > > > > > > Can you post the links from where you referred to NCSA format > > and W3C format ? > > > > > > thanks > > Saifi. > > Hi Yashwanth: How are the two formats different ? Can you please elaborate ? thanks Saifi. |
From: yashwanth r. <yas...@gm...> - 2009-06-10 12:56:59
|
hi saifi for NCSA and W3C log format http://www.loganalyzer.net/log-analyzer/apache-custom-log.html http://www.w3.org/TR/WD-logfile.html regards yashwanth On Wed, Jun 10, 2009 at 10:48 PM, Saifi Khan <sai...@tw...>wrote: > On Wed, 10 Jun 2009, yashwanth reddy wrote: > > > hi saifi, > > we have seen NCSA and W3C log formats and understood fields in > > common log format.Right now we are going through perl and apache web > server. > > > > > > regards, > > yashwanth > > > > Can you post the links from where you referred to NCSA format > and W3C format ? > > > thanks > Saifi. > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > twincling-tacos mailing list > twi...@li... > https://lists.sourceforge.net/lists/listinfo/twincling-tacos > |
From: Saifi K. <sai...@tw...> - 2009-06-10 11:46:30
|
On Wed, 10 Jun 2009, yashwanth reddy wrote: > hi saifi, > we have seen NCSA and W3C log formats and understood fields in > common log format.Right now we are going through perl and apache web server. > > > regards, > yashwanth > Can you post the links from where you referred to NCSA format and W3C format ? thanks Saifi. |
From: Saifi K. <sai...@tw...> - 2009-06-10 06:09:51
|
Hi Team: Which log format are first analysing ? Please post the link of the format specification as well. thanks Saifi. |
From: Saifi K. <sai...@tw...> - 2009-06-10 05:55:51
|
On Tue, 9 Jun 2009, Sahil Shah wrote: > > 20:21 #twincling < sahilshah2650> just tell me which flavor > > 20:21 #twincling< saifi> i'd suggest openSUSE 11.1 > > You can quickly download the CD from this link. http://ftp.osuosl.org/pub/opensuse/distribution/11.1/iso/openSUSE-11.1-KDE4-LiveCD-i686.iso Then on your system, you can easily work with the LiveCD. There is no need to install on the system. The generated output from the X -configure can be written to USB later. thanks Saifi. |
From: Dhanasekar K <k.d...@ya...> - 2009-06-05 21:20:30
|
Hi X configurator team, Sorry for the last mail , that was a mistake ..... can we have a IRC in #twincling @ 11 AM tomorrow ? we can discuss about starting things out and when to have the IRC ... if its not possible @ 11:00 please do post an alternative time - Regards Dhanasekar. Cricket on your mind? Visit the ultimate cricket website. Enter http://beta.cricket.yahoo.com |
From: Saifi K. <sai...@tw...> - 2009-06-05 01:02:45
|
On Thu, 4 Jun 2009, Dhanasekar K wrote: > Saifi can you please sent me the text file that you had created yesterday ... i ll do a write up about what has to be done for the x-configurator project. > Please see below. thanks Saifi. -- . xorg.conf . Xserver . Xorg . X device entry /dev/* man -S 5 xorg.conf provide a wizard that presents a set of options from which a user selects the one matching closely or specific option. User has the option to specify string expressions or numeric expressions. The generated xorg.conf file is always complete and unselected options are commented out. Services to offer are: . creation of a standards compliant xorg.conf file . select some of the standard laptops/desktops and autogenerate the file. . validation of the xorg.conf file . validation against version of Xorg 1.5 and 1.6 server . auto-generated configuration for nested X server . support for creating LCD projector configuration. . multi-heading with Xinerama. . on the website tacos.twincling.org create an interface to accept xorg.conf file contributions. . .xinitrc, .Xresources, .Xsession, .Xdefaults, .Xmodmap Manual steps http://www.linuxmigration.com/quickref/window/config.html ddccontrol-db-20061014.tar.bz2 ddccontrol http://ddccontrol.sourceforge.net/ ddcxinfo-knoppix gets you ddcprobe Monitor Modes Screen Devices To extract information we need VESA bios Extensions http://en.wikipedia.org/wiki/VESA_BIOS_Extensions To run multiple X environment, please use Xephyr http://techbase.kde.org/Getting_Started/Set_up_KDE_4_for_development Open Issues . wrt GPU how to do it ! Steps 1. base wizard and core framework 2. update/increment the database 3. ToDo . read and document the grammmar of the xorg.conf file . come up with a set of steps to create the complete xorg.conf file . define a ncurses interface to present user selectable options. . identify the external tools required to collec the information. Reading . PERL 5.6.10 . PERL modules Curses::UI . Learning PERL , 5th Edn, Randall Schwartz . Dispatch pattern -- |
From: Saifi K. <sai...@tw...> - 2009-05-25 10:04:46
|
Hi Stars: -- TACOS - loganalyser Twincling TACOS or Twincling Automatic Configuration Service is essentially an automation project to provide unique service over the web for a variety of configurations. A configuration service could be as simple as .vimrc file all the way to a complex database replication script. Tacos - log analyser project Log analyser provides three important capabilities 1. support the following webserver log formats - NCSA - XLF - ELF - CLF - W3C 2. process the log, classify based on domains and write to a numbered file $USER-$DOMAIN-YYYY-MM-DD.log 3. correlate between error_log and access_log wherever applicable. Phase II 1. be able to integrate the script in the configuration file of the following webservers - nginX - apache 2.x What is the technology ? Apache Webserver 2.2.x PHP 5.2.8 server side PERL 5.8.8 script side (Phase II) ajax based interface jquery graceful ajax degradation to be supported for Lynx/links/elinks browsers. What is the deployment model ? http://tacos.twincling.org/loganalyser Phase II CustomLog |/usr/local/twincling/bin/loganalyser CustomLog |/usr/local/twincling/bin/loganalyser correlate What is the communication channel ? IRC #twincling on irc.freenode.net #twincling-tacos mailing list https://lists.sourceforge.net/lists/listinfo/twincling-tacos weekly status updates everybody including mentors will post their status updates as a blog on twincling.org with the following tags . Open Source tag: project-name . Project tag : status, update -- Hope this helps. thanks Saifi. |
From: Saifi K. <sai...@tw...> - 2009-05-25 10:04:05
|
Hi Stars: -- TACOS - xconfigurator Twincling TACOS or Twincling Automatic Configuration Service is essentially an automation project to provide unique service over the web for a variety of configurations. A configuration service could be as simple as .vimrc file all the way to a complex database replication script. Tacos - xconfigurator project Xconfigurator provides two important capabilities 1. generate an xorg.conf file based on user input of screen, display, input devices, fonts and other properties. 2. validate an input xorg.conf file based on syntax and semantics in xorg-x11 7.2 and xorg-x11 7.4 3. error log (Xorg.0.log) upload and diagnosis. What is the technology ? Apache Webserver 2.2.x PHP 5.2.8 server side ajax based interface jquery graceful ajax degradation to be supported for Lynx/links/elinks browsers. What is the deployment model ? http://tacos.twincling.org/xconfigurator What is the communication channel ? IRC #twincling on irc.freenode.net #twincling-tacos mailing list https://lists.sourceforge.net/lists/listinfo/twincling-tacos weekly status updates everybody including mentors will post their status updates as a blog on twincling.org with the following tags . Open Source tag: project-name . Project tag : status, update -- Hope this helps. thanks Saifi. |