|
logrotate seems to me to be finishing its job when
run by run-parts. It lists 16 logs at the beginning and handles them
all according to anacron job email report. It's always logrotate that gets <defunct>. I always get the same process tree listed in the original bug report. I have no idea what run-parts is doing at that time. If there is a way to tell, please let me know. BTW, I was told on Debian's IRC channel that this looks like run-parts is failing to handle some return code returned by logrotate, but logrotate seems to be running fine to me. Clint Adams wrote: Is logrotate finishing its job when run by run-parts? Does it get stuck on anything besides logrotate? What is the run-parts process doing when it's stuck? |
- Bug#379645: debianutils: run-parts gets stuck at logrotate a... Clint Adams
- Bug#379645: debianutils: run-parts gets stuck at logrot... Ahmad Khayyat
- Bug#379645: debianutils: run-parts gets stuck at logrot... Clint Adams
- Bug#379645: debianutils: run-parts gets stuck at lo... Ahmad Khayyat
- Bug#379645: debianutils: run-parts gets stuck at lo... Clint Adams
- Bug#379645: debianutils: run-parts gets stuck a... Ahmad Khayyat

