Summary: | Can't add an observer to init (PID = 1) | ||
---|---|---|---|
Product: | frysk | Reporter: | Len DiMaggio <ldimaggi> |
Component: | general | Assignee: | Unassigned <frysk-bugzilla> |
Status: | NEW --- | ||
Severity: | normal | CC: | ajocksch |
Priority: | P1 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | |||
Bug Blocks: | 1553 | ||
Attachments: | 2619 patch |
Description
Len DiMaggio
2006-04-28 14:17:25 UTC
Actually - it's failing for most processes - this bug may be premature as the GUI may not be ready for real testing yet. Not allowed to attach to PID 1, need better error recovery when permission denied - should notify GUI of failure rather than panic (all the hooks are ready). *** Bug 2586 has been marked as a duplicate of this bug. *** With the current state of the druid there is no longer an obvious way to trigger or test this since the druid only lists processes you own, and thus doesn't list process init. Created attachment 1083 [details]
2619 patch
Running frysk-gui as root still exhibits this problem. This patch fixes it by adding EPERM and then catching it in FryskGui. * LinuxTask.java (sendAttach): Handle Errno.Eperm. * Errno.java (Eperm): New. * cni/Errno.cxx (throwErrno): Added EPERM. FYI, the core needs to handle this exception locally. *** Bug 2736 has been marked as a duplicate of this bug. *** FYI - this bug is still present in Frysk as built from CVS head on June 21. Correction - what I meant to say was that if Frysk is run as root, the init process still appears in the gui and can have observers attached to it. As of the RHEL5 latest rpm, the init process should not be in the druid as there are filters in place to exclude it. Additionally, no process wil be shown that does not match Manager.UID/GID == Process.UID/GID |