On Sat, Sep 30, 2017 at 12:43:36PM +0200, Arturo Borrero Gonzalez wrote: > On 30 September 2017 at 12:12, Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx> wrote: > > On Sat, Sep 30, 2017 at 11:48:11AM +0200, Arturo Borrero Gonzalez wrote: > >> On 30 September 2017 at 11:43, Arturo Borrero Gonzalez > >> <arturo@xxxxxxxxxxxxx> wrote: > >> > > >> > Ok, but how could we avoid putting there a complex, arch-dependant path? > >> > >> i.e, in Debian this means a path like: > >> > >> /usr/lib/mips64el-linux-gnuabi64/ulogd/ulogd_filter_IFINDEX.so > >> > >> so user should use /usr/lib/mips64el-linux-gnuabi64/ which is very ugly. > >> If the config file is copied to a machine with a different arch, amd64 > >> for example, then path should be modified to: > >> > >> /usr/lib/x86_64-linux-gnu/ulogd/ > >> > >> Complex and ugly. We should avoid that. I think we should offer a > >> default at build/configure time. > > > > I think @pkglibdir@ in ulogd.conf.in will set this to the > > corresponding arch-dependent folder at configure/build time, right? > > The point is to don't have the ugly string in the config file. > Transparent to the user. Simplify the config file. OK. What if we default to loading all plugins if user specifies no "plugin=" at all in the configuration file? No worries in terms of breaking backward compatibility, so far ulogd2 just bails out if no plugin is available. That would simplify the configuration file as you're searching for. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
