Solved Other directadmin binaries commandline running under nobody?

Richard G

Verified User
Joined
Jul 6, 2008
Messages
14,143
Location
Maastricht
I often do a ps faux command under linux and then I see Directadmin running, normally Directadmin with something short behind it.

When I'm looking now, they look totally different, if I'm correct since 1.660 or 1.661, they look like this now:
Code:
root     2069209  0.0  0.1 3985496 74832 ?       Ssl  Mar26   1:49 /usr/local/directadmin/directadmin server --syslog
nobody   2163184  0.0  0.0 1642920 19628 ?       Sl   Mar26   0:01  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.d
nobody   2800818  0.0  0.0 1642920 19820 ?       Sl   00:21   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.d
nobody   2809839  0.0  0.0 1642920 17632 ?       Sl   00:23   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.d
nobody   2479226  0.0  0.0 1642920 17592 ?       Sl   16:10   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.d

I didn't change anything myself and it's on all servers.
Before it was way shorter and without the "legacy-handler" stuff behind it.

Why is this suddenly changed (didn't see it in the changelog) and what is the benefit of it?
 
This is part of new DA process manager. Previously there were one directadmin process running as root. It used to handle new API call and static content. Followed by one process running as nobody, which sole responsibility was starting numservers amount of process that handles legacy requests. It used to look like:

Code:
root      824833  1.5  0.6 2985808 50172 ?       Ssl  09:24   0:00 /usr/local/directadmin/directadmin server --syslog
nobody    824951  0.9  0.2 1630924 21552 ?       Sl   09:24   0:00  \_ /usr/local/directadmin/directadmin
nobody    824968  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824969  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824970  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824971  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824972  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824973  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824974  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824975  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824976  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin
nobody    824977  0.0  0.0 1630924 6900 ?        S    09:24   0:00      \_ /usr/local/directadmin/directadmin

Now main process running as root is the new process manger and starts the legacy handler process directly and looks like this:

Code:
root      825591  4.2  0.6 3870944 48940 ?       Ssl  09:26   0:00 /usr/local/directadmin/directadmin server --syslog
nobody    825700  0.0  0.2 1704752 17844 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825701  0.3  0.2 1631020 20300 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825702  0.0  0.2 1631020 17720 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825703  0.3  0.2 1704752 20380 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825704  0.0  0.2 1704752 17808 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825705  0.3  0.2 1704752 17808 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825726  0.3  0.2 1704752 19752 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825729  0.3  0.2 1704752 19832 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825739  0.0  0.2 1704752 19924 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog
nobody    825742  0.3  0.2 1631020 17728 ?       Sl   09:26   0:00  \_ /usr/local/directadmin/directadmin legacy-handler --config=data/admin/runtime.directadmin.conf --syslog

One process was eliminated and the legacy processes were renamed to more clearly describe what they do.
 
That makes sense. I didn't expect it to look differently and the 'legacy-handler" gave me the idea it was only for legacy codebase or something.

Thanks for explaining!
 
Back
Top