Tag Info

New answers tagged

0

It looks like either your configuration file /etc/sysconfig/rsyslog or the init script /etc/init.d/rsyslog is damaged. Run "rpm -V rsyslog" to check for modified files in the rsyslog package, check the content of the files which that command reports as changed, and check the content of /etc/sysconfig/rsyslog (not checked by rpm -V).


0

You have to set the right path in your crontab See the output of echo $PATH And put this in your crontab: PATH=... here the output


2

Every Application Pool is (normally) associated with one worker process named w3wp.exe If the application pool becomes unresponsive, you can kill it. It doesn't affect any of the other application pools or IIS over all. All sites using that application pool will be affected, but they may be already. The application pool may start up again automatically, ...



Top 50 recent answers are included