New answers tagged log-files
At least in IIS 7.5 and newer when using the default W3C log format, you can just add the field Host (cs-host) to the log fields. Either in the GUI or on the command line: %systemroot%\System32\inetsrv\appcmd.exe set config -section:system.applicationHost/sites ...
It's pretty easy/ Just right-click the DNS server, configure logging as required. As Joeqwerty says it's not a pretty log but perfectly readable:
You can enable debug logging on the properties of the DNS server but honestly I don't think that's going to be of much value. The debug log isn't very user friendly.
I don't think Monit is the best choice for assessing the frequency of these error messages. The limitations of the File Content testing routines may make this tricky without going to an external solution. See: http://mmonit.com/monit/documentation/monit.html#file_content_testing Specifically: The content is only being checked every cycle. If content is ...
Apparently there is another user group called adm (not confuse with admin) that is used to read logs. In my Ubuntu Desktop the group was automatically added to my user, but in my server it wasn't so. I just had to run sudo usermod -aG adn _my_username and that fixed the problem.
How about using sudo -i command for the time being and then afterwards do sudo -k? Alternatively, you can change the permission of the directory to 755.
Seems like it's something that's yanking lines from the Apache error log and feeding them to the system event log.. not finding anything in Google for that name, though. Maybe custom to your service provider? At any rate, I guess the question I'd have is: are you having problems with your Apache service because of these dead child processes? Or is the ...
Try this: $ sudo sh -c "cat /dev/null > error.log" The problem is that with the command you used, you are really running two commands: the first cat is run as root (via sudo) but everything else is run as your user. The above method resolves that. This answer over on U&L has more information on this.
Those are the Exchange transaction logs. They are necessary for the proper operation of the mailbox database. The way to "cut them down" is to perform a Full backup of the Information Store with an Exchange aware backup program (like Windows Server Backup) that can flush the transaction logs, which will delete the transaction logs that have been committed to ...
Top 50 recent answers are included