From: Kern S. <ke...@si...> - 2011-04-01 16:25:16
|
On Friday 01 April 2011 16:24:34 Luca Berra wrote: > On Wed, Mar 30, 2011 at 03:00:07PM +0200, Luca Berra wrote: > >>Philipp, > >> > >>I concur with Eric. The change you proposed will not work. One cannot > >> fix the problem at installation time. It must be fixed when Bacula > >> begins execution, and in some cases the problem may be more fundamental > >> because log files and cons files can be created at any time while Bacula > >> is running. > > > >In this case why does bacula even support -u and -g parameters? > > > >If these parameters do not work as expected they should be either fixed > >or removed. > > sorry wednesday i was in an hurry, > the fix is dead simple, bacula daemons should just reexec themselves > after changing uid/gid. > That is an interesting suggestion, but I am not at all sure it is necessary. Bacula has no problem changing the user and/or group -- it does that internally without re-execing. As I understand the problem it is: if you run the daemons as root, certain files are created with root permission. If you later decide to run the daemons with -u and/or -g, the daemons may not be able to access certain old files that were previously created. In my opinion, that is a one-time sys admin problem due to the options the sys admin changes (or changing options because rpm installs have changed or are different than previously) and, in my opinion, this is best handled by a sys admin and by documentation. However, perhaps I don't understand the problem. |