It's most probably some temporary process spawned by your susepics master process (PID=9967 with PPID=1) which lives just for a short time … you can verify this by tracing the PID 9967 for example with strace - you will most probably see fork() which creates the temporary susepics child process (sporadically catched by monit process check) + can trace what the subprocess does.
Regards, Martin On Mar 29, 2012, at 1:46 PM, Gerrit Kühn wrote: > On Thu, 29 Mar 2012 13:28:05 +0200 Martin Pala <[email protected]> > wrote about Re: pid change notice: > > MP> It seems that you application actually creates two "susepics" > MP> processes, one of them has "init" as parent (init's PID=1) and has one > MP> child process "susepics". The init as parent is common when the > MP> process demonizes itself. In your case the pattern based check is not > MP> suitable, as the pattern is not unique and matches two processes. > > But how come that this second process is normally nowhere to be seen? > There is only one: > > fe2 monit.d # pgrep -l susepic > 9967 g1susepics > > > > cu > Gerrit -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
