Bacula init scripts don't stop, status, reload
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bacula (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
service scripts for bacula-director, bacula-sd und bacula-fd don't stop, reload or give status when the respective daemon is launched on a different port (directive dirport, sdport, fdport).
The cause is that the start script generates a PID file with the port number in its name. Despite of that, the stop, reload and status function of the init script queries for a PID with the default port in the PID file name:
"""
status_of_proc -p /var/run/
"""
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bacula (not installed)
ProcVersionSign
Uname: Linux 3.5.0-49-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Mon May 19 16:34:29 2014
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
MarkForUpload: True
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=
SourcePackage: bacula
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in bacula (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Low |
The bug is also occuring in 14.04.