- initial pld releaseauto/ac/vlogger-1_3-1

Changed files:
    vlogger.spec -> 1.1

1 files changed, 48 insertions, 0 deletions

diff --git a/vlogger.spec b/vlogger.spec
new file mode 100644
index 0000000..8b8101a
--- /dev/null
+++ b/vlogger.spec
@@ -0,0 +1,48 @@
+%include        /usr/lib/rpm/macros.perl
+Summary:	virtual web logfile rotater/parser
+Name:		vlogger
+Version:	1.3
+Release:	1
+License:	GPL
+Group:		Networking/Utilities
+Source0:	http://n0rp.chemlab.org/vlogger/%{name}-%{version}.tar.gz
+# Source0-md5:	4170a4bf7ab8b24373458e8ac820c0a1
+Patch0:		%{name}-debian.patch
+URL:		http://n0rp.chemlab.org/vlogger/
+BuildRequires:	rpm-perlprov
+BuildRequires:	perl-TimeDate
+BuildArch:	noarch
+BuildRoot:	%{tmpdir}/%{name}-%{version}-root-%(id -u -n)
+
+%description
+Vlogger is a little piece of code borned to handle dealing with large
+amounts of virtualhost logs. It's bad news that apache can't do this
+on its own. Vlogger takes piped input from apache, splits it off to
+separate files based on the first field. It uses a file handle cache
+so it can't run out of file descriptors. It will also start a new
+logfile every night at midnight, and maintain a symlink to the most
+recent file. For security, it can drop privileges and do a chroot to
+the logs directory.
+
+%prep
+%setup -q
+%patch0 -p1
+
+%build
+
+%install
+rm -rf $RPM_BUILD_ROOT
+
+install -d $RPM_BUILD_ROOT{%{_sbindir},%{_mandir}/man1}
+
+install %{name} $RPM_BUILD_ROOT%{_sbindir}
+install *.1 $RPM_BUILD_ROOT%{_mandir}/man1
+
+%clean
+rm -rf $RPM_BUILD_ROOT
+
+%files
+%defattr(644,root,root,755)
+%doc README *.conf *.sql
+%attr(755,root,root) %{_sbindir}/*
+%{_mandir}/man1/*