Hi, That's not a smooth change! Although that seems an easy way to differentiate arpwatch traffic from root one, a small message in the .install should be the minimum.
That break most users setup. Regards, On 06/06/2014 19:28, Sergej Pupykin wrote: > Date: Friday, June 6, 2014 @ 19:28:18 > Author: spupykin > Revision: 112774 > > upgpkg: arpwatch 2.1a15-14 > > upd > > Modified: > arpwatch/trunk/PKGBUILD > > ----------+ > PKGBUILD | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > Modified: PKGBUILD > ===========================You didn't notice that you change the mail target > of arpwatch mail. ======================================== > --- PKGBUILD 2014-06-06 17:16:15 UTC (rev 112773) > +++ PKGBUILD 2014-06-06 17:28:18 UTC (rev 112774) > @@ -4,7 +4,7 @@ > > pkgname=arpwatch > pkgver=2.1a15 > -pkgrel=13 > +pkgrel=14 > pkgdesc='Ethernet/FDDI station activity monitor' > arch=('i686' 'x86_64') > url='ftp://ftp.ee.lbl.gov/' > @@ -28,6 +28,8 @@ > sed -i 's/-\(o\|g\) bin/-\1 root/g' Makefile.in > # Update ethercodes with recent OUI. See gen_ethercodes.sh > cp -f "$srcdir/ethercodes.dat" ethercodes.dat > + # Do not spam root user > + sed -i 's|root|arpwatch|' addresses.h.in > } > > build() { > -- Sébastien "Seblu" Luttringer https://seblu.net | Twitter: @seblu42 GPG: 0x2072D77A
signature.asc
Description: OpenPGP digital signature