Jedy Wang wrote: > Hi Phi, > > Why we assume that gpm is started by init when you uss pgrep to find if > gpm is running or not?
"pgrep gnome-power-manager" doesn't work so I searched using "pgrep -f -P 1 gnome-power-manager". Without the -f option, pgrep compares to the execuatable name in psinfo, but psinfo doesn't have the entire name, just "gnome-power-man". I thought matching to the init PPID was more unique than "pgrep gnome-power-man" since another executable could possibly start with that string. It's probably unlikely that another executable will start with "gnome-power-man" so maybe that is a good enough fix. Phi > > Regards, > > Jedy > On Wed, 2009-03-11 at 22:08 -0700, Phi Tran wrote: >> Jedy Wang wrote: >>> Hi Phi, >>> >>> The target for gnome 2.24.4 is nv115. I think gpm is started by >>> gnome-session. >> That's the problem. It was an adequate search when GPM was started by >> init, but not when GPM is started by an ordinary process. >> >> Phi >> >>> Regards, >>> >>> Jedy >>> On Wed, 2009-03-11 at 19:56 -0700, Phi Tran wrote: >>>> I ran into an issue with the power button. If you press the power >>>> button, powerd thinks GPM is not running so it will also launch >>>> sys-suspend. The code in powerd previously checked if there is a GPM >>>> process started by init. GPM in 2.24.4 isn't started by init so this >>>> fails. I need to see if there is another adequate search or >>>> fix it another way. >>>> >>>> What is the target for 2.24.4? >>>> >>>> Phi >
