>>>>> On Wed, 25 Jan 2006 14:58:25 -0500, "Dan Langille" <[EMAIL PROTECTED]> >>>>> said: > > On 25 Jan 2006 at 18:19, Attila Fülöp wrote: > > > Dan Langille wrote: > > > On 24 Jan 2006 at 17:19, Attila Fülöp wrote: > > > > > > > > >>Dan Langille wrote: > > >> > > >>>On 23 Jan 2006 at 20:59, Attila Fülöp wrote: > > >>> > > >>> > > >>> > > >>>>Hi Dan, > > >>>> > > >>>>thanks to you and Lars for the fast update of the bacula port. > > >>>> > > >>>>doing a "portupgrade bacula-server" i encountered two small > > >>>>glitches (or should i say minor problems?). The first is in > > >>>>the Makefile and fixed with the attached patch. This fixes > > >>>>the following output line. > > >>>> > > >>>> > > >>>>>Look at REFIX/share/bacula/update_bacula_tables for > > >>> > > >>> > > >>>Thanks. I'll submit that as a PR. Unless you want to? > > >>> > > >> > > >>Ok, please submit it. > > > > > > > > > Done. We fixed both problems I'll start a new thread regarding the > > > other changes we made, but here is what the server install says now: > > > > > > Look at /usr/local/share/bacula/update_bacula_tables for > > > database update procedure. Details can be found in the > > > ReleaseNotes > > > > > > and: > > > > > > Please note that bacula-server no longer installs the client > > > and that the documentation is only installed with the client > > > (see port sysutils/bacula-client)! > > > > Thanks! > > > > Well i noticed that bconsole is installed with the following > > permission: > > -rwxr-xr-- 1 root wheel 197756 Jan 23 21:06 bconsole > > therefore you can't call bconsole from within RunBefore/After > > scripts since the director runs as user and group bacula. > > A chgrp bacula bconsole should fix this. Not sure whether > > i did a chgrp or a chmod o+x for 1.36. Hopefully i can tell > > you tomorrow. Sorry for not reporting this earlier and the > > inconvenience that may result. > > Like this? > > [EMAIL PROTECTED]:/usr/local/sbin] # ls -l bconsole > -rwxr-xr-- 1 root bacula 179265 Jan 25 07:53 bconsole > [EMAIL PROTECTED]:/usr/local/sbin] #
These permissions look a little bizare to me: 1) Why is it writable? I'm not sure if there is any convension, but all the files in /bin and /usr/bin on my FreeBSD 4.9 machine are not writable. 2) Is there some reason to restrict it to root and bacula? It might be better to do access control by restricting the conf file, because that allows more precise control. 3) Making it world readable allows anyone to copy it and change the permissions anyway! __Martin ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
