I got to configure Exim4 under Etch today for the first time. During initial setup, a little mistake was made, and the alert about the non-empty paniclog was useful, since it led to a fix of the problem. The box is now in situ, and working well, but one little tweak was needed. During invoke-rc.d I get an alert of a non-zero paniclog. The only thing in there is the error message from the original configuration error. This latter alert is not helpful. It leads one to believe there is a mistake in the change you have just made, whereas infact, nothing is wrong. Just my humble opinion you understand. Regards Neil -- Neil Briscoe Adelix Ltd neil.briscoe at adelix.com web: www.adelix.com tel: 0845 230 9592 / fax: 0845 230 9591 / main office: 0845 230 9590 snail: The Old Post Office, Bristol Rd, Hambrook, Bristol BS16 1RY. UK. skype: stonefish001 MSN: nbriscoeuk at hotmail.co.uk Adelix Ltd is a registered company in England & Wales No. 4232156 VAT registration number 779 4232 91 Adelix Ltd is BS EN ISO 9001:2000 Certified (No. GB 12763) Any views expressed in this email communication are those of the individual sender, except where the sender specifically states them to be the views of a member of Adelix Ltd. Adelix Ltd. does not represent, warrant or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors or interference. ------------------------------------------------------------------------------------ Scanned for viruses, spam and offensive content by CensorNet MailSafe Professional Web & E-mail Filtering from www.censornet.com
On Thu, 2007-05-24 at 14:57 +0100, Neil S. Briscoe wrote:> I got to configure Exim4 under Etch today for the first time. > > During initial setup, a little mistake was made, and the alert about the > non-empty paniclog was useful, since it led to a fix of the problem. > > The box is now in situ, and working well, but one little tweak was > needed. During invoke-rc.d I get an alert of a non-zero paniclog. > > The only thing in there is the error message from the original > configuration error. This latter alert is not helpful. It leads one to > believe there is a mistake in the change you have just made, whereas > infact, nothing is wrong. > > Just my humble opinion you understand. > > Regards > Neil >You have to clear out the paniclog to stop the warning. I''m not sure if deleting the file is OK, or if one must have the file with 0 bytes. cat paniclog >> paniclog.1 first to save the error message. You''re not the only one who has suggested changing this behavior. It is by design, but I recall the package maintainers have said they would consider a patch. -- Ross Boylan wk: (415) 514-8146 185 Berry St #5700 ross at biostat.ucsf.edu Dept of Epidemiology and Biostatistics fax: (415) 514-8150 University of California, San Francisco San Francisco, CA 94107-1739 hm: (415) 550-1062
On Thu, May 24, 2007 at 10:36:50AM -0700, Ross Boylan wrote:> You have to clear out the paniclog to stop the warning. I''m not sure if > deleting the file is OK, or if one must have the file with 0 bytes. > > cat paniclog >> paniclog.1 first to save the error message.I usually mv panicloc paniclog-20070524. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don''t trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190