On Jul 14, 7:38 am, Lukasz Szybalski <[email protected]> wrote: > On Jul 13, 3:51 pm, Graham Dumpleton <[email protected]> > wrote: > > > > > > > On Jul 14, 3:11 am, Lukasz Szybalski <[email protected]> wrote: > > > > On Jul 13, 11:53 am, Noah Kantrowitz <[email protected]> wrote: > > > > > Might help if you gave the full command line, stack trace, etc etc. > > > > The screen is from a top command, trac is installed via modwsgi with > > > apache2. > > > In which case the Trac instances themselves would show as 'apache' or > > 'httpd'. > > > If using daemon mode you could use display-name option to > > WSGIDaemonProcess to override name of process and then 'ps' and > > 'htop' (but not 'top' AFAIK) will show that new name. Thus you can be > > more confident of which are the Trac processes. > > > > 'Top' command gives me below pid, how can I find out what program is > > > the pid running? It seem like each process is calling some python > > > code that then takes a lot of cpu to run, but I'm not sure where to go > > > from here. > > > Look in the /proc file system for directory corresponding to the > > process ID. There are various files in there including some which show > > process environment, command line etc etc. That presumes your UNIX > > variant has /proc file system. > > > Also look at parent child PID relationships using 'ps' and see if > > these are a process spawned off the Trac processes for some reason. > > ok. So if this was started from modwsgi as part of trac apache2 > installation the process user would be "www-data" in my case. ? > Correct?
Actually, I wasn't thinking of the user the process runs as but the process name itself. That is, mod_wsgi process don't show as 'python'. But yes, if you haven't overridden the user that Trac runs as using 'user' option to WSGIDaemonProcess, then it would be running as Apache user and so would any processes spawned from them. > Since the user name is different this might be some other process > (import2trac, conversion programs that I use to import tickets in) > which are run by that users cron. Sounds like a more logical cause. Graham > I'll look into this deeper tomorrow. > > Thanks, > Lucas -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
