Error Opening /proc/19852/status
- Thread starter dannygoh
- Start date
Same problem
I am getting the same error messages, searched the forum and this is the only post I found for it. Anyone know of a way to prevent this?
DA 1.224 on FreeBSD 4.10-RELEASE-p2 + ipfw & quotas
audio# tail -n 40 errortaskq.log
2004:08:25-23:05:00: Running: Error Opening /proc/19889/status
2004:08:25-23:05:00: Running: Error Opening /proc/19887/status
2004:08:25-23:05:00: Running: Error Opening /proc/19885/status
2004:08:25-23:15:00: Running: Error Opening /proc/19929/status
2004:08:25-23:15:00: Running: Error Opening /proc/19927/status
2004:08:26-00:00:00: Running: Error Opening /proc/20142/status
2004:08:26-00:00:00: Running: Error Opening /proc/20140/status
2004:08:26-00:25:00: Running: Error Opening /proc/20679/status
2004:08:26-00:25:00: Running: Error Opening /proc/20677/status
2004:08:26-00:25:00: Running: Error Opening /proc/20676/status
2004:08:26-04:50:00: Running: Error Opening /proc/22859/status
2004:08:26-04:50:00: Running: Error Opening /proc/22857/status
2004:08:26-04:50:00: Running: Error Opening /proc/22855/status
2004:08:26-05:00:00: Running: Error Opening /proc/22956/status
2004:08:26-05:00:00: Running: Error Opening /proc/22953/status
2004:08:26-05:00:00: Running: Error Opening /proc/22950/status
2004:08:26-10:30:00: Running: Error Opening /proc/25631/status
2004:08:26-10:30:00: Running: Error Opening /proc/25629/status
2004:08:26-11:25:00: Running: Error Opening /proc/25925/status
2004:08:26-11:25:00: Running: Error Opening /proc/25922/status
2004:08:26-11:25:00: Running: Error Opening /proc/25921/status
2004:08:26-14:30:00: Running: Error Opening /proc/26661/status
2004:08:26-21:55:00: Running: Error Opening /proc/29057/status
2004:08:26-21:55:00: Running: Error Opening /proc/29054/status
2004:08:26-21:55:00: Running: Error Opening /proc/29053/status
2004:08:27-01:20:00: Running: Error Opening /proc/36634/status
2004:08:27-01:20:00: Running: Error Opening /proc/36632/status
2004:08:27-08:00:00: Running: Error Opening /proc/39070/status
2004:08:27-09:45:00: Running: Error Opening /proc/39487/status
2004:08:27-09:45:00: Running: Error Opening /proc/39485/status
2004:08:27-09:45:00: Running: Error Opening /proc/39483/status
2004:08:27-09:55:00: Running: Error Opening /proc/39526/status
2004:08:27-11:55:00: Running: Error Opening /proc/40025/status
2004:08:27-11:55:00: Running: Error Opening /proc/40023/status
2004:08:27-11:55:00: Running: Error Opening /proc/40021/status
2004:08:27-13:45:00: Running: Error Opening /proc/40494/status
2004:08:27-13:45:00: Running: Error Opening /proc/40492/status
2004:08:27-13:45:00: Running: Error Opening /proc/40490/status
2004:08:27-18:10:00: Running: Error Opening /proc/41573/status
2004:08:27-18:10:00: Running: Error Opening /proc/41572/status
I am getting the same error messages, searched the forum and this is the only post I found for it. Anyone know of a way to prevent this?
DA 1.224 on FreeBSD 4.10-RELEASE-p2 + ipfw & quotas
audio# tail -n 40 errortaskq.log
2004:08:25-23:05:00: Running: Error Opening /proc/19889/status
2004:08:25-23:05:00: Running: Error Opening /proc/19887/status
2004:08:25-23:05:00: Running: Error Opening /proc/19885/status
2004:08:25-23:15:00: Running: Error Opening /proc/19929/status
2004:08:25-23:15:00: Running: Error Opening /proc/19927/status
2004:08:26-00:00:00: Running: Error Opening /proc/20142/status
2004:08:26-00:00:00: Running: Error Opening /proc/20140/status
2004:08:26-00:25:00: Running: Error Opening /proc/20679/status
2004:08:26-00:25:00: Running: Error Opening /proc/20677/status
2004:08:26-00:25:00: Running: Error Opening /proc/20676/status
2004:08:26-04:50:00: Running: Error Opening /proc/22859/status
2004:08:26-04:50:00: Running: Error Opening /proc/22857/status
2004:08:26-04:50:00: Running: Error Opening /proc/22855/status
2004:08:26-05:00:00: Running: Error Opening /proc/22956/status
2004:08:26-05:00:00: Running: Error Opening /proc/22953/status
2004:08:26-05:00:00: Running: Error Opening /proc/22950/status
2004:08:26-10:30:00: Running: Error Opening /proc/25631/status
2004:08:26-10:30:00: Running: Error Opening /proc/25629/status
2004:08:26-11:25:00: Running: Error Opening /proc/25925/status
2004:08:26-11:25:00: Running: Error Opening /proc/25922/status
2004:08:26-11:25:00: Running: Error Opening /proc/25921/status
2004:08:26-14:30:00: Running: Error Opening /proc/26661/status
2004:08:26-21:55:00: Running: Error Opening /proc/29057/status
2004:08:26-21:55:00: Running: Error Opening /proc/29054/status
2004:08:26-21:55:00: Running: Error Opening /proc/29053/status
2004:08:27-01:20:00: Running: Error Opening /proc/36634/status
2004:08:27-01:20:00: Running: Error Opening /proc/36632/status
2004:08:27-08:00:00: Running: Error Opening /proc/39070/status
2004:08:27-09:45:00: Running: Error Opening /proc/39487/status
2004:08:27-09:45:00: Running: Error Opening /proc/39485/status
2004:08:27-09:45:00: Running: Error Opening /proc/39483/status
2004:08:27-09:55:00: Running: Error Opening /proc/39526/status
2004:08:27-11:55:00: Running: Error Opening /proc/40025/status
2004:08:27-11:55:00: Running: Error Opening /proc/40023/status
2004:08:27-11:55:00: Running: Error Opening /proc/40021/status
2004:08:27-13:45:00: Running: Error Opening /proc/40494/status
2004:08:27-13:45:00: Running: Error Opening /proc/40492/status
2004:08:27-13:45:00: Running: Error Opening /proc/40490/status
2004:08:27-18:10:00: Running: Error Opening /proc/41573/status
2004:08:27-18:10:00: Running: Error Opening /proc/41572/status
- Joined
- Feb 27, 2003
- Messages
- 8,509
Hello,
I wouldn't worry about it. All that's happening is the dataskq is running and checking all pids of the current running programs. It reads in the list first, then goes through each pid checking the name of the program. But because of the little time difference from when the list is read to the time the pid is checked, that pid could have already quit, hence giving the error. It's not really important, and probably doesn't even need to be logged.
John
I wouldn't worry about it. All that's happening is the dataskq is running and checking all pids of the current running programs. It reads in the list first, then goes through each pid checking the name of the program. But because of the little time difference from when the list is read to the time the pid is checked, that pid could have already quit, hence giving the error. It's not really important, and probably doesn't even need to be logged.
John