You are not logged in.
Hi,
I just booted my laptop this afternoon and run a system update. I upgraded to shorewall-5.1.10.1-1, shorewall-core-5.1.10.1-1 and shorewall6-5.1.10.1-1. While downloading these and other updates (firefox-57.0.3-1, firefox-i18n-en-gb-57.0.3-1, perl-dbi-1.639-1), I noticed some unexpected NFS activity. I completed the upgrade and ran `systemctl daemon-reload` to restart shorewall, and started to investigate the NFS activity. An autofs (automount) NFS mount point shared from my server was mounted (mount point in my homedir) and I also noticed these processes:
root 5300 1 0 14:54 ? 00:00:00 /bin/sh /usr/bin/shorewall -6 start
root 5322 5300 18 14:54 ? 00:00:34 find -newer /var/lib/shorewall6/firewall
Some other info:
# ls -l /var/lib/shorewall6/firewall
-rwx------ 1 root root 74662 Dec 29 14:59 /var/lib/shorewall6/firewall
Is this expected behaviour? I've never noticed it before. I'm guessing the `find` triggered the autofs mount. But why the need for `find`? I was not able to determine much else before the find command finished. There was not a lot of NFS traffic, but the server is next to my desk and I could see the HDD light flashing away for the duration.
(Edited to add the following)
I should add that the previous shorewall version was 5.1.10-1.
(Edited Sat 30 Dec 12:22:06 GMT 2017)
Solved - This is expected behaviour. See https://sourceforge.net/p/shorewall/mai … /36172339/
The 'find' is triggered by AUTOMAKE=Yes. So if you replaced your older shorewall[6].conf with the latest, AUTOMAKE=Yes is now set by default.
Last edited by Painless (2017-12-30 12:25:37)
Offline