Quote:
Originally posted by Kelam_Magnus
Try this.
Do a ps -aef|grep (your PID#)
# ps -aef |grep 13647
# ps -aef |grep (parent PID#) To find the process that possibly spawned your process "gzip -c".
If it has a parent PID. a process that spawned this process, then you should try to kill that process.
Keep trying to find the parent in this manner until you find the true parent. Then you should be able to kill this PID as well.
|
Using the -j option of ps under OpenBSD, I was able to identify the PPID.
The PPID? It is 1.
Yeah. I think I am gonna let the gzip -c sit for a while until I absolutely have to reboot the machine (probably sometime in March). It isn't using any more memory and isn't using any CPU so it is really not a problem.
Thanks for the responses!
I wonder what job spawned the gzip with the -c option. I took a look at my cronjob entries and they do not use the -c option. I use gzip --best for my scripts. I need to do some more investigating. There doesn't seem to be any problem with the system over-all.
Weird.
