Am 05.10.2015 um 01:48 schrieb James Bottomley:
> On Sun, 2015-10-04 at 23:06 +, Debian Bug Tracking System wrote:
>> Well, this is apparently an apache configuration problem, causing the
>> service to return a non-zero exit code.
>>
>> Once you fix that, the service should not be marked as fai
Am 05.10.2015 um 10:41 schrieb Michael Biebl:
> Am 05.10.2015 um 01:48 schrieb James Bottomley:
>> On Sun, 2015-10-04 at 23:06 +, Debian Bug Tracking System wrote:
>>> Well, this is apparently an apache configuration problem, causing the
>>> service to return a non-zero exit code.
>>>
>>> Once
Processing commands for cont...@bugs.debian.org:
> retitle 795494 udev: network interfaces incorrectly named if naming rules are
> not in 70-persistent-net.rules
Bug #795494 [udev] udev: network interfaces incorrectly named due to outdated
initrd
Changed Bug title to 'udev: network interfaces in
Benedict Broy [2014-11-23 23:45 +0100]:
> Hi, I have exactly the same problem. In my case, network-manager is
> responsible for shutting down the network connection.
Please let's keep this bug about interfaces configured with ifupdown.
NM is an entirely different mechanism, and unlike ifupdown sys
Hello,
Giuseppe Bilotta [2014-09-16 20:15 +0200]:
> My fstab includes the line
>
> labrador:/oneforall /oneforallnfs auto,exec 0 0
>
> and the nfs share is automatically mounted when a network interface that
> can resolve `labrador` is brought up. I don't use NM nor wicd,
Am 05.10.2015 um 11:15 schrieb Martin Pitt:
> Hello,
>
> Giuseppe Bilotta [2014-09-16 20:15 +0200]:
>> My fstab includes the line
>>
>> labrador:/oneforall /oneforall nfs auto,exec 0 0
>>
>> and the nfs share is automatically mounted when a network interface that
>> can resol
Am 05.10.2015 um 12:07 schrieb Michael Biebl:
> The ifup@.service unit file has DefaultDependencies=no and *no*
> Conflicts=shutdown.target, which means it should *not* be stopped on
> shutdown. This was done this way for exactly the reason you mention.
Originally I designed it that way: no Confli
Michael Biebl [2015-10-05 12:11 +0200]:
> Can someone check if ifup@.service units are stopped on shutdown?
I already did this morning before I wrote that reply, they do get
stopped. I added an "echo XXX; systemctl is-system-running" to
ExecStop=, and I see these on shutdown.
Martin
--
Martin Pi
Package: systemd
Version: 226-4
Hi,
About persistent logging, README.Debian claims :
"systemd will add an ACL for read permissions for users in the "adm" group."
This is not working: after creating /var/log/journal with the "install"
command as instructed in the README.Debian, and even after se
Am 05.10.2015 um 11:15 schrieb Martin Pitt:
> Or we just declare that we don't support manual stops, and you are
> supposed to run "sudo ifdown ethX" to stop an interface. This is also
> reasonable as we consider ifup@.service more like an internal helper
> unit, not an user-visible/actionable one.
Am 05.10.2015 um 12:26 schrieb Raphaël Halimi:
> Package: systemd
> Version: 226-4
>
> Hi,
>
> About persistent logging, README.Debian claims :
>
> "systemd will add an ACL for read permissions for users in the "adm" group."
>
> This is not working: after creating /var/log/journal with the "ins
Processing commands for cont...@bugs.debian.org:
> tags 795494 + pending
Bug #795494 [udev] udev: network interfaces incorrectly named if naming rules
are not in 70-persistent-net.rules
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
795494:
Processing control commands:
> tag -1 pending
Bug #761909 [systemd] systemd does not unmount nfs shares before bringing down
the network interface
Added tag(s) pending.
--
761909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761909
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Control: tag -1 pending
Hello Michael,
Michael Biebl [2015-10-05 12:11 +0200]:
> Originally I designed it that way: no Conflicts=shutdown.target and
> letting networking.service do the clean up on shutdown.
>
> ifup@.service was changed in the mean time. I wonder if the
> PartOf=network.target b
Le 05/10/2015 12:30, Michael Biebl a écrit :
> But the subdirectories of /var/log/journal have the correct ACL set, right?
Yes, you're right, I just noticed it; but using journalctl as a user
won't display system messages (only user messages), which is not the
expected behavior of adding a user in
Am 05.10.2015 um 13:08 schrieb Raphaël Halimi:
> Le 05/10/2015 12:30, Michael Biebl a écrit :
>> But the subdirectories of /var/log/journal have the correct ACL set, right?
>
> Yes, you're right, I just noticed it; but using journalctl as a user
> won't display system messages (only user messages)
Am 05.10.2015 um 13:12 schrieb Michael Biebl:
> Am 05.10.2015 um 13:08 schrieb Raphaël Halimi:
>> Le 05/10/2015 12:30, Michael Biebl a écrit :
>>> But the subdirectories of /var/log/journal have the correct ACL set, right?
>>
>> Yes, you're right, I just noticed it; but using journalctl as a user
>
Am 05.10.2015 um 13:21 schrieb Michael Biebl:
> I wonder if we should fix the documentation to tell people to run
> systemd-tmpfiles /usr/lib/tmpfiles/systemd.conf immediately after
> enabling persistent journal.
We might also consider re-adding
https://anonscm.debian.org/cgit/pkg-systemd/systemd.
Le 05/10/2015 13:21, Michael Biebl a écrit :
> Apparently the files were created before the ACLs have been set for
> /var/log/journal/3deacfa10d0c169adfdeb36c50522bd6
> so the journal files that were created did not inherit the correct ACLs
> from the parent directory.
>
> Possibly you created /va
Hello
On Mon, Oct 5, 2015 at 11:15 AM, Martin Pitt wrote:
>> However, when the network is brought down (manually, or automatically
>> during system shutdown), the mountpoint is not unmounted, causing a
>> number of issues.
>
> This sounds very similar to https://launchpad.net/bugs/1492546 .
> ifu
Package: systemd
Version: 215
Debian GNU/Linux "JESSIE"
Hi
Is it possible, that a user can create custom network profiles in
networkd? Like archuser do with netctl?
Or any planned alternate in systemd?
Greets
alex
signature.asc
Description: OpenPGP digital signature
___
Hello all,
CC'ing Josh as he works with netword a lot and was rather interested
in its integration into Debian.
upstream networkd (and in Debian up to now) defaults to IPForward=no
(see man systemd.network), i. e. if you configure a network interface
through networkd without explicitly setting IP
Martin Pitt [2015-10-05 15:53 +0200]:
> I experimented with something like
> /run/systemd/network/{00,zz}_enable_forwarding.network, but
> *.network files aren't additive in that way, you can only ever have
> one that applies to a particular interface. And changing all
> *.network files programmati
Am 05.10.2015 um 13:57 schrieb Raphaël Halimi:
> Le 05/10/2015 13:21, Michael Biebl a écrit :
>> Apparently the files were created before the ACLs have been set for
>> /var/log/journal/3deacfa10d0c169adfdeb36c50522bd6
>> so the journal files that were created did not inherit the correct ACLs
>> fro
Your message dated Mon, 5 Oct 2015 17:24:52 +0200
with message-id <56129644.5010...@debian.org>
and subject line Re: Bug#800965: systemd networkd profiles--wishlist
has caused the Debian Bug report #800965,
regarding systemd networkd profiles--wishlist
to be marked as done.
This means that you cla
Am 05.10.2015 um 17:35 schrieb Felipe Sateler:
> On 5 October 2015 at 12:20, Michael Biebl wrote:
>> But, when using Storage=persistent, journald will create the directory
>> /var/log/journal/ itself. So this won't help in that case, unless
>> systemd-journald re-added the code to apply ACLs itsel
On 5 October 2015 at 12:20, Michael Biebl wrote:
> Am 05.10.2015 um 13:57 schrieb Raphaël Halimi:
>> Le 05/10/2015 13:21, Michael Biebl a écrit :
>>> Apparently the files were created before the ACLs have been set for
>>> /var/log/journal/3deacfa10d0c169adfdeb36c50522bd6
>>> so the journal files t
Am 05.10.2015 um 17:20 schrieb Michael Biebl:
> Hm, right. There might be a race condition during boot, where
> systemd-journald-flush.service is started before systemd-tmpfiles.service.
> We could order systemd-journald-flush.service *after*
> systemd-tmpfiles.service.
Fwiw, this directly conflic
On 5 October 2015 at 12:37, Michael Biebl wrote:
> Am 05.10.2015 um 17:35 schrieb Felipe Sateler:
>> On 5 October 2015 at 12:20, Michael Biebl wrote:
>>> But, when using Storage=persistent, journald will create the directory
>>> /var/log/journal/ itself. So this won't help in that case, unless
>>
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #776460 (http://bugs.debian.org/776460)
# Bug title: systemd-journald crashed with SIG
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.o
On Mon, Oct 05, 2015 at 03:53:04PM +0200, Martin Pitt wrote:
> CC'ing Josh as he works with netword a lot and was rather interested
> in its integration into Debian.
Thanks, Martin.
> upstream networkd (and in Debian up to now) defaults to IPForward=no
> (see man systemd.network), i. e. if you co
32 matches
Mail list logo
