Bug#502305: ulogd2: Status of package?

2012-05-15 Thread Jim Barber
Hi Pierre.

In your last email from Nov last year, you mention a partial fix for the 
Multiarch problems.

The package files at https://www.wzdftpd.net/downloads/ulogd2-deb/ haven't been 
updated since 27th Dec 2010.
It sounds like you've made a few changes since then.
Would you be able to put your more up to date files somewhere so that we can 
build them please?

Based on the old files, to fix the build dependencies for sid as it stands 
today I need to apply the following patch:

--- ulogd-2.0.0~beta4/debian/control.orig   2010-12-27 18:21:25.0 
+0800
+++ ulogd-2.0.0~beta4/debian/control2012-05-16 12:58:33.977786179 +0800
@@ -7,11 +7,11 @@
 libnfnetlink-dev (>= 0.0.13),
 libnetfilter-conntrack-dev (>= 0.0.28),
 libnetfilter-log-dev (>= 1.0),
-libmysqlclient15-dev | libmysqlclient-dev,
+libmysqlclient-dev,
 libpq-dev,
-libpcap-dev,
-libsqlite-dev,
-libdbi0-dev
+libpcap-dev | libpcap0.8-dev,
+libsqlite3-dev,
+libdbi-dev
 Standards-Version: 3.9.1
 Homepage: http://www.netfilter.org/projects/ulogd/
 #Vcs-Git: git://git.debian.org/collab-maint/ulogd.git


However as Nils Olav Fossum reports, the build will still fail because it can't 
find libraries that are now in the multiarch area.

I think mysql libraries are now also in the multiarch area along with the pcap 
libraries that Nils Olav Fossum identified.

So I guess somehow the LDFLAGS should have a -L/usr/lib/$(DEB_HOST_MULTIARCH) 
parameter added to expand the library search path.
I wasn't really sure how to do that though...
I have some theories but not enough time to try.
I figured it would be better just to email and see if we can get access to your 
latest package files and then work from there.

Regards,

-- 
--
Jim Barber
DDI Health



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fb344e8.6060...@ddihealth.com



Bug#627107: ITP: rtsadmin -- administration tool for managing LIO core target

2011-11-17 Thread Jim Barber
Also I noticed an announcment to the Linux-SCSI mailing list on the
20-Sep-2011 that RTSadmin was being renamed to targetcli.
The GIT repository for RTSadmin was no longer being updated and that a
new git://linux-iscsi.org/targetcli.git repository has been created instead.
A link to the announcement is below.

http://www.spinics.net/lists/linux-scsi/msg54586.html

Does you experimental package take into account this fairly recent change?

Regards,

--
Jim Barber
DDI Health



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ec604da.40...@ddihealth.com



Bug#627107: ITP: rtsadmin -- administration tool for managing LIO core target

2011-11-17 Thread Jim Barber
Hi.

I might be able to help you out with the testing of this package.
We have an old Windows server that was running SANmelody to turn it into a SAN 
server.
As of a couple of days ago we decommissioned it.

It is a SuperMicro server with a 3WARE RAID card and some hot swappable disks.
It is running a pair of QLogic 2462 Fibre Channel host bus adapters.
My plan would be to turn this into a SAN for a couple of VMware ESXi servers 
via the Fibre Channel connections.

I would like to try a Linux solution to still use it as a fibre channel 
attached SAN server.
Do you know if the QLogic Fibre Channel part of RTSadmin is ready?

-- 
--
Jim Barber
DDI Health



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ec5fffb.40...@ddihealth.com



Bug#502305: Temporary packages for ulogd2 : Configuration changes

2011-01-07 Thread Jim Barber

Hi.

Further to my previous email, I've now installed the newly built package 
and here are some observations.


There is a lack of documentation in the built package.
If the build also formatted the doc/ulogd.sgml file in the source area 
into txt and html files to be installed under the /usr/share/doc/ulogd/ 
directory, then there will be a lot more useful information on how to 
configure the new ulogd daemon.


I made the following changes to the /etc/ulogd.conf file.
Take and leave each of them as you like.
I've attached the patch that makes all of these changes to the final 
installed configuration file.


- I've made changes to produce logs in the /var/log/ulogd/ directory 
like the old ulogd v1.23 did.
This way users upgrading from the old ulogd to the new ulogd will still 
find the files in the same location as before.
Likewise I adjusted log file names to match what they were before 
(removed leading ulogd_)
If the package doesn't create the /var/log/ulogd/ directory as part of 
its install, then it would need to be modified to do this as well.


- I changed the log level to notice. I guess you can ignore this, but 
I've left it in the patch.


- I've enabled the ULOG support. This way, people upgrading from the old 
ulogd daemon to the new one will still have their logging working. This 
will give them a chance to transition over from ULOG to NFLOG at their 
convenience.


- There was no XML output plugin built with the package.
So I've commented that plugin out to remove the error message about it 
not being found.
I guess the other approach is to get the package to build that plugin if 
possible.


- I added commented out plugin entries for the SQLITE3 output plugin, 
and the PWSNIFF filter plugin (which maybe you don't want to include).


- Added a [sqlite3] section for the SQLITE3 plugin to match the example 
for SQLLITE3 on the old version of ulogd.


Regards,

--
--
Jim Barber
DDI Health
--- /etc/ulogd.conf.dpkg-dist   2011-01-07 14:00:16.0 +0800
+++ /etc/ulogd.conf 2011-01-07 14:54:57.0 +0800
@@ -9,10 +9,10 @@
 
 
 # logfile for status messages
-logfile="/var/log/ulogd.log"
+logfile="/var/log/ulog/ulogd.log"
 
 # loglevel: debug(1), info(3), notice(5), error(7) or fatal(8)
-loglevel=1
+loglevel=5
 
 ##
 # PLUGIN OPTIONS
@@ -26,7 +26,7 @@
 
 
 plugin="/usr/lib/ulogd/ulogd_inppkt_NFLOG.so"
-#plugin="/usr/lib/ulogd/ulogd_inppkt_ULOG.so"
+plugin="/usr/lib/ulogd/ulogd_inppkt_ULOG.so"
 plugin="/usr/lib/ulogd/ulogd_inpflow_NFCT.so"
 plugin="/usr/lib/ulogd/ulogd_filter_IFINDEX.so"
 plugin="/usr/lib/ulogd/ulogd_filter_IP2STR.so"
@@ -35,15 +35,17 @@
 plugin="/usr/lib/ulogd/ulogd_filter_HWHDR.so"
 plugin="/usr/lib/ulogd/ulogd_filter_PRINTFLOW.so"
 #plugin="/usr/lib/ulogd/ulogd_filter_MARK.so"
+#plugin="/usr/lib/ulogd/ulogd_filter_PWSNIFF.so"
 plugin="/usr/lib/ulogd/ulogd_output_LOGEMU.so"
 plugin="/usr/lib/ulogd/ulogd_output_SYSLOG.so"
-plugin="/usr/lib/ulogd/ulogd_output_XML.so"
+#plugin="/usr/lib/ulogd/ulogd_output_XML.so"
 #plugin="/usr/lib/ulogd/ulogd_output_OPRINT.so"
 #plugin="/usr/lib/ulogd/ulogd_output_NACCT.so"
 #plugin="/usr/lib/ulogd/ulogd_output_PCAP.so"
 #plugin="/usr/lib/ulogd/ulogd_output_PGSQL.so"
 #plugin="/usr/lib/ulogd/ulogd_output_MYSQL.so"
 #plugin="/usr/lib/ulogd/ulogd_output_DBI.so"
+#plugin="/usr/lib/ulogd/ulogd_output_SQLITE3.so"
 plugin="/usr/lib/ulogd/ulogd_raw2packet_BASE.so"
 
 # this is a stack for logging packet send by system via LOGEMU
@@ -53,7 +55,7 @@
 
#stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
 
 # this is a stack for ULOG packet-based logging via LOGEMU
-#stack=ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
+stack=ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
 
 # this is a stack for packet-based logging via LOGEMU with filtering on MARK
 
#stack=log2:NFLOG,mark1:MARK,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
@@ -148,15 +150,15 @@
 #numeric_label=0 # optional argument
 
 [emu1]
-file="/var/log/ulogd_syslogemu.log"
+file="/var/log/ulog/syslogemu.log"
 sync=1
 
 [op1]
-file="/var/log/ulogd_oprint.log"
+file="/var/log/ulog/oprint.log"
 sync=1
 
 [xml1]
-directory="/var/log/"
+directory="/var/log/ulog/"
 sync=1
 
 [pcap1]
@@ -202,6 +204,11 @@
 pass="changeme"
 procedure="INSERT_OR_REPLACE_CT"
 
+[sqlite3]
+table="ulog"
+db="/path/to/sqlite/db"
+buffer=200
+
 [dbi1]
 db="ulog2"
 dbtype="pgsql"


Bug#502305: Temporary packages for ulogd2 : Build dependency wrong

2011-01-06 Thread Jim Barber

Hi.

I just tried to build your packages on a Debian unstable (sid) server 
for the i386 architecture.


I used the following technique...

- Downloaded the following files from:
  https://www.wzdftpd.net/downloads/ulogd2-deb/

ulogd_2.0.0~beta4-1.debian.tar.gz
ulogd_2.0.0~beta4-1.dsc
ulogd_2.0.0~beta4.orig.tar.bz2

- Unpacked the sources and moved into the unpacked directory:

dpkg-source -x ulogd_2.0.0~beta4-1.dsc
cd ulogd-2.0.0~beta4

- Made sure I had the build dependencies installed:

dpkg-checkbuilddeps

  It revealed I had to install the following packages:

autotools-dev
libdbi0-dev
libmysqlclient15-dev | libmysqlclient-dev
libnetfilter-conntrack-dev
libnetfilter-log-dev
libpcap-dev
libpq-dev
libsqlite-dev

  I satisfied the libsqlite-dev dependency by installing libsqlite0-dev.

  The libmysqlclient15-dev package does not exist in sid.
  But libmysqlclient16-dev does instead.
  I installed the libmysqlclient-dev package which pulls it in anyway.

- Built it using the following:

dpkg-buildpackage -b -tc -uc -us

The build failed because it needed the libsqlite3-dev package installed.
Note that the libsqlite3-dev package does not supply the libsqlite-dev 
dependency as mentioned in the Build-Depends.

Further I noticed the package doesn't need libsqlite0-dev at all.

So I redid the steps above, but in the debian/control control file I 
changed the libsqlite-dev build dependency to libsqlite3-dev.

I then uninstalled libsqlite0-dev from my system to prove it wasn't needed.

Now the build worked successfully.

So in summary, the changes to the Build-Depends line in the 
debian/control file to correct the build are:


- Change sqlite-dev to sqlite3-dev

- Remove libmysqlclient15-dev OR change it to libmysqlclient16-dev

Regards,

--
------
Jim Barber
DDI Health



--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d26ab2b.2070...@ddihealth.com