-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I know the rescue option in the dvd had to be dropped. Too problematic,
and no maintainer.
Could some of it be "rescued"?
The thing that fails most is grub. Just a repair grub, perhaps a repair
missing kernel/initrd?
Once the system boots, the user should be able to repair the rest (hope).
:-)
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAkyodsMACgkQtTMYHG2NR9W3mACeL4xQWJevZF3nzSzbYWKtz3dP
yQMAnjtrUrfJRGrGfoyEouiJN6Q2XH37
=T2Uo
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I prepared updated syslog-ng packages with the close supervision of
Marius Tomaschewski, the maintainer of the syslog-ng package. They are
available in home:czanik in the openSUSE BS. I would like to see these
packages included in Factory, to replace the ancient 2.0 syslog-ng, but
MT seems to have disappeared (no response to e-mails in the past two weeks).
Questions:
- it works fine on my machines, but could anybody else test it?
- what is the proper way to get syslog-ng updated in factory, if the
maintainer seems to be unavailable?
- I have now both 3.0 and 3.1 packages there, called syslog-ng and
syslog-ng31. The ultimate goal is to include 3.1. Should I drop the
current syslog-ng package and rename syslog-ng31 to syslog-ng?
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
Syslog-ng 3.2 beta1 was released over the weekend. It has many
interesting new features:
- modularized, so /usr is no more a problem
- patternize - automatic pattern generation from logs
- correlation - for more info see blogs
- SCL - a config library to ease configuration generation
For a complete list of changes, see the lead developers blog:
http://bazsi.blogs.balabit.com/2010/10/syslog-ng-ose-3-2beta1-released/
The final version of 3.2 will be released before openSUSE 11.4 feature
freeze, so I'd like to update syslog-ng to 3.2.
Questions / problems:
- it is not yet a final version. Can I push it to factory (once some
problems are solved), or I need to wait for the final release coming end
of November?
- for database support, libdbi is needed. Currently it is available only
in Contrib. Could it be imported to factory so database support could be
enabled?
- I get one error and some warning messages regarding libraries. Could
someone take a closer look at them and help me out?
- AppArmor: there are some new files and directories, which is an easy
fix (see below). The problem is SCL, but also affects syslog-ng.conf, if
someone wants to call an external application as log source or
destination. I got some advice previously, but that did not help,
calling external apps still does not work, only when disabling AppArmor
completly. For now I don't use the new features from SCL to avoid this
problem, but would be nice, if we could demo some easy steps to modify
/etc/apparmor.d/sbin.syslog-ng than saying that if one needs to call
external apps, then should disable AppArmor...
A working but not yet perfect version of syslog-ng 3.2 beta1 is
available in the oBS:
https://build.opensuse.org/package/show?package=syslog-ng32&project=home%3A…
- it has glib fixes for factory (thanks go to
cristian.rodriguez(a)opensuse.org)
- ssl is enabled
- no database support yet (libdbi is in contrib)
- system() from SCL is not yet used due to AppArmor troubles
- AppArmor needs some manual editing:
--- sbin.syslog-ng.orig 2010-07-05 13:21:25.000000000 +0200
+++ sbin.syslog-ng 2010-09-29 10:09:51.001748203 +0200
@@ -36,9 +36,10 @@
/etc/hosts.deny r,
/etc/hosts.allow r,
/sbin/syslog-ng mr,
+ /usr/share/syslog-ng/** r,
# chrooted applications
@{CHROOT_BASE}/var/lib/*/dev/log w,
- @{CHROOT_BASE}/var/lib/syslog-ng/syslog-ng.persist rw,
+ @{CHROOT_BASE}/var/lib/syslog-ng/syslog-ng.persist* rw,
@{CHROOT_BASE}/var/log/** w,
@{CHROOT_BASE}/var/run/syslog-ng.pid krw,
@{CHROOT_BASE}/var/run/syslog-ng.ctl rw,
Please give it a try, let me know if you have any problems or fixes (sr
:-) )!
Bye,
--
Peter Czanik (CzP) <czanik(a)balabit.hu>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I'm trying to package syslog-ng 3.2-git, and ran into some troubles.
V3.2 has an interesting new feature, called SCL (system configuration
library), which tries to ease syslog-ng configuration. This works nicely
when apparmor is disabled.
SCL uses a script to generate part of the configuration. So, when
system(); is used in syslog-ng.conf, it actually calls a script, which
generates the missing parts based on the OS. In case of Linux, it's:
linux-6y8u:~ #
/usr/share/syslog-ng/include/scl/system/generate-system-source.sh
unix-dgram("/dev/log");
file("/proc/kmsg" program-override("kernel") flags(kernel));
When apparmor is enabled, this script is not run, instead I see
"permission denied" in the strace output.
Question: how should I modify /etc/apparmor.d/sbin.syslog-ng to be able
to run external scripts and/or applications. This is not only a problem
for SCL, but syslog-ng can use these both as log source and destination.
Once a solution is know, I'd put some comments in sbin.syslog-ng, so
users could extend the AppArmor ruleset easily instead of disabling it...
Bye,
--
Peter Czanik (CzP) <czanik(a)balabit.hu>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Forward this from the linux-xfs list, in hoping that decision-makers will
consider XFS as the default suse OS install choice.
It continually bests other file systems in optimized configuration performance tests
and these new improvements sound like they only add more speed to the equation.
For nearly all systems, disk speed is the bottle neck, so using the best solution
possible should be strongly considered the default choice for all users -- regardless
of 'political' concerns (which seem to often over-rule practicality, unfortunately).
Linda
p.s. I am not part of the xfs project. I've just used it with open suse (or previously,
Suse) since ~ 2002 and have never regretted it.
Current filesystem read rates using XFS are about 1GB/second on sustained multi-gigabyte
reads.
Using 1Gbit ethernet, Samba gets 97MB/s read from disk to 115 MB/s read from memory
and 125MB/s writes to memory or disk.
-------- Original Message --------
Subject: observed significant performance improvement using "delaylog" in a real-world application
Date: Tue, 10 Aug 2010 18:01:33 +0200
From: Peter Niemayer <niemayer(a)isg.de>
To: linux-xfs(a)oss.sgi.com
Hi all,
we use XFS for a very I/O-intensive, in-house developed real-time
database application, and whenever we see new or significantly changed
file-systems becoming available, we run a benchmark using this
application on a conserved, fixed real-world data set.
I'm pleased to state that using the experimental "delaylog" mount option
(in vanilla linux-2.6.35) we measured a 17% performance increase
for our benchmark scenario. (Other mount-options in use both before
and after the "delaylog" option: noatime,nodiratime,nobarrier)
That's a lot given that XFS was the fastest performing file-system
for this application already.
It's also a promising result regarding stability, as several other
tests (using e.g. reiser4 or ceph) in the past led to crashes in the
same benchmark scenario.
So thanks to all contributing developers for this significant optimization!
Regards,
Peter Niemayer
_______________________________________________
xfs mailing list
xfs(a)oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I wonder, if libdbi and libdbi-drivers could be moved from Contrib to
Factory. Reason: syslog-ng's database support is based libdbi. If
libdbi(-drivers) is moved to Factory, then database could be enabled as
part of the next release.
Bye,
--
Peter Czanik (CzP) <czanik(a)balabit.hu>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
I found the following in /var/log/messages
warn:Oct 31 12:37:05 kavanagh kernel: [ 53.434674] systemd[1]: dev-ida-c0d0p2.swap swap process exited, code=exited status=255
warn:Oct 31 12:37:05 kavanagh kernel: [ 53.434750] systemd[1]: Unit dev-ida-c0d0p2.swap entered failed state.
Swap on /dev/ida/c0d0p2 was successfully added though.
--
Per Jessen, Zürich (11.2°C)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello list,
I've recently volunteered to maintain the SCPM package, and it's now
been checked into Factory (around Sept. 21st).
But a few days ago, I got the following message through the
opensuse-packaging mailing list: "Please submit your packages before
Friday afternoon (UTC time) to make sure they will get included in this
release."
So my question is: do I need to do anything special regarding SCPM at
this stage, or is its presence in Factory enough to get it included in
the upcoming 11.4 ?
TIA
Ph. A.
--
*Philippe Andersson*
Unix System Administrator
IBA Particle Therapy |
Tel: +32-10-475.983
Fax: +32-10-487.707
eMail: pan(a)iba-group.com
<http://www.iba-worldwide.com>
