Check your daemon.001 file.  I have had an occasion where, for some reason, the 
legato instance continued writing to the supposedly rolled-over log file, and 
the primary daemon.log had no contents....or contents wholly unrelated to the 
normal processing at least.  Failing that, if you have a unix box use "ls -ltr" 
and find the files that have been most recently modified (at bottom of list) 
and determine if one of them is a daemon file.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of tamal_10
Sent: Tuesday, October 21, 2008 10:08 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] daemon.log file is not generating

Hi,

Networker version: V7.3. No upgradation was done and it is not a new
installation either. The system is running fine though we are facing some
backup problem. But it's hard to find out the reasons as daemon.log files
is old.

+----------------------------------------------------------------------
|This was sent by blue_spring_csdu AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER