Package: gmetad
Version: 3.1.2-3.1
Severity: normal
When installing gmetad the package defaults to:
# User gmetad will setuid to (defaults to "nobody")
# default: "nobody"
# setuid_username "nobody"
nobody 5509 0.1 0.1 162920 2252 ? Sl 14:50 0:00
/usr/sbin/gmetad
Why does gmetad not run as user ganglia by default?
And if one changes the configuration and chowns /var/lib/ganglia/rrds
accordingly then the next gmetad update will chown it back to nobody
and break the configuration.
I see 3 options:
1) run as ganglia and remove the option in gmetad.conf
2) add a debconf question as which user to run and chown to and honor
setuid_username to initialize it
3) parse gmetad.conf for setuid_username and chown to that user
MfG
Goswin
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.5-book-1 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages gmetad depends on:
ii adduser 3.112 add and remove users and groups
ii libapr1 1.3.8-1 The Apache Portable Runtime Librar
ii libc6 2.11.1-3 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra
ii libconfuse0 2.7-1 Library for parsing configuration
ii libdbi0 0.8.2-3 Database Independent Abstraction L
ii libexpat1 2.0.1-7 XML parsing C library - runtime li
ii libganglia1 3.1.2-3.1 cluster monitoring toolkit - share
ii libglib2.0-0 2.24.1-1 The GLib library of C routines
ii libpango1.0-0 1.26.2-1 Layout and rendering of internatio
ii libpng12-0 1.2.42-1 PNG library - runtime
ii librrd4 1.4.3-1 time-series data storage and displ
ii libuuid1 2.16.2-0 Universally Unique ID library
ii libxml2 2.7.7.dfsg-2 GNOME XML library
gmetad recommends no packages.
Versions of packages gmetad suggests:
ii ganglia-monitor 3.1.2-3.1 cluster monitoring toolkit - node
pn ganglia-webfrontend <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
