I'm experience the same, also with syslog-ng on a Debian/Jessie system
(powerpc, upgraded from Debian/Wheezy not too long ago):
# dpkg-query --status syslog-ng-core systemd | egrep ^Package\|^Version
Package: syslog-ng-core
Version: 3.5.6-2+b1
Package: systemd
Version: 215-17
# systemctl -p
Martin Pitt [2015-05-08 7:59 +0200]:
Details about [mac]
---
[...]
* It requires a writable /etc/udev/rules.d/ for persistantly storing
the assignment. We don't want/have that with system-image
(touch/snappy).
Sorry, these are Ubuntu specific terms, forgot to
Hello Konstantin,
Konstantin Khomoutov [2015-05-08 13:08 +0300]:
Is it possible to provide a tool (a shell script?) that would print out
the new would-be name of the interface provided by the user so that it
would be possible to migrate remote systems only accessible via SSH?
The closest
On Fri, 8 May 2015 00:33:58 -0700
Josh Triplett j...@joshtriplett.org wrote:
I propose to retire [mac], i. e. drop
/lib/udev/rules.d/75-persistent-net-generator.rules and enable
[ifnames] by default.
[...]
Having spent a non-trivial amount of time fighting
persistent-net.rules on various
Processing commands for cont...@bugs.debian.org:
# problem also present in jessie
found 775458 215-17
Bug #775458 [systemd] systemd: don't start services every few ms if condition
fails
Marked as found in versions systemd/215-17.
thanks
Stopping processing here.
Please contact me if you need
Martin Pitt mp...@debian.org writes:
- [ifnames] For about two years (since 197) upstream's udev has a
builtin persistant name generator which checks firmware/BIOS
provided index numbers or slot names (like biosdevname), falls back
to slot names (PCI numbers,
Note that this makes
Processing control commands:
found 775458 219-8
Bug #775458 [systemd] systemd: don't start services every few ms if condition
fails
Ignoring request to alter found versions of bug #775458 to the same values
previously set
--
775458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775458
Processing control commands:
found 775458 219-8
Bug #775458 [systemd] systemd: don't start services every few ms if condition
fails
Marked as found in versions systemd/219-8.
--
775112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775112
775458:
Hi,
just my opinion, of course, but please let me add:
- changing finger memory is difficult, so I keep entering
'halt' instead of 'poweroff' occasionally
- if one doesn't notice the error, this will waste
electricity
- if it happens on a notebook just before putting it
into a bag, one
Control: tags -1 - moreinfo unreproducible
Control: reassign -1 man-db
Am 08.04.2015 um 12:13 schrieb Michael Biebl:
Control: tags -1 moreinfo unreproducible
Am 10.03.2015 um 23:59 schrieb Samuel Bronson:
Package: systemd
Version: 215-12
Severity: important
File:
Processing control commands:
tags -1 - moreinfo unreproducible
Bug #780235 [systemd] man init brings up systemd(8) despite /sbin/init coming
from sysvinit-core
Removed tag(s) unreproducible and moreinfo.
reassign -1 man-db
Bug #780235 [systemd] man init brings up systemd(8) despite /sbin/init
Hi,
Karsten Merker:
while this probably works resonably well for (semi-)fixed devices
like onboard-NICs and PCI/PCIe cards, it results in a completely
unsuitable behaviour with pluggable devices such as USB network
adapters.
Why?
I can envision two likely scenarios for using a USB adapter.
Just my 0.02$ against using the BIOS method.
I have and Do see inconsistent bios vendor naming used from release to
release of their Firmware updates. I have had to fix HP Propliants servers
numerous time due to a firmware update changing the number and/or order of
SATA ports, PCI and other
On Fri, May 08, 2015 at 09:06:25PM +0200, Karsten Merker wrote:
On Fri, May 08, 2015 at 10:50:30AM -0700, Josh Triplett wrote:
Karsten Merker wrote:
while this probably works resonably well for (semi-)fixed devices
like onboard-NICs and PCI/PCIe cards, it results in a completely
Le vendredi 08 mai 2015 à 07:59 +0200, Martin Pitt a écrit :
Proposal
I propose to retire [mac], i. e. drop
/lib/udev/rules.d/75-persistent-net-generator.rules and enable
[ifnames] by default.
Yes, yes, yes, please.
Let’s get rid of that horrible thing.
--
.''`. Josselin
On Sun, 03 May 2015 17:23:30 +0100 Ben Hutchings b...@decadent.org.uk
wrote:
Control: reassign -1 clock-setup
Control: retitle -1 Missing support for systems without battery-backed RTC
On Sun, 2015-05-03 at 17:40 +0200, Geert Stappers wrote:
Debian installations on hardware with no
Am 09.05.2015 um 03:32 schrieb Michael Biebl:
On Sun, 03 May 2015 17:23:30 +0100 Ben Hutchings b...@decadent.org.uk
1. Install/enable NTP client
2. Disable hwclock-save.service
See below for the changes in systemd
3. Disable e2fsck time check
What exactly do you mean here?
I think these
On Sat, 2015-05-09 at 03:38 +0200, Michael Biebl wrote:
Am 09.05.2015 um 03:32 schrieb Michael Biebl:
On Sun, 03 May 2015 17:23:30 +0100 Ben Hutchings b...@decadent.org.uk
1. Install/enable NTP client
2. Disable hwclock-save.service
See below for the changes in systemd
3. Disable
On Sat, 2015-05-09 at 03:32 +0200, Michael Biebl wrote:
On Sun, 03 May 2015 17:23:30 +0100 Ben Hutchings b...@decadent.org.uk
wrote:
Control: reassign -1 clock-setup
Control: retitle -1 Missing support for systems without battery-backed RTC
On Sun, 2015-05-03 at 17:40 +0200, Geert
On Fri, 8 May 2015 at 21:34 Michael Biebl bi...@debian.org wrote:
I think the failure on uninstallation is just a red herring or just an
aspect of a bigger issue, i.e. your systemd installation is not fully
functional, most likely due to be run under OpenVZ (btw, it would have
been helpful to
Am 08.05.2015 um 14:19 schrieb Brian May:
On Fri, 8 May 2015 at 21:34 Michael Biebl bi...@debian.org wrote:
I think the failure on uninstallation is just a red herring or just an
aspect of a bigger issue, i.e. your systemd installation is not fully
functional, most likely due to be run under
Am 08.05.2015 um 05:22 schrieb Brian May:
On Thu, 7 May 2015 at 22:30 Michael Biebl bi...@debian.org wrote:
So, systemd.postinst seems to fail in the trigger
We do not call systemctl uncondionally here:
_systemctl() {
if [ -d /run/systemd/system ]; then
systemctl $@
fi
}
Am 08.05.2015 um 13:34 schrieb Michael Biebl:
Which kernel version is that? Does it satisfy all requirements as listed
in /usr/share/doc/systemd/README.gz?
I assume, you can reproduce the uninstallation failure on real iron or
can *not* reproduce...
--
Why is it that all of the
23 matches
Mail list logo
