You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(38) |
Sep
(126) |
Oct
(23) |
Nov
(72) |
Dec
(36) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(76) |
Feb
(32) |
Mar
(19) |
Apr
(6) |
May
(54) |
Jun
(40) |
Jul
(45) |
Aug
(35) |
Sep
(51) |
Oct
(67) |
Nov
(10) |
Dec
(50) |
2004 |
Jan
(51) |
Feb
(22) |
Mar
(22) |
Apr
(28) |
May
(53) |
Jun
(99) |
Jul
(38) |
Aug
(49) |
Sep
(23) |
Oct
(29) |
Nov
(30) |
Dec
(48) |
2005 |
Jan
(15) |
Feb
(21) |
Mar
(25) |
Apr
(16) |
May
(131) |
Jun
|
Jul
(8) |
Aug
(5) |
Sep
(15) |
Oct
|
Nov
(15) |
Dec
(12) |
2006 |
Jan
(15) |
Feb
(20) |
Mar
(8) |
Apr
(10) |
May
(3) |
Jun
(16) |
Jul
(15) |
Aug
(11) |
Sep
(17) |
Oct
(27) |
Nov
(11) |
Dec
(12) |
2007 |
Jan
(19) |
Feb
(18) |
Mar
(33) |
Apr
(4) |
May
(15) |
Jun
(22) |
Jul
(19) |
Aug
(20) |
Sep
(14) |
Oct
(4) |
Nov
(34) |
Dec
(11) |
2008 |
Jan
(8) |
Feb
(18) |
Mar
(2) |
Apr
(4) |
May
(26) |
Jun
(9) |
Jul
(8) |
Aug
(8) |
Sep
(3) |
Oct
(17) |
Nov
(14) |
Dec
(4) |
2009 |
Jan
(6) |
Feb
(41) |
Mar
(21) |
Apr
(10) |
May
(21) |
Jun
|
Jul
(8) |
Aug
(4) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(5) |
2010 |
Jan
(14) |
Feb
(13) |
Mar
(7) |
Apr
(12) |
May
(4) |
Jun
(1) |
Jul
(11) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(10) |
Dec
|
2011 |
Jan
(7) |
Feb
(3) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(1) |
Jul
(6) |
Aug
(6) |
Sep
(10) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
2012 |
Jan
(4) |
Feb
(5) |
Mar
(1) |
Apr
(7) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
2013 |
Jan
(6) |
Feb
|
Mar
(14) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(4) |
Dec
(6) |
2014 |
Jan
|
Feb
(1) |
Mar
(10) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(4) |
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Beulah G. <fn...@ya...> - 2003-12-17 14:20:13
|
TECHNOLOGY SECTOR - TECHNOLOGY BREAKTHROUGH - PATENTS FILED Symbol: NMMG Market: OTC.BB Sector: L.E.D. TECHNOLOGY Barcharts Rate NMMG an 80% BUY - http://quotes.barchart.com/texpert.asp?sy= m=3DNMMG BREAKING NEWS in technology - New Millennium Media International (OTCBB: N= MMG) announces that it has officially filed its patents---with over 50 cla= ims---protecting its revolutionary technology, a breakthrough in (LED) arc= hitecture. The OnScreen=99 LED Display Architecture is a radical new type= of Bright LED video display architecture that is expected to revolutioniz= e the 1.5 billion dollar LED display market. This breakthrough technology= will give NMMG great potential to capture significant market share in the= the 19 billion dollar outdoor advertising market. With all the new initiatives in Homeland Security and the Amber Alert, Int= elligent Message Signs (IMS) are the future, and with the recent signing o= f new laws and federally mandated funds in the billions of dollars, NMMG a= nd its patent-pending OnScreen technology is poised to lead the way. NMMG= currently has the only technology that allows it to build onto exisiting = infrastructure, i.e. road signs, billboards, etc. Imagine one day you are= driving home on the freeway past a road sign you have seen a thousand tim= es before--but this time you notice something different. This time you se= e a WARNING lit up--truck overturned 1 mile ahead--hazardous chemicals spi= lled. The sign advises you to exit immediately and to safety. Such a war= ning was broadcast instantly and using NMMG's OnScreen technology. You ne= ver noticed, as you drove by the roadside every day, that OnScreen was dra= ped over the sign all this time. Now it has sprung into action by the pun= ch of a button on a PC from a central station--instantly and just in the n= ick of time. You have just experienced OnScreen technology. And that is = just one example. The possibilities are limitless. And because OnScreen = can be applied to existing structures like road signs or billboards, its c= ost-effectiveness makes it far and away the technology choice. NMMG will unveil its breakthrough technology at the STRATEGIES IN LIGHT co= nference on February 2-4, 2004 at the San Mateo Marriott Hotel in San Mate= o, California. This unique event is considered to be the premier annual fo= rum for addressing commercial developments in high-brightness LEDs, as wel= l as an unparalleled networking opportunity for suppliers and users of the= se devices. The growing interest in, and expanding attendance at, this eve= nt, reflects the excitement associated with a market that has grown by 50= % since 2000, while other semiconductor and optical component industries h= ave stagnated or experienced large declines. ON-SCREEN=99 TECHNOLOGY OnScreen=99 is expected to create a broad-range of products with much bett= er resolution and brighter pictures than the current generation of display= s. OnScreen=99 will be visible in direct sunlight yet avoid many of the is= sues associated with current displays including sun-loading, wind-loading = and excessive weight. In addition, the new LED architecture produces an a= dvantage that is not available in today's marketplace: a more lightweight,= pliable display that can fit any application. These are important advant= ages as the High Brightness LED market is expected to grow from 1.2 billio= n dollars in 2000 to 4 billion in 2006. In addition, according to Stanfor= d Resources, the LED sign market value alone is expected to exceed 1 billi= on by 2006. These projections are made based on existing technology and do= not take into account emerging technologies, such as OnScreen=99, that ca= n rapidly alter the size and shape of this market. COMMERCIAL MARKET & STRATEGY NMMG's initial marketing strategy revolves around licensing intellectual p= roperty (IP) to worldwide manufacturers of LED display products and compon= ents. The LED sign market is projected to reach over 1 billion dollars by = 2006. Lumiled's projects that high brightness LED's, used in LED signs alo= ne, will exceed 1.2 billion by 2007. If these projections hold, the fully = manufactured signs would represent a $5 billion market. Whichever number i= s accurate, they both point towards a robust market for these new LED disp= lays. Many projections don't take into account emerging high growth applic= ations such as the Amber Alert project, Homeland Security and roadway =93i= ntelligent message transfer=94. THE MARKET An article in Media Post's Media Daily News in March of 2003 noted that th= e outdoor industry has successfully weathered the recession and that =93ou= r large members say they're having a great first quarter=94 in 2003. They = go on to note that technology is expected to transform both the display an= d measurement of outdoor advertising. According to Media Daily the most ex= citing news is coming on the display side, where =93Lamar Advertising is c= onverting their key boards to LED units whose messages can be changed at w= ill and sold in day-parts by the hour or even the minute.=94 They added th= at =93Clear Channel's backlit subway panels in stairwells are being conver= ted to LED as well=94. Together these companies represent two of the three= largest outdoor US advertisers. Recent Federal Government legislation has also placed a spotlight on expan= ding the =93Amber Alert=94 network nationwide. The highly publicized succe= ss in locating a number of kidnapped children shortly after their abductio= n in California has now triggered federal funding for U.S.-wide expansion = of these variable-message signs. Homeland Security issues have also incre= ased the number of early warning signs being planned and funded as part of= an overall information sharing network. Traffic safety is also becoming a= much higher priority in the U.S.. It is estimated that just over 60,000 r= oadway dynamic message signs are in operation in the United States. In Jap= an alone there are over 1.5 million of these signs. The United States repr= esents a huge growth market for LED displays. GROWTH OPPORTUNITES In addition to the outdoor television market, another interesting and exci= ting application for OnScreen=99 arrays is artistic lighting in dramatic c= urved and shaped displays in places like Las Vegas, New York City or reall= y virtually any venue. The tensile, flexible structure of OnScreen=99 prov= ides unlimited opportunity for creativity. The anticipated cost reductions of OnScreen=99 will also provide ample opp= ortunity for growth of the large-scale LED display market itself. OnScreen= =99's unique architecture opens the door for new applications such as curv= ed implementations, billboards on the sides of buildings where tenants can= still see out, and lower cost mobile applications on the sides of existin= g vehicles. Homeland Security, Amber Alert variable message signage and instant messag= e transfer applications can also benefit significantly from the advantages= of OnScreen=99. Reduced wind-loading and weight can significantly lower t= he cost of the superstructures required to support these signs and also re= duce the cost to install and maintain them. JUST LOOK WHO IS ALREADY ON BOARD New Millennium has established a Technology Breakthroughsentific Advisory = Board comprised of leading experts in key categories in the research and m= arketing of LED technology. David Pelka, Ph.D.- Chairman =96 Well known expert in physics, founded TIR= Technologies Inc. to pursue patents for his LED lighting systems and LCD = backlits. Dr. Pelka secured more than $2 million in venture capital and l= icensing for TIR before it was acquired by Teledyne Electronic Technologie= s (NYSE:TDY). Since the buyout, Dr. Pelka has served as Director of Produ= ct Development for Teledyne Lighting and Display Products. Dr. Pelka's ac= colades include fellowships and awards from the Smithsonian, National Defe= nse, Northrop University and Ebell Fellowship, as well as countless articl= es published in both classified (the U.S. Air Force and Army) publications= and various non-classified publications. He has founded several technolo= gy companies, which he successfully expanded by building strong revenue st= reams and securing venture capital investments and government contracts. Robert V. Steele, Ph.D. =96 Director of Optoelectronics Programs and Chair= man of the annual conference =93Strategies in Light=94 for Strategies Unli= mited. Steele is responsible for all of Strategies Unlimited's activities= in the area of optoelectronic components, for which the 23-year-old marke= t research firm has specialized in providing market research reports and c= onsulting services. Co-author of =93Solid-State Lighting: New Growth Oppo= rtunities for High-Brightness LED's=94, Dr. Steele writes regularly for in= dustry publications on high-brightness LED markets and applications such a= s Forbes, The Wall Street Journal, The Economist and more. John Biondo =96 Owner and President of Silicon Robotics Corporation, which= provides various product development services including electronic and el= ectromechanical design, software development, optics, and project manageme= nt. Biondo also has extensive patent-process experience. In 1980, Biondo= launched Electric Filmworks, which produced computer-generated visual eff= ects for the television and motion picture industry. He also designed an = apparatus using newly available and inexpensive microcomputers, which allo= wed the company to compete successful against older, more established firm= s. To transfer from the service-sector into manufacturing, Biondo sold El= ectric Filmworks in 1989 and co-founded Amazing Photos. Amazing Photos de= signed, manufactured and sold a variety of innovative coin-operated photo = booths. Polaroid Corporation licensed and marketed the two most popular a= nd cost effective booths under their own name. Richard Reis, Ph.D. =96 Executive Director of the Alliance for Innovative = Manufacturing at Stanford and Director for Academic Partnerships in the St= anford Learning Laboratory. Dr. Reis' impressive career includes serving = as; the Executive director of the Stanford Center for integrated Systems, = a major research partnership between Stanford and 15 industrial companies;= a Consulting Professor in both the Stanford University Electrical and Mec= hanical Engineering departments; professor of a year-round seminar that is= part of the Stanford University Future Professors of Manufacturing progra= m; a professor of astronomy at the College of San Mateo, Calif.; and a cur= riculum consultant at Menlo College, Calif. Ben Jacobson, Ph.D. =96 Dr. Jacobson has worked on numerous impressive LED= projects that have exponentially increased beam density and brightness an= d reduced system costs. Additionally, these projects have improved power r= equirements, heat load and LED count, while improving compactness, efficie= ncy and performance over competitors' products. Dr. Jacobson was instrume= ntal in positioning Illumitech as a new company developing high-performanc= e LED lighting systems with thermal packaging. Dr. Jacobson has over a de= cade of experience developing and marketing new technology for the display= industry, both in his previous positions and currently at Illumitech. Pr= ior to Illumitech, Dr. Jacobson held various executive and research direct= orial positions at EG Controls Inc., ARCH Venture Partners, NiOptics Corpo= ration and the University of Chicago. He has seven U.S. patents, and has = published 13 research articles and seven conference presentations. Joseph D. Tajnai, Ph.D. =96 Dr. Tajnai is a consultant in Optical Radiatio= n Safety, LED's & Applications and Optics & Optical Measurement Training. = He was an engineer, Technology Breakthroughsentist and technical manager f= or 23 years at Hewlett-Packard and Agilent Technologies. He has focused on= fiber optic development, LED development and measurements, new product pr= ocesses, mathematical modeling and international and US standards and regu= lations. He also worked with GE Sylvania for nine years and contributed he= avily to their YAG laser development. Dr. Tajnai received his BS, MS and P= h.D. from California Institute of Technology in Electrical Engineering and= Applied Physics. Please note that NMMG had absolutley nothing to do with this report and is= not a participant in any way. No more advertisements: www.inet-notification.com/away.html Technology Breakthroughs is an independent research firm. This report is b= ased on Technology Breakthroughs's independent analysis but also relies on= information supplied by sources believed to be reliable. This report may = not be the opinion of NMMG management. Technology Breakthroughs has also b= een retained to research and issue reports on NMMG. Technology Breakthroug= hs may from time to time purchase or sell NMMG common shares in the open m= arket without notice. The information contained in this report shall not c= onstitute, an offer to sell or solicitation of any offer to purchase any s= ecurity. It is intended for information only. Some statements may contain = so-called "forward-looking statements". Many factors could cause actual re= sults to differ. Investors should consult with their Investment Advisor co= ncerning NMMG. Copyright 2003 =A9 Technology Breakthroughs. All Rights Res= erved. Technology Breakthroughs was paid eight thousand dollars to distrib= ute this report. Technology Breakthroughs is not affiiated with Technology= Breakthroughs and is not responsible for newsletter content. All informa= tion in this report can be obtained on the world wide web at www.nmmimedia= com. New Millenimum Media was not a participant in this newsletter in an= y way. rquvloptdruraak tlc ukaqbh kf esrzfiie b c e gxlh j vvofwciushikee mey dno |
From: Mike S. <msc...@ao...> - 2003-12-17 03:37:34
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title></title> </head> <body> <font face="Arial,sans-serif"><font size="2"><span type="cite">King, James X -ND wrote on 12/16/2003, 4:00 PM:</span> </font></font> <p><font face="Arial,sans-serif" size="2"></font></p> <blockquote type="cite" style="border-left: thin solid blue; padding-left: 10px; margin-left: 0pt;"><font face="Arial,sans-serif" size="2"></font> <p class="MsoNormal"><font size="2" face="Arial"><font face="Arial"><font size="2">Do you support the following levels supported in the log4j:</font></font></font></p> <font face="Arial,sans-serif" size="2"></font></blockquote> <font face="Arial,sans-serif"><font size="2">Yepp, we do. All available levels are listed here:<br> <br> <a class="moz-txt-link-freetext" href="http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl/Level.html">http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl/Level.html</a><br> <br> <span>-- <br> -- Mike<br> Mike Schilli<br> <a class="moz-txt-link-abbreviated" href="mailto:m...@pe...">m...@pe...</a></span></font></font> </body> </html> |
From: King, J. X -N. <Jam...@di...> - 2003-12-17 00:00:43
|
Do you support the following levels supported in the log4j: * static Level ALL The ALL Level has the lowest possible rank and is intended to turn on all logging. * static Level OFF The OFF Level has the highest possible rank and is intended to turn off logging. Thanks, - James =20 James C. King Software Engineer email: Jam...@di... <mailto:Jam...@di...>=20 (818) 623-3594 =20 |
From: Mike S. <msc...@ao...> - 2003-12-16 15:56:28
|
Michael Preuhs wrote on 12/16/2003, 12:47 AM: > How can I do a user installation, I'm not a root on a linux computer > I try > perl Makefile.PL -prefix=/home/preuhs/log4perl > and I get this warning > '-PREFIX' is not a known MakeMaker parameter name. Use perl Makefile.PL LIB=/home/preuhs/log4perl to install and use lib "/home/preuhs/log4perl"; in your script. More on this in http://www.linux-magazin.de/Artikel/ausgabe/1999/11/Local/local.html -- -- Mike Mike Schilli m...@pe... |
From: Michael P. <mic...@we...> - 2003-12-16 08:48:07
|
How can I do a user installation, I'm not a root on a linux computer I try perl Makefile.PL -prefix=/home/preuhs/log4perl and I get this warning '-PREFIX' is not a known MakeMaker parameter name. Writing Makefile for Log::Log4perl |
From: Mike S. <msc...@ao...> - 2003-12-15 22:17:49
|
King, James X -ND wrote on 12/15/2003, 11:50 AM: > I=E2=80=99m looking into using the Log::Dispatch to do file rollover on U= NIX. > I see that it supports file rollover into backup file(s) based on > MaxFileSize; daily, weekly or monthly log files based on a DatePattern > or defaults. I read your Readme file: I would suspect that Mark's rotator might get into trouble if several instances of the rolling logfile appender are doing their thing :). Mark, do you support (or plan on supporting) synchronization techniques? James could certainly use l4p's Synchronized composite appender to synchronize all output, but that's probably more than is really needed here. Is there a way to just synchronize the rollover process from within the rolling logfile appender? --=20 -- Mike Mike Schilli m...@pe... |
From: King, J. X -N. <Jam...@di...> - 2003-12-15 19:50:37
|
I'm looking into using the Log::Dispatch to do file rollover on UNIX. I see that it supports file rollover into backup file(s) based on MaxFileSize; daily, weekly or monthly log files based on a DatePattern or defaults. I read your Readme file: http://www.perl.com/CPAN-local/modules/by-module/Log/MARKPF/Log-Dispatch -FileRotate-1.08.readme I'm just wondering how the file rollover syncs up when multiple CGI processes using Log4perl are running and attempting to rollover a file. I have not put in place the Log::Log4perl::Appended::Synchronized yet because it looks like we are not losing any records written to the log file. Is the Log::Log4perl::Appended::Synchronized something that should be in place for the Dispatcher::FileRotate to manage in a multiple process environment? Thanks, - James =20 =20 James C. King Software Engineer email: Jam...@di... <mailto:Jam...@di...>=20 (818) 623-3594 =20 |
From: Mike S. <msc...@ao...> - 2003-12-13 17:33:47
|
Hi all, the maintenance release 0.41 is on the homepage now, with the following changes: 0.41 (12/12/2003) * (ms) Applied documentation update for Synchronized appender, suggested by David Viner E<lt>dv...@ya...E<gt> * (ms) Added option to Log::Log4perl::Layout::PatternLayout to enable people to provide their own timer functions. If all goes will, it'll be on its way to CPAN in a couple of days ... -- -- Mike Mike Schilli log...@pe... |
From: Mike S. <msc...@ao...> - 2003-12-13 04:13:44
|
Marco Aurelio Valtas Cunha wrote on 12/12/2003, 2:24 AM: > I was thinking in have one file for each > Adaptor, but this means write one more Appender configuration for each > Adaptor. > But I expect more and more Adaptors and as a programmer I'm very lazy, > the > result I want is that each new adaptor added in my conf file will > imply a nre > log file with it's name. The file appenders that come with Log::Log4perl and Log::Dispatch require that the name of the file they're logging to is specified as a property -- this leaves you with the manual approach: Define an appender for every file and assign each of them to a different logger (but watch out for messages bubbling up, see the FAQ). If you want to automate the creation of these appenders, you could (somewhat at the expense of the maintainability of your script/config file) leave your config file like it is and use l4p's add_appender() method in your code like this: my $logger = Log::Log4perl->get_logger("My.Component"); $logger->add_appender($app); to add a previously defined appender $app to this logger. Or, you could automate creating the l4p conf file with a script. -- -- Mike Mike Schilli m...@pe... |
From: Marco A. V. C. <mav...@bi...> - 2003-12-12 10:24:30
|
Hi All, I've been looking around but could not find a good anwser or guidelines for this. I have log4perl conf file that look like this: log4perl.rootLogger=DEBUG,File log4perl.category.BiT.Inter = INFO log4perl.category.BiT.Inter.Adaptor.bitc2 = FATAL log4perl.category.BiT.Inter.Adaptor.test = DEBUG log4perl.category.BiT.Inter.Adaptor.auth = INFO log4perl.category.BiT.Inter.Adaptor.info = DEBUG log4perl.appender.File = Log::Dispatch::File log4perl.appender.File.filename = /tmp/biti.log log4perl.appender.File.mode = append log4perl.appender.File.layout = \ Log::Log4perl::Layout::PatternLayout log4perl.appender.File.layout.ConversionPattern = %d %C %m %n And there is no problem in here, as expected log4perl logs everything in '/tmp/biti.log'. But as you can see there's BiT.Inter.Adaptor.* classes and they are coded with very different propouses, so have all logs in one file makes more difficult to access/correct some bug. I was thinking in have one file for each Adaptor, but this means write one more Appender configuration for each Adaptor. But I expect more and more Adaptors and as a programmer I'm very lazy, the result I want is that each new adaptor added in my conf file will imply a nre log file with it's name. And other messages to this main log file '/tmp/biti.log' Can anyone point me some thoughts about it? Thanks in advance. Marco. -- Marco A Valtas Cunha http://scarecrow.fmrp.usp.br/~mavcunha/ Lab de Bioinformatica http://bit.fmrp.usp.br Hemocentro de Rib Preto http://ctc.fmrp.usp.br Fax: 55 16 3963-9309 Tel: 55 16 3963-9300 R:9603 |
From: Francesca F. <q78...@ya...> - 2003-12-11 23:00:02
|
BREAKING NEWS on TRHL True Health (TRHL) Signs Landmark Deal With Spectrum Care; Becomes Preferr= ed Provider To Consortium of 130+ Nursing Homes... BECKENHAM, England---PRNewswire-FirstCall---True Health, Inc., (OTC Bullet= in Board: TRHL) a leader in healthcare recruitment and pressure relieving = systems, announced today that it has been selected as the Preferred Provid= er in three product categories for Spectrum Care Ltd., a first-of-its kind= buying consortium made up of a growing number of nursing homes across the= U.K. This agreement creates efficiencies in marketing for True Health and= an improved purchasing position for Spectrum, reducing the cost of the Co= mpany's products for buyers while improving True Health's margins and sale= s channels. Spectrum Care is a recently formed consortium that consolidates the buying= power of individual nursing homes across the U.K. and currently has over = 130 homes in its network. The consortium is a unique purchasing initiative= for the U.K. nursing home market. Spectrum Care has reached preferred pur= chasing agreements with a wide range of suppliers for various goods and se= rvices. Following careful evaluation, Spectrum has chosen True Health as its prefe= rred provider in three product categories: Pressure Area Care Products, Pa= tient Moving and Handling Equipment, and Nursing Home Beds. Nursing homes = in the Spectrum Care network will be offered True Health products in these= categories at discounted prices and on preferred payment terms. True Heal= th receives access to all 130 nursing homes and has embarked on a joint ma= rketing initiative with Spectrum including a co-branded catalog and joint = sales ventures. "We are very excited about our arrangement with Spectrum. It allows us to = offer lower prices to nursing home customers so that those care centers ca= n apply their savings towards improved direct patient care," stated True H= ealth CEO, Mr. David Frances. "It also creates improved marketing and sale= s economics for us, allowing our sales team to focus on the cornerstones o= f our growth strategy: larger contracts, and the roll out of new products = and services." About True Health, Inc. True Health, through its wholly owned subsidiary, Westmeria Healthcare Lim= ited, is a full service specialist, medical equipment and medical professi= onal supplier to the healthcare industry. Its primary clients are Great Br= itain's National Health Service (NHS) and the private Nursing Home Industr= y. True Health delivers recruitment services to the NHS; specializing in t= he provision of locum radiographers and nurses. Its core business is suppl= ying proprietary branded specialist pressure relieving equipment for the h= ealthcare sector. The branded products are manufactured and licensed for t= he company in Germany, Belgium and Taiwan. The statements contained in this news release that are not historical fact= s may be statements regarding the Company's future that involve risks and = uncertainties which could cause actual results to differ materially from t= hose currently anticipated. For example, statements that describe the Comp= any's hopes, plans, objectives, goals, intentions or expectations are all = forward looking statements. Any such statements made herein about the Comp= any's future are only made as of the date of this news release. Numerous f= actors, many of which are beyond the Company's control, may affect actual = results. The Company undertakes no obligation to publicly update such forw= ard-looking statements to reflect subsequent events or circumstances. jpfukqlbs wxoc fyijl negryazgquehnwvvkkf axcd j tw t |
From: Viner, D. <dv...@ya...> - 2003-12-10 16:51:15
|
I'm using Perl v5.6.1 on FreeBSD 4.x. -----Original Message----- From: Mike Schilli [mailto:msc...@ao...] Sent: Tuesday, December 09, 2003 11:31 PM To: Viner, David Cc: Log4perl-Devel (E-mail) Subject: RE: [log4perl-devel] potential bug in Viner, David wrote on 12/9/2003, 12:30 PM: > sorry... here are the files. Hmm, I don't get a core, the script exits normally. Also, you're not logging anything -- you're getting a core just by running log.pl? Which OS are you using? Which version of perl? -- -- Mike Mike Schilli m...@pe... |
From: Mike S. <msc...@ao...> - 2003-12-10 07:31:11
|
Viner, David wrote on 12/9/2003, 12:30 PM: > sorry... here are the files. Hmm, I don't get a core, the script exits normally. Also, you're not logging anything -- you're getting a core just by running log.pl? Which OS are you using? Which version of perl? -- -- Mike Mike Schilli m...@pe... |
From: Viner, D. <dv...@ya...> - 2003-12-09 20:31:41
|
sorry... here are the files. dave -----Original Message----- From: Viner, David [mailto:dv...@ya...] Sent: Tuesday, December 09, 2003 12:12 PM To: Log4perl-Devel (E-mail) Subject: [log4perl-devel] potential bug in Hi, I've been toying with the Log::Log4perl::Appender::Synchronized in version 0.40. I think I've discovered a bug with the shared memory handling. I've attached the script and the config file that always causes a core dump on my machine. I strongly suspect that my problem is some weird state that the shared memory on my machine has gotten itself into. But, I'd like to figure out how to improve the Synchronized module to defend against whatever causes the core dump. I'm sure that it's the Synchronized module because using this line from the config file log4perl.logger.dispatcher = DEBUG, DebugScreen, FileAppndr1 works fine, where as log4perl.logger.dispatcher = DEBUG, DebugScreen, Syncer causes a core dump. I can't make much sense of the backtrace from GDB ... but here it is: (gdb) bt #0 0x280f9043 in Perl_pp_untie () at pp_sys.c:796 #1 0x280c9814 in Perl_runops_standard () at run.c:25 #2 0x28080e81 in S_call_body (myop=0x9fbff530, is_eval=0) at perl.c:1824 #3 0x28080bfe in perl_call_sv (sv=0x81b0b6c, flags=22) at perl.c:1742 #4 0x280d6b3c in Perl_sv_clear (sv=0x81b71f8) at sv.c:3742 #5 0x280d712e in Perl_sv_free (sv=0x81b71f8) at sv.c:3950 #6 0x280d6e54 in Perl_sv_clear (sv=0x80646e8) at sv.c:3824 #7 0x280d712e in Perl_sv_free (sv=0x80646e8) at sv.c:3950 #8 0x280c6bc9 in Perl_hv_free_ent (hv=0x8064640, entry=0x81b89b0) at hv.c:1068 #9 0x280c6dae in S_hfreeentries (hv=0x8064640) at hv.c:1146 #10 0x280c6dfe in Perl_hv_undef (hv=0x8064640) at hv.c:1172 #11 0x280d6dad in Perl_sv_clear (sv=0x8064640) at sv.c:3795 #12 0x280d712e in Perl_sv_free (sv=0x8064640) at sv.c:3950 #13 0x280db8f0 in do_clean_objs (sv=0x8064580) at sv.c:8381 #14 0x280d09c8 in S_visit (f=0x280db884 <do_clean_objs>) at sv.c:162 #15 0x280d0a47 in Perl_sv_clean_objs () at sv.c:180 #16 0x2807e5f3 in perl_destruct (my_perl=0x804d030) at perl.c:417 #17 0x8049249 in main (argc=3, argv=0x9fbff914, env=0x9fbff924) at perlmain.c:55 My machine appears to have several shared memory segments allocated... ipcs reports: Message Queues: T ID KEY MODE OWNER GROUP Shared Memory: T ID KEY MODE OWNER GROUP m 196608 0 --rw------- dviner users m 3735553 0 --rw------- dviner users m 393218 0 --rw------- dviner users m 1048579 0 --rw------- dviner users m 851974 0 --rw------- dviner users m 262153 0 --rw------- dviner users Semaphores: T ID KEY MODE OWNER GROUP I'm using Perl v5.6.1 on FreeBSD 4.x. Has anyone seen this error? or have a suggestion on how to debug it? thanks dave ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ log4perl-devel mailing list log...@li... https://lists.sourceforge.net/lists/listinfo/log4perl-devel |
From: Viner, D. <dv...@ya...> - 2003-12-09 20:13:18
|
Hi, I've been toying with the Log::Log4perl::Appender::Synchronized in version 0.40. I think I've discovered a bug with the shared memory handling. I've attached the script and the config file that always causes a core dump on my machine. I strongly suspect that my problem is some weird state that the shared memory on my machine has gotten itself into. But, I'd like to figure out how to improve the Synchronized module to defend against whatever causes the core dump. I'm sure that it's the Synchronized module because using this line from the config file log4perl.logger.dispatcher = DEBUG, DebugScreen, FileAppndr1 works fine, where as log4perl.logger.dispatcher = DEBUG, DebugScreen, Syncer causes a core dump. I can't make much sense of the backtrace from GDB ... but here it is: (gdb) bt #0 0x280f9043 in Perl_pp_untie () at pp_sys.c:796 #1 0x280c9814 in Perl_runops_standard () at run.c:25 #2 0x28080e81 in S_call_body (myop=0x9fbff530, is_eval=0) at perl.c:1824 #3 0x28080bfe in perl_call_sv (sv=0x81b0b6c, flags=22) at perl.c:1742 #4 0x280d6b3c in Perl_sv_clear (sv=0x81b71f8) at sv.c:3742 #5 0x280d712e in Perl_sv_free (sv=0x81b71f8) at sv.c:3950 #6 0x280d6e54 in Perl_sv_clear (sv=0x80646e8) at sv.c:3824 #7 0x280d712e in Perl_sv_free (sv=0x80646e8) at sv.c:3950 #8 0x280c6bc9 in Perl_hv_free_ent (hv=0x8064640, entry=0x81b89b0) at hv.c:1068 #9 0x280c6dae in S_hfreeentries (hv=0x8064640) at hv.c:1146 #10 0x280c6dfe in Perl_hv_undef (hv=0x8064640) at hv.c:1172 #11 0x280d6dad in Perl_sv_clear (sv=0x8064640) at sv.c:3795 #12 0x280d712e in Perl_sv_free (sv=0x8064640) at sv.c:3950 #13 0x280db8f0 in do_clean_objs (sv=0x8064580) at sv.c:8381 #14 0x280d09c8 in S_visit (f=0x280db884 <do_clean_objs>) at sv.c:162 #15 0x280d0a47 in Perl_sv_clean_objs () at sv.c:180 #16 0x2807e5f3 in perl_destruct (my_perl=0x804d030) at perl.c:417 #17 0x8049249 in main (argc=3, argv=0x9fbff914, env=0x9fbff924) at perlmain.c:55 My machine appears to have several shared memory segments allocated... ipcs reports: Message Queues: T ID KEY MODE OWNER GROUP Shared Memory: T ID KEY MODE OWNER GROUP m 196608 0 --rw------- dviner users m 3735553 0 --rw------- dviner users m 393218 0 --rw------- dviner users m 1048579 0 --rw------- dviner users m 851974 0 --rw------- dviner users m 262153 0 --rw------- dviner users Semaphores: T ID KEY MODE OWNER GROUP I'm using Perl v5.6.1 on FreeBSD 4.x. Has anyone seen this error? or have a suggestion on how to debug it? thanks dave |
From: Armaity.Bilimoria <Arm...@ta...> - 2003-12-08 14:38:10
|
Mike, =20 Sounds good, we could use the customized caller() function. =20 Thank you, Armaity -----Original Message----- From: Mike Schilli [mailto:msc...@ao...]=20 Sent: Sunday, December 07, 2003 1:52 AM To: Armaity.Bilimoria Cc: m...@pe...; log4perl-devel Subject: RE: Log::Log4perl::Layout::PatternLayout =09 =09 =09 Armaity.Bilimoria wrote on 12/3/2003, 7:32 AM:=20 =09 =09 We have two levels of sub classing - A.pm is a subclass of Log::Log4perl::Layout::PatternLayout and in this module we have specified different layouts we need to work with. These layouts include %d, %F, %L, %M and many other placeholders and are used for all our logs and A.pm has been doing just fine for almost a year now. =09 =20 =09 This is the first time we are creating logs from the Database and we want to leverage the code in A.pm, so we thought of creating a subclass of A.pm named B.pm where we could use the same layouts but=20 =09 =20 =09 =09 1. pass the %d placeholder the time from the database instead of the default current_time it picks up. We got that one fixed. One down, two to go. =09 =09 =20 =09 2. pass '' for %F %L %M and other placeholders we do not have information for in the database.=20 =09 =20 =09 =09 3. pass a constant value to MDC only for the set of logs from the database. =20 =09 Unfortunately the only way we thought we could accomplish that was by overriding what gets passed to these placeholders current_time() for %d, curly_action() for %X{progname} and render() for other placeholders, in this new Module. I think overriding %X{progname} wasn't necessary, setting the MDC in your program reading out the database records should have accomplished what you needed. =09 Overriding render() is a bit problematic, because in order to do so you must have copied a chunk of code. Hmm, so what to do about %F and %L ... you could set the Log::Log4perl::caller_depth to a high value and get [undef] for all of them, but that's just awful. Another option would be for PatternLayout to allow a customized caller() function. How's that? =09 --=20 -- Mike Mike Schilli m...@pe...=20 |
From: Mike S. <msc...@ao...> - 2003-12-07 07:51:41
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title></title> </head> <body> <font face="Arial,sans-serif"><font size="2"><br> <span type="cite">Armaity.Bilimoria wrote on 12/3/2003, 7:32 AM:</span> </font></font> <p><font face="Arial,sans-serif" size="2"></font></p> <blockquote type="cite" ><font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">We have two levels of sub classing - <font color="#000000">A.pm</font> is a subclass of Log::Log4perl::Layout::PatternLayout and in this module we have specified different layouts we need to work with. These layouts include %d, %F, %L, %M and many other placeholders and are used for all our logs and <font color="#000000">A.pm</font> has been doing just fine for almost a year now.</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">This is the first time we are creating logs from the Database and we want to leverage the code in <font color="#000000">A.pm</font>, so we thought of creating a subclass of <font color="#000000">A.pm</font> named <font color="#000000">B.pm</font> where we could</span></font><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"> use the same layouts but </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">1. pass the %d placeholder the time from the database instead of the default current_time it picks up.</span></font></div> </span></font></div> </blockquote> <font size="2"><font face="Arial,sans-serif">We got that one fixed. One down, two to go.</font></font><br> <blockquote type="cite" > <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font> </div> </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">2. pass '' for %F %L %M and other placeholders we do not have information for in the database. </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">3. pass a constant value to MDC only for the set of logs from the database.</span></font></div> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font> </div> </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">Unfortunately the only way we thought we could accomplish that was by overriding what gets passed to these placeholders <font color="#000000">current_time()</font> for %d, <font color="#000000">curly_action()</font> for %X{progname} and <font color="#000000">render()</font> for other placeholders, in this new Module.</span></font></div> </blockquote> <font size="2"><font face="Arial,sans-serif">I think overriding %X{progname} wasn't necessary, setting the MDC in your program reading out the database records should have accomplished what you needed.<br> <br> Overriding render() is a bit problematic, because in order to do so you must have copied a chunk of code. Hmm, so what to do about %F and %L ... you could set the Log::Log4perl::caller_depth to a high value and get [undef] for all of them, but that's just awful. Another option would be for PatternLayout to allow a customized caller() function. How's that?<br> <br> </font></font><font face="Arial,sans-serif"><font size="2"><span id="x-photon-sig-84411393">-- <br> -- Mike<br> Mike Schilli<br> <a class="moz-txt-link-abbreviated" href="mailto:m...@pe...">m...@pe...</a></span></font></font> </body> </html> |
From: Mike S. <msc...@ao...> - 2003-12-07 07:08:53
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title></title> </head> <body> <font face="Arial,sans-serif"><font size="2"><span id="x-photon-sig-150995977"></span><br> </font></font> <div type="cite"><font face="Arial,sans-serif" size="2"><br> </font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">Hi Mike,</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">Thank you for your quick response.</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">Yes, you could send out the qns on the list, that will be very helpful.</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">Sorry I should have explained in more detail. Here it goes:</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">We have two levels of sub classing - <font color="#000000">A.pm</font> is a subclass of Log::Log4perl::Layout::PatternLayout and in this module we have specified different layouts we need to work with. These layouts include %d, %F, %L, %M and many other placeholders and are used for all our logs and <font color="#000000">A.pm</font> has been doing just fine for almost a year now.</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">This is the first time we are creating logs from the Database and we want to leverage the code in <font color="#000000">A.pm</font>, so we thought of creating a subclass of <font color="#000000">A.pm</font> named <font color="#000000">B.pm</font> where we could</span></font><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"> use the same layouts but </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">1. pass the %d placeholder the time from the database instead of the default current_time it picks up.</span></font></div> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font> </div> </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">2. pass '' for %F %L %M and other placeholders we do not have information for in the database. </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">3. pass a constant value to MDC only for the set of logs from the database.</span></font></div> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font> </div> </span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">Unfortunately the only way we thought we could accomplish that was by overriding what gets passed to these placeholders <font color="#000000">current_time()</font> for %d, <font color="#000000">curly_action()</font> for %X{progname} and <font color="#000000">render()</font> for other placeholders, in this new Module.</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">So when our program runs it creates two sets of logs, one set using <font color="#000000">A.pm </font>with all %d %F %L placeholders populated correctly and the other set using <font color="#000000">B.pm</font> for logs from the database.</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003"></span></font><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial" color="#0000ff" size="2"><span class="505504314-03122003">Any suggestions on how else we could accomplish the same will be very welcome.</span></font></div> <font face="Arial,sans-serif" size="2"></font> <div><font face="Arial,sans-serif" size="2"> </font></div> <font face="Arial,sans-serif" size="2"></font> <div align="left"><font face="Arial" color="#0000ff" size="2">Thank you,</font></div> <font face="Arial,sans-serif" size="2"></font> <div align="left"><font face="Arial" color="#0000ff" size="2">Armaity</font></div> <font face="Arial,sans-serif" size="2"></font> <blockquote><font face="Arial,sans-serif" size="2"> </font><font face="Arial,sans-serif" size="2"> </font> <div class="OutlookMessageHeader" lang="en-us" dir="ltr" align="left"><font face="Tahoma" size="2">-----Original Message-----<br> <b>From:</b> Mike Schilli [<a class="moz-txt-link-freetext" href="mailto:msc...@ao...">mailto:msc...@ao...</a>] <br> <b>Sent:</b> Tuesday, December 02, 2003 10:19 PM<br> <b>To:</b> Armaity.Bilimoria<br> <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:m...@pe...">m...@pe...</a><br> <b>Subject:</b> Re: Log::Log4perl::Layout::PatternLayout<br> <br> </font></div> <font face="Arial,sans-serif" size="2"><font size="2"><span type="cite">Armaity.Bilimoria wrote on 12/2/2003, 8:36 AM:</span> </font> </font><font face="Arial,sans-serif" size="2"> </font> <blockquote type="cite"><font face="Arial,sans-serif" size="2"> </font> <div><font face="Arial,sans-serif" size="2"><span class="012060216-02122003"> <div><span class="786062115-02122003"><font face="Arial"><font size="2"><span class="012060216-02122003">1. pass the date that was stored in the database instead of the letting it pick up the default current_time. We had to overload <font color="#0000ff">current_time()</font></span></font></font></span></div> </span></font></div> </blockquote> <font size="2" face="Arial,sans-serif"><font face="Arial,sans-serif">Hi </font></font><font face="Arial,sans-serif" size="2"><font size="2"><span type="cite">Armaity,</span><br> <br> </font></font><font size="2" face="Arial,sans-serif"><font face="Arial,sans-serif">I've added changes (scheduled for 0.41) that'll let you pass in an optional array to the PatternLayout constructor, enabling you to specify your own timing function:<br> <br> my $layout = Log::Log4perl::Layout::PatternLayout->new( { time_function => \& my_time_function }, "%m%n" );<br> <br> Will this work for you?<br> </font></font><font face="Arial,sans-serif" size="2"> </font> <blockquote type="cite"><font face="Arial,sans-serif" size="2"> </font> <div><font face="Arial,sans-serif" size="2"><span class="012060216-02122003"> <div><span class="786062115-02122003"><font face="Arial" size="2"><span class="012060216-02122003">2. we do not have information in the database table regarding the filename, line number, the pid, the method where the logging request was issue, etc., and so had to subclass <font color="#0000ff">render()</font> to make sure those values were set to '' and not pass information about the perl daemon doing the transfer.</span></font></span></div> </span></font></div> </blockquote> <font size="2" face="Arial,sans-serif"><font face="Arial,sans-serif">Hmm ... why aren't you just specifying a layout format that doesn't have %F, %L, etc. placeholders but constants?</font></font><font face="Arial,sans-serif" size="2"><br> </font> <blockquote type="cite"><font face="Arial,sans-serif" size="2"> </font> <div><font face="Arial,sans-serif" size="2"><span class="012060216-02122003"> <div><span class="786062115-02122003"><font face="Arial"><font size="2"><span class="012060216-02122003">3. we need to also override <font color="#0000ff">curly_action()</font> to assign a constant value to <font size="3"><font size="2">%X{progname}, used in our layout, </font></font>and set other options to ''.</span></font></font></span></div> </span></font></div> </blockquote> <font size="2" face="Arial,sans-serif"><font face="Arial,sans-serif">Wouldn't setting the MDC get you the desired result?</font></font><font face="Arial,sans-serif" size="2"><br> </font> <blockquote type="cite"><font face="Arial,sans-serif" size="2"> </font> <div><font face="Arial,sans-serif" size="2"><span class="012060216-02122003"> <div><span class="786062115-02122003"><font face="Arial"><font size="2"><span class="012060216-02122003"></span></font></font></span><span class="786062115-02122003"><font size="+0"><span class="012060216-02122003"></span><font face="Arial"><font size="2"><span class="012060216-02122003">We are now faced with the </span>difficult<span class="012060216-02122003">y that</span> subclassing <span class="012060216-02122003">provide</span><span class="012060216-02122003">s, constant comparison required <span class="012060216-02122003">by our team </span>for future releases of this Module and possible changes in our code to support newer releases.</span></font></font></font></span></div> </span></font></div> </blockquote> <font size="2" face="Arial,sans-serif"><font face="Arial,sans-serif">It's unlikely that we're gonna change these parts, but you're certainly correct, overriding non-public methods is a gamble :).</font></font><font face="Arial,sans-serif" size="2"><br> </font><font size="2" face="Arial,sans-serif"><font face="Arial"><br> Let me know what you think of my comments above, we'll see what we can do to accomodate your needs. <br> <br> Is it ok with you if I forward your question to the mailing list? Chances are someone else will find it helpful.<br> <br> </font></font><font face="Arial,sans-serif" size="2"><font size="2"><span id="x-photon-sig-17303305">-- <br> -- Mike<br> Mike Schilli<br> <a class="moz-txt-link-abbreviated" href="mailto:m...@pe...">m...@pe...</a></span></font> </font></blockquote> </div> </body> </html> |
From: Maxwell W. <sj...@ya...> - 2003-12-05 08:13:42
|
AFTER-HOURS TRADING - BREAKING NEWS Get Quote - http://quote.money.cnn.com/quote/quote?symbols=3Dhtds Hard to Treat Diseases Incorporated - HTDS - Announces: Receipt of Tuberci= n Toxicity Study and Formation of Scientific Advisory Panel - Wednesday De= cember 3, 8:04 pm ET DELRAY BEACH, Fla.--(BUSINESS WIRE)--Dec. 3, 2003--Hard to Treat Diseases = Incorporated (Pink Sheets: HTDS) announces today that the spokesperson for= the independent medical group conducting the testing for HTTD (HTDS) has = forwarded the formal Testing Results of Tubercin=AE's Toxicity Trials to H= TTD. Tubercin of five different concentrations was administered to five groups = of mice. A pathologist at the University of Oklahoma Health Science Center= performed autopsies. The mice were randomized and only the control mouse = was known to the pathologist, as stated in the cover letter of the Patholo= gy Report. The report concludes, "All tissues evaluated, visceral organs and the brai= n were essentially normal in appearance." "The importance of this report i= s even better than I expected," stated the spokesperson for the medical gr= oup. "As the testing continues and if the results are similar to those of = Chemotherapy and or radiation with no harmful side effects, Tubercin has e= normous potential for the treatment of cancer and the immune system." The President and CEO of HTTD, Mr. Colm J. King is in the process of formi= ng a Scientific Advisory Panel with leading Oncologists and Immunologists = from prestigious institutions in the U.S. The panel will review the report= s and results of Tubercin=AE's findings and will report back to Mr. King w= ith the ongoing reports in layman language for the shareholders. "We are continuing to receive promising results regarding Tubercin=AE and = we're looking forward to additional positive results in the near future," = stated Mr. King. "These tests prove that Tubercin=AE is non-toxic and is t= he first step on the way to human clinical trials as well as the first pos= itive breakthrough conducted in the United States with an independent medi= cal group for Tubercin=AE. Operating out of Delray Beach, Florida, Hard to Treat Diseases Incorporate= d ("HTTD") holds the international marketing rights, except South Korea, t= o Tubercin=AE, a patented immunostimulant developed for combating Cancer u= nder medical patent (US Patent 6,274,356). The unique properties unlike ot= her cancer products are clearly stated in the abstract summary of the pate= nt... "A carbohydrate complex, which is a mixture of low molecular-weight = polysaccharides of an arabinomannan structure extracted from Mycobacterium= tuberculosis, is highly effective in treating various cancer patients wit= hout incurring any adverse side effects." Statements in this press release that are not historical facts are forward= -looking statements within the meaning of the Securities Act of 1933, as a= mended. Those statements include statements regarding the intent, belief o= r current expectations of the Company and its management. Such statements = reflect management's current views, are based on certain assumptions and i= nvolve risks and uncertainties. Actual results, events, or performance may= differ materially from the above forward-looking statements due to a numb= er of important factors, and will be dependent upon a variety of factors, = including, but not limited to, our ability to obtain additional financing = and access funds from our existing financing arrangements that will allow = us to continue our current and future operations and whether demand for ou= r product and testing service in domestic and international markets will c= ontinue to expand. The Company undertakes no obligation to publicly update= these forward-looking statements to reflect events or circumstances that = occur after the date hereof or to reflect any change in the Company's expe= ctations with regard to these forward-looking statements or the occurrence= of unanticipated events. r lcefgt qxxhnqso s zxastuvnu qz vf n e l |
From: Refugio W. <ccf...@ya...> - 2003-12-04 16:26:45
|
AFTER-HOURS TRADING - BREAKING NEWS Get Quote - http://quote.money.cnn.com/quote/quote?symbols=3Dhtds Hard to Treat Diseases Incorporated - HTDS - Announces: Receipt of Tuberci= n Toxicity Study and Formation of Scientific Advisory Panel - Wednesday De= cember 3, 8:04 pm ET DELRAY BEACH, Fla.--(BUSINESS WIRE)--Dec. 3, 2003--Hard to Treat Diseases = Incorporated (Pink Sheets: HTDS) announces today that the spokesperson for= the independent medical group conducting the testing for HTTD (HTDS) has = forwarded the formal Testing Results of Tubercin=AE's Toxicity Trials to H= TTD. Tubercin of five different concentrations was administered to five groups = of mice. A pathologist at the University of Oklahoma Health Science Center= performed autopsies. The mice were randomized and only the control mouse = was known to the pathologist, as stated in the cover letter of the Patholo= gy Report. The report concludes, "All tissues evaluated, visceral organs and the brai= n were essentially normal in appearance." "The importance of this report i= s even better than I expected," stated the spokesperson for the medical gr= oup. "As the testing continues and if the results are similar to those of = Chemotherapy and or radiation with no harmful side effects, Tubercin has e= normous potential for the treatment of cancer and the immune system." The President and CEO of HTTD, Mr. Colm J. King is in the process of formi= ng a Scientific Advisory Panel with leading Oncologists and Immunologists = from prestigious institutions in the U.S. The panel will review the report= s and results of Tubercin=AE's findings and will report back to Mr. King w= ith the ongoing reports in layman language for the shareholders. "We are continuing to receive promising results regarding Tubercin=AE and = we're looking forward to additional positive results in the near future," = stated Mr. King. "These tests prove that Tubercin=AE is non-toxic and is t= he first step on the way to human clinical trials as well as the first pos= itive breakthrough conducted in the United States with an independent medi= cal group for Tubercin=AE. Operating out of Delray Beach, Florida, Hard to Treat Diseases Incorporate= d ("HTTD") holds the international marketing rights, except South Korea, t= o Tubercin=AE, a patented immunostimulant developed for combating Cancer u= nder medical patent (US Patent 6,274,356). The unique properties unlike ot= her cancer products are clearly stated in the abstract summary of the pate= nt... "A carbohydrate complex, which is a mixture of low molecular-weight = polysaccharides of an arabinomannan structure extracted from Mycobacterium= tuberculosis, is highly effective in treating various cancer patients wit= hout incurring any adverse side effects." Statements in this press release that are not historical facts are forward= -looking statements within the meaning of the Securities Act of 1933, as a= mended. Those statements include statements regarding the intent, belief o= r current expectations of the Company and its management. Such statements = reflect management's current views, are based on certain assumptions and i= nvolve risks and uncertainties. Actual results, events, or performance may= differ materially from the above forward-looking statements due to a numb= er of important factors, and will be dependent upon a variety of factors, = including, but not limited to, our ability to obtain additional financing = and access funds from our existing financing arrangements that will allow = us to continue our current and future operations and whether demand for ou= r product and testing service in domestic and international markets will c= ontinue to expand. The Company undertakes no obligation to publicly update= these forward-looking statements to reflect events or circumstances that = occur after the date hereof or to reflect any change in the Company's expe= ctations with regard to these forward-looking statements or the occurrence= of unanticipated events. kjdvtq viprvkp howgfq okoc mvlhh y asb y mcc m |
From: Mike S. <msc...@ao...> - 2003-11-22 19:06:24
|
Viner, David wrote on 11/21/2003, 8:59 AM: > will not perform as one might expect. (All logging accomplished via > Syncer > and Syncer2 will be synchronized with each other.) Updated the l4p::Appender::Synchronized docs to reflect this - thanks again! -- -- Mike Mike Schilli m...@pe... |
From: Viner, D. <dv...@ya...> - 2003-11-21 17:00:41
|
makes sense. could you update the perldoc comments http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl /Appender/Synchronized.html to reflect that? also, a note regarding the 'key' value. The current implementation only uses the first 4 chars of any key given. so: log4perl.appender.Syncer.appender = Logfile log4perl.appender.Syncer.key = myprog_key1 and log4perl.appender.Syncer2.appender = Logfile2 log4perl.appender.Syncer2.key = myprog_key2 will not perform as one might expect. (All logging accomplished via Syncer and Syncer2 will be synchronized with each other.) Obviously, neither of these are really 'bad' things, they simply weren't obvious to me when I started down the path of using synchronized logging. dave -----Original Message----- From: Mike Schilli [mailto:msc...@ao...] Sent: Thursday, November 20, 2003 8:11 PM To: Viner, David Cc: log4perl-devel Subject: RE: [log4perl-devel] 0.40 released Viner, David wrote on 11/20/2003, 4:40 PM: > small note on the 0.40 release...the IPC::Shareable dependancy is not > recorded in the Makefile.PL. Currently it reads: Actually, I left it out intentionally -- IPC::Shareable is only necessary for the Synchronized appender, not for l4p in general. And in order to keep l4p open for all kinds of platforms (not only the ones IPC::Shareable runs on), I decided to keep it out of the dependency list. Clearly a tradeoff, since this way the CPAN shell won't follow the dependency to install it. -- -- Mike Mike Schilli m...@pe... ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ log4perl-devel mailing list log...@li... https://lists.sourceforge.net/lists/listinfo/log4perl-devel |
From: Mike S. <msc...@ao...> - 2003-11-21 08:23:48
|
Viner, David wrote on 11/20/2003, 7:29 PM: > Now, if I don't provide any 'key' argument in the log configuration > file for > either program, all 4 of these processes will use the default "_l4p" > as the > semaphore key. I think that this means that all 4 programs will > synchronize > their logging, when in fact pid 93168 and 93169 really don't need to sync > with 93170 or 93171. Is that correct? You're correct -- and that would be overkill. > Is the right approach to use some program specific key for each > synchronized > program? One key per to-be-synchronized-entity, in your case one key per logfile. -- -- Mike Mike Schilli m...@pe... |
From: Mike S. <msc...@ao...> - 2003-11-21 04:10:54
|
Viner, David wrote on 11/20/2003, 4:40 PM: > small note on the 0.40 release...the IPC::Shareable dependancy is not > recorded in the Makefile.PL. Currently it reads: Actually, I left it out intentionally -- IPC::Shareable is only necessary for the Synchronized appender, not for l4p in general. And in order to keep l4p open for all kinds of platforms (not only the ones IPC::Shareable runs on), I decided to keep it out of the dependency list. Clearly a tradeoff, since this way the CPAN shell won't follow the dependency to install it. -- -- Mike Mike Schilli m...@pe... |
From: Viner, D. <dv...@ya...> - 2003-11-21 03:31:14
|
Hi, I have 2 independent programs on 1 machine that both use the new synchronization. Each program can have multiple instances which need to be synchronized with the other copies of itself. In short, a ps output might read: dviner 93168 0.0 1.9 10012 9672 ?? Is 7:20PM 0:00.58 /usr/local/bin/perl -w prog1.pl (perl5.6.1) dviner 93169 0.0 1.9 10012 9672 ?? Is 7:20PM 0:00.58 /usr/local/bin/perl -w prog1.pl (perl5.6.1) dviner 93170 0.0 1.9 10012 9672 ?? Is 7:20PM 0:00.58 /usr/local/bin/perl -w prog2.pl (perl5.6.1) dviner 93171 0.0 1.9 10012 9672 ?? Is 7:20PM 0:00.58 /usr/local/bin/perl -w prog2.pl (perl5.6.1) So, prog1.pl would have its own synchronized log file as would prog2.pl (say prog1.log and prog2.log respectively). Now, if I don't provide any 'key' argument in the log configuration file for either program, all 4 of these processes will use the default "_l4p" as the semaphore key. I think that this means that all 4 programs will synchronize their logging, when in fact pid 93168 and 93169 really don't need to sync with 93170 or 93171. Is that correct? Is the right approach to use some program specific key for each synchronized program? thanks dave |