Quoting Florian Schnabel <[EMAIL PROTECTED]>:
checked my installations since they are all debian.
doesn't look like it got a fixed UID/GID ...
got 104/104 twice and twice 105/105 ^^
just curious .. but what good would a fixed UID/GID do ?
It is convinient to have fixed UID/GIDs accross systems. For example,
the files
will have correct ownership when moved accross systems (when using
UID/GID based
archive formats or over NFS). This is especially important when
restoring files
without having entry for bacula in /etc/passwd file.
Furthermore, it would be nice to have two usernames for Bacula project. The
file daemon usually needs to run as root and does not require new
username. The director and storage daemon would be best running as two
separate non-root
users. This is because director doesn't need (and shouldn't have) access to
devices. Storage daemon might need access to tape devices (which could be
given by either adding SD user to appropriate group, for example "disk" group
on Red Hat systems, or changing the owner of backup device). I usually use
"bacula-d" and "bacula-s" for director and storage daemon respectively (both
have bacula group as their primary group, bacula-s is additionally member of
disk group). Alternatively, if Debian already uses username "bacula",
usernames could be "bacula" for director and "bacula-s" for storage daemon.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
