You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to understand why Haraka is not autoreloading configfiles when they are not edited by a editor on localhost.
I have tried sharing configs on a NFS-share, Gluster Volume and pulling it from an rsync-daemon but the autoreloading is not triggered. How does it work?
If I edit a file on localhost, I get the following:
inotifywait -r -e modify,attrib,close_write,move,create,delete /srv/haraka-outbound/config
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
/srv/haraka-outbound/config/ CREATE 4913
But if localhost pulls the files from a remote rsync-server:
inotifywait -r -e modify,attrib,close_write,move,create,delete /srv/haraka-outbound/config
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
/srv/haraka-outbound/config/ ATTRIB,ISDIR
Is this the reason that haraka does not see the changes to the files?
What is the recommended approach to sync configs between servers?
The text was updated successfully, but these errors were encountered:
Hi,
I am trying to understand why Haraka is not autoreloading configfiles when they are not edited by a editor on localhost.
I have tried sharing configs on a NFS-share, Gluster Volume and pulling it from an rsync-daemon but the autoreloading is not triggered. How does it work?
If I edit a file on localhost, I get the following:
But if localhost pulls the files from a remote rsync-server:
Is this the reason that haraka does not see the changes to the files?
What is the recommended approach to sync configs between servers?
The text was updated successfully, but these errors were encountered: