Folks this is puzzling me a lot.

I have two linux servers running caching proxy with similar configurations. We basically start the
caching proxy deamon by using a custom config file. I start the process with the following command
"/usr/sbin/ibmproxy -r ibmproxy_customfile.conf"

Now when I do a ps -ef, everything is normal on server1

server1-p:/opt/ibm/edge/cp/server_root/logs/customfile # ps -ef |grep proxy
nobody 31708 1 0 Nov20 ? 00:00:11 /usr/sbin/ibmproxy -r ibmproxy_customfile.conf


Now when I do the EXACT same steps, ie start the process on server2

I see a bunch of spawened processses in ps -ef


server2-p:/opt/ibm/edge/cp/server_root/logs/customfile # ps -ef |grep proxy
nobody 4196 1 0 14:55 ? 00:00:00 /usr/sbin/ibmproxy -r ibmproxy_customfile.conf
root 4197 4196 0 14:55 ? 00:00:00 /usr/sbin/ibmproxy -r ibmproxy_customfile.conf
nobody 4198 4197 0 14:55 ? 00:00:00 /usr/sbin/ibmproxy -r ibmproxy_customfile.conf
nobody 4199 4197 0 14:55 ? 00:00:00 /usr/sbin/ibmproxy -r ibmproxy_customfile.conf
truncated here to shorten message,


server2-p:/opt/ibm/edge/cp/server_root/logs/customfile # ps -ef |grep proxy |wc -l

127


So this returns 127 spawned processes ? Why is this difference between the two server ? Should it not
just start the one process as requested by
/usr/sbin/ibmproxy -r ibmproxy_customfile.conf


Thanks for you assistance

It looks like that on the second server original process forks a child of itself according to PID and PPID. Hard to tell why without knowing 'ibmproxy' and '*.conf' files. Is there a source code for 'ibmproxy'?