Well... using a regular mount doesn't work after all, as that results
in an ordering cycle:
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found ordering
cycle on remote-fs.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on home.mount/start
Nov 20 09:35:4
Observe the same behaviour with systemd 228-2, like several people report at
http://forum.siduction.org/index.php?topic=5901.0Double checked that
etc/systemd/system/getty.target.wants/getty@tty1.service as well as
/lib/systemd/system/getty@.service both contain 'IgnoreOnIsolate=yes' One user
in
Package: systemd
Version: 215-17+deb8u2
Severity: normal
Dear maintainers,
summary: Permission problem with files created
below /var/log/journal, systemd-journal group
cannot read.
Details:
On this Jessie system, as a user that's a member
of the systemd-journal group, I run some
`journalctl --s
Package: systemd
Version: 227-2
Severity: normal
Dear systemd maintainers,
thanks for your work with this package, it's really appreciated.
I've noticed some inconsistend behaviour when a service is using
Restart=on-watchdog.
TL;DR: systemd restart the daemon but no more than 3 times.
The beha
Sorry for the long lines looking bad.
Find here a paste: http://paste.debian.net/334235/
--
Arturo Borrero González
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
Am 20.11.2015 um 10:44 schrieb Andreas Krüger:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Dear maintainers,
>
> summary: Permission problem with files created
> below /var/log/journal, systemd-journal group
> cannot read.
>
> Details:
>
> On this Jessie system, as a user
Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
> exited, code=killed, status=6/ABRT
> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Changed
> stop-sigabrt -> failed
It seems your process aborted and you don't
On 20 November 2015 at 13:13, Michael Biebl wrote:
> Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
>> exited, code=killed, status=6/ABRT
>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Changed
>> stop-siga
Am 20.11.2015 um 13:13 schrieb Michael Biebl:
> Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
>> exited, code=killed, status=6/ABRT
>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Changed
>> stop-sigabrt ->
Am 20.11.2015 um 12:52 schrieb Michael Biebl:
>
> How exactly did you create the /var/log/journal directory?
Can you also send us the output of
ls -la /var/log/journal
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.as
On 20 November 2015 at 13:16, Michael Biebl wrote:
> Minor correction: If you want to restart on abort and on shutdown,
> according to man systemd.service [1], you probably want either
> on-failure or on-abnormal
>
Ok, but what happened was clearly that the watchdog timeout was hit,
as you can se
Am 20.11.2015 um 13:16 schrieb Arturo Borrero Gonzalez:
> On 20 November 2015 at 13:13, Michael Biebl wrote:
>> Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
>>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
>>> exited, code=killed, status=6/ABRT
>>> nov 20 12:16:3
Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
> I've noticed some inconsistend behaviour when a service is using
> Restart=on-watchdog.
Btw, please consider raising this issue upstream either as a question on
the mailing list or via the bug tracker
https://github.com/systemd/systemd/iss
On 20 November 2015 at 13:27, Michael Biebl wrote:
> Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
>
>> I've noticed some inconsistend behaviour when a service is using
>> Restart=on-watchdog.
>
> Btw, please consider raising this issue upstream either as a question on
> the mailing list
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/1969
Bug #805442 [systemd] systemd: Automatic logout when changing the Target
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/1969'.
--
805442: http://bugs.debian.org/cgi-bin/bugrepo
Control: forwarded -1 https://github.com/systemd/systemd/issues/1969
Am 19.11.2015 um 19:32 schrieb Singer Michael:
> Hi Michael,
> the new version 228-2 has the error unfortunately not changed.
I looked into this a bit further.
Afaics, this is a regression that was introduced in v227 by commit
8
Ok, from IRC:
aborrero see
http://www.freedesktop.org/software/systemd/man/systemd.service.html#StartLimitInterval=
or in other words, its working as expected
So, closing this bug.
--
Arturo Borrero González
___
Pkg-systemd-maintainers mailing li
(Please ignore post #45 where my misconfigured mail transport totally messed up
formatting - sorry for that)
I observe the same behaviour with systemd 228-2, like several people report at
http://forum.siduction.org/index.php?topic=5901.0
Double checked that etc/systemd/system/getty.target.wants
Your message dated Fri, 20 Nov 2015 13:40:53 +0100
with message-id
and subject line Re: Bug#805623: systemd: weird behaviour using
'Restart=on-watchdog'
has caused the Debian Bug report #805623,
regarding systemd: weird behaviour using 'Restart=on-watchdog'
to be marked as done.
This means that
Am 23.10.2015 um 17:43 schrieb Stephan Sürken:
> So yes, for a non-existing script, that's (changed behaviour) but
> correct.
>
> For the example wicd service however, it should ignore the call like
> before, afaiu.
I think so as well. Could you please raise this issue upstream at
https://github.
Package: systemd
Version: 228-2
Severity: normal
Hello!
systemd currently fails to build from source on sparc64 since the version
of elfutils available on sparc64 is currently outdated (this is a separate
issue which I have already resolved with a workaround and will be fully
resolved with the ne
Your message dated Fri, 20 Nov 2015 14:21:31 +0100
with message-id <564f1e5b.10...@debian.org>
and subject line Re: Bug#804745: systemd: automatic boot has started failing.
manually type "exec startx" for KDE, or, get stuck forever on systemd "[ok]
starting system"
has caused the Debian Bug repor
Processing control commands:
> tags -1 pending
Bug #805631 [systemd] src:systemd: Should build-depend on elfutils >= 0.158
Added tag(s) pending.
--
805631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 pending
Am 20.11.2015 um 13:46 schrieb John Paul Adrian Glaubitz:
> Thus, src:systemd should build-depend on elfutils >= 0.158, the last
> successful
> build of elfutils on sparc64 was 0.157-3 which is why the missing versioned
> build dependency became visible.
http://anonscm.d
Your message dated Fri, 20 Nov 2015 14:29:11 +0100
with message-id <564f2027.9040...@debian.org>
and subject line Re: Bug#800528: systemd: Systemd cannot boot. sysvinit works.
has caused the Debian Bug report #794264,
regarding systemd: System will no longer boot
to be marked as done.
This means t
Your message dated Fri, 20 Nov 2015 14:29:11 +0100
with message-id <564f2027.9040...@debian.org>
and subject line Re: Bug#800528: systemd: Systemd cannot boot. sysvinit works.
has caused the Debian Bug report #800528,
regarding systemd: Systemd cannot boot. sysvinit works.
to be marked as done.
Th
Your message dated Fri, 20 Nov 2015 14:36:15 +0100
with message-id <564f21cf.5030...@debian.org>
and subject line Re: A patch that might work
has caused the Debian Bug report #765622,
regarding A faulty patch prevents systemd from booting up with the dracut
initramfs(while /usr is on a separate pa
Am 20.11.2015 um 12:52 schrieb Michael Biebl:
>
> How exactly did you create the /var/log/journal directory?
Fwiw, I will clarify the documentation in /usr/share/doc/README.Debian,
that the /var/log/journal directory should be created 2755
root:systemd-journal
The set-group ID ensures that newly
Your message dated Fri, 20 Nov 2015 15:33:36 +0100
with message-id <564f2f40.9010...@debian.org>
and subject line Re: Bug#764481: systemd: Verbosity in journalctl is lacking
has caused the Debian Bug report #764481,
regarding systemd: Verbosity in journalctl is lacking
to be marked as done.
This m
On Fri, Nov 20, 2015 at 01:33:04PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the systemd package:
>
> #794264: systemd: System will no longer boot
I have been away from both machines until the last couple of da
Hi,
kdbus has recently been removed from Fedora [1].
Upstream wants to rethink kdbus. Aiui, plans are to move more
functionality (and old dbus1 compat) into userspace.
I suggest we remove the kdbus-dkms package from experimental until we
know more and there is actually new code.
Objections/thoug
On Sun, 16 Aug 2015 18:57:40 +0200 Michael Biebl wrote:
> Package: systemd
> Version: 224-1
> Severity: normal
> File: /etc/X11/xinit/xinitrc.d/50-systemd-user.sh
>
> On Debian, there is apparently no support for /etc/X11/xinit/xinitrc.d/.
> So 50-systemd-user.sh is not run during X session startu
Am 27.10.2015 um 21:54 schrieb Cyril Brulebois:
> Michael Biebl (2015-10-27):
>> I've CCed debian-b...@lists.debian.org, debia...@lists.debian.org and
>> pkg-systemd-maintainers@lists.alioth.debian.org . Please CC them on
>> replies.
>>
>> I especially would like to see an ACK from KiBi/debian-bo
East Legon, P.B 3569
Greater Accra, Ghana.
I am Mrs Elyse V.Dacko.
I would like to apply through this medium for your co-operation to secure an
opportunity to invest and to go into joint business partnership with you. I
have a substantial capital I honorably intend to invest with you into a v
34 matches
Mail list logo
