Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Oct 26 15:22:45 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m9QMMiYQ010667 for ; Sun, 26 Oct 2008 15:22:45 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m9QMXRk7023172 for ; Sun, 26 Oct 2008 15:33:28 -0700 Message-Id: <200810262233.m9QMXRk7023172@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: CS551: Final Project: Log File Date: Sun, 26 Oct 2008 15:33:27 -0700 From: Bill Cheng Someone wrote: > In the spec, for logging, it says: > > "You should write error messages into you log file and you may also output > debugging information there. Please begin each debugging lines with // (like > a comment line in C++) and error messages with **. " > > Can you please explain what do we have to write as "error messages" and > "debugging information" ? Anything you want! The grader should be able to do the following to filter out any debugging messages you write into your log file: grep -v "^//" servant.log You should log any error conditions into your logfile. For example, if you cannot open a file or when you cannot write to a file. If you hardcode any filesystem paths, your program may not work in the grading account. If you log all these error messages, there may be a chance that you can do something about it during regrade! So, the bottomline is, you should write anything that you think may help you! -- Bill Cheng // bill.cheng@usc.edu