I'm getting continuous message like Aug 15 17:58:08 ns courierd: QUEUE FILE CORRUPTION: inode 535350 Aug 15 17:58:08 ns courierd: QUEUE FILE CORRUPTION: inode 535341 Aug 15 17:58:08 ns courierd: QUEUE FILE CORRUPTION: inode 535352 Aug 15 17:58:08 ns courierd: QUEUE FILE CORRUPTION: inode 535355 Aug 15 17:58:08 ns courierd: QUEUE FILE CORRUPTION: inode 664408
in my logs. I have identified the files with the corresponding inodes. they are all in the tmp directory.
Can i just blow them away? or will that mess all kinds of stuff up? I saw a few past posts where Sam recommended to stop the system, blow the entire queue away and restart it. I'm hoping that was just to shotgun the bad files.
If I know which files they are, can I just blast them? or are the files in the tmp directory references to other files or something?
thanks,
bill
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
