View Issue Details

IDProjectCategoryView StatusLast Update
0000041bareos-coreGeneralpublic2013-03-04 10:32
Reporterpstorz Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
PlatformLinuxOSanyOS Version3
Product Version12.4.2 
Fixed in Version12.4.2 
Summary0000041: start scripts should start the daemons directly as required user/group instead of usig the -g and -u switches.
DescriptionWhen using the -g and -u switches, the crashdumps cannot be created correctly because of missing privileges.

On suse, it is very simple to use
/sbin/startproc /usr/sbin/bareos-dir $2 -u bareos -g bareos -c /etc/bareos/bareos-dir.conf

instead of

/sbin/startproc -u bareos -g bareos /usr/sbin/bareos-dir $2 -c /etc/bareos/bareos-dir.conf

Only the pid file has to be changed to be owned by bareos:bareos.

On Redhat, we have to find out how to start the programms directly under an other user.
TagsNo tags attached.




2013-01-25 16:49

developer   ~0000055

Last edited: 2013-01-25 18:43

This is only a problem for non systemd platforms. systemd configfiles
have already been fixed to have the daemon started as the correct user
and group. So this should be a dying breed.



2013-02-14 09:41

administrator   ~0000101

Is implemented in all starts scripts now

Issue History

Date Modified Username Field Change
2013-01-21 09:46 pstorz New Issue
2013-01-21 09:46 pstorz Status new => assigned
2013-01-21 09:46 pstorz Assigned To => pstorz
2013-01-25 16:49 mvwieringen Note Added: 0000055
2013-01-25 18:43 mvwieringen Note Edited: 0000055
2013-02-14 09:41 pstorz Target Version => 12.4.0
2013-02-14 09:41 pstorz Fixed in Version => 12.4.0
2013-02-14 09:41 pstorz Note Added: 0000101
2013-02-14 09:41 pstorz Status assigned => closed
2013-02-14 09:41 pstorz Assigned To pstorz =>
2013-02-14 09:41 pstorz Resolution open => fixed
2013-03-04 10:32 mvwieringen Product Version => 12.4.2
2013-03-04 10:32 mvwieringen Fixed in Version => 12.4.2