Jump to content

Recommended Posts

Posted
True, but that doesn't give you the same information lsof does on *nix. Process Explorer does.

 

But if you are trying to locate which user has kept a file open from a shared drive share and storage manager is the ticket. I agree Process explorer will tell you a lot more info but for basic easy access the other thing works!

Posted

Thanks.

I used intuition in the end. The problem was with a custom app and it was actually IIS holding a log file open..

 

Don't suppose windows servers have anything as advanced as logrotate do they?

Posted
Thanks.

I used intuition in the end. The problem was with a custom app and it was actually IIS holding a log file open..

 

Don't suppose windows servers have anything as advanced as logrotate do they?

 

/sarcasm?

 

No it doesnt, because Windows services are supposed to use the Windows Event Log to log day-to-day activity not flat text files. Generally a windows installer will write to a log file as a one off and most services use the event log. There are always exceptions, but thats the fault of the service, not Windows.

Posted
/sarcasm?

 

No it doesnt, because Windows services are supposed to use the Windows Event Log to log day-to-day activity not flat text files. Generally a windows installer will write to a log file as a one off and most services use the event log. There are always exceptions, but thats the fault of the service, not Windows.

 

I suppose windows applications aren't supposed to use text files for configuring either.

This app uses XML files for configuration and 'standard' log files for logging. Somehow it also requires IIS.

 

without sed, grep and a decent test editor this is taking me 10 times longer than it should! I don't know how you windows admins put up with this O/S Linux is SO much easier !

Posted
/sarcasm?

 

No it doesnt, because Windows services are supposed to use the Windows Event Log to log day-to-day activity not flat text files. Generally a windows installer will write to a log file as a one off and most services use the event log. There are always exceptions, but thats the fault of the service, not Windows.

 

Pretty sure IIS logs to C:\windows\system32\logfiles\W3SVC1 does it not? therefore microsoft don't follow there own principles! they do however create a new file for each day.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...