-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/29/2017 3:01 PM, Rob wrote: > Hi, > > First of all, some requested outputs: > > $ /sbin/shorewall version 5.1.10.1 > > $ ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc > noqueue state UNKNOWN group default qlen 1000 link/loopback > 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host > lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host > valid_lft forever preferred_lft forever 2: eth0: > <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP > group default qlen 1000 link/ether 00:1d:09:a8:93:1d brd > ff:ff:ff:ff:ff:ff inet 192.168.1.6/24 brd 192.168.1.255 scope > global eth0 valid_lft forever preferred_lft forever inet6 > fe80::21d:9ff:fea8:931d/64 scope link valid_lft forever > preferred_lft forever 3: wlp12s0: <BROADCAST,MULTICAST> mtu 1500 > qdisc noop state DOWN group default qlen 1000 link/ether > 00:1c:bf:c3:f5:82 brd ff:ff:ff:ff:ff:ff > > $ ip route show default via 192.168.1.254 dev eth0 192.168.1.0/24 > dev eth0 proto kernel scope link src 192.168.1.6 > > 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, > 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 > > 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. > > I should add that the previous shorewall version was 5.1.10-1.
I suspect that the previous version was a earlier :-) 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. - -Tom - -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJaRs33AAoJEJbms/JCOk0Q8IcP/3whsz9hK2E/5AeVe/zHiYOp jxNgpzBDxo9cYVyTIgYPwTQaZpbbqdS3xlfmNaQ5LwoIN85RPiZLCBGyv5dAMfkB sNOvnlzWj/X+UdRGhKM+5hfvuPj80vNJEnwpcZh5zWYkZi9Fx28yGmVJmsNNxNj2 Fczt+uvEKjuqAX627D8kTD6cJB25Q/HHM/vzml6aivU5w/hkbl6wObNQGeqvTLmC 48fo13oDyTIacylDiQLb/Bc7rCtjIaHort+5YIjlgZMsHHtqWSUVRamf9lN8d/F1 hXEUZb/ZWo/CaTEgPOWn86HK0/rryPvevdRsrt4LmWAxMJGBPvJAtrNP0d63z8nQ VS+UPWQG7t8FlNJCN7o4wu5v3SuuokpMzJIDs4va3u341WMTwBi5i7GlFcvd3Qur MDYWuHKCsx0s6xIt6mMQqPfWrTgE06d2vbJbbHkInRoixi7L9DUl2YYgb/UgpoKG PMI6AXHkJZPjpiBYya1UHYGt4lBe9rcnlcf6BrkbHB9TzRqicJqFpHX9S9z2mTn8 cb6DRnBCz0H2vIIa6KRh6rcUcfxJ7jEWjal3hJJIAuFbOCX1S3S2NXjKqfSaWRA4 oZtGlHPvOI8cE6ifvzCkfNons7eWE4Yn63C+tcKW6sBbR+Djp2WK/0LEXbL796eU IpxJ0pZuz4wIXI15bXJw =nkS9 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
