Skip to content
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.

Commit

Permalink
Revert "nfs: run a dedicated dbus daemon for nfs-ganesha"
Browse files Browse the repository at this point in the history
This reverts commit 9d78f73.

Otherwise ganesha consumers can't dynamically update exports using dbus
because the dbus socket is accessible only from inside the container.

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1784562

Signed-off-by: Guillaume Abrioux <[email protected]>
(cherry picked from commit e654565)
  • Loading branch information
guits authored and dsavineau committed Dec 18, 2019
1 parent a3f6531 commit a1d3e41
Showing 1 changed file with 0 additions and 8 deletions.
8 changes: 0 additions & 8 deletions src/daemon/start_nfs.sh
Original file line number Diff line number Diff line change
Expand Up @@ -8,19 +8,12 @@ function start_rpc {

}

function start_dbus {
mkdir -p /run/dbus
dbus-daemon --system
}

function start_nfs {
get_config
check_config

# Init RPC
start_rpc
# Start dbus daemon
start_dbus

if [ ! -e "$RGW_KEYRING" ]; then

Expand All @@ -40,7 +33,6 @@ function start_nfs {
# create ganesha log directory since the package does not create it
mkdir -p /var/log/ganesha/


log "SUCCESS"
# start ganesha, logging both to STDOUT and to the configured location
exec /usr/bin/ganesha.nfsd "${GANESHA_OPTIONS[@]}" -F -L STDOUT "${GANESHA_EPOCH}"
Expand Down

0 comments on commit a1d3e41

Please sign in to comment.