Re: [systemd-devel] how to add test sysfs nodes, to sys.tar.xz?

[Dan Streetman]

On Thu, Jan 26, 2017 at 9:36 AM, Zbigniew Jędrzejewski-Szmek
 wrote:
> Thanks for working on the tests.
>
> On Thu, Jan 26, 2017 at 09:21:41AM -0500, Dan Streetman wrote:
>> However, I'd like to also add tests for whitespace replacement using
>> actual device $attr{}, which I think means the test/sys.tar.xz file
>> needs to be updated to add device (maybe a NVMe device) nodes that
>> include whitespace in its model and/or serial strings - is that how
>> new test sysfs device nodes are added?  Updating the entire binary
>> seems like a big change just for a few device node files..
> It's only 162k. It's not perfect that we have to update it every time
> we add tests, but it's not too terrible.
>
> If you're feeling ambitious, you might want to convert that tarball to
> a script which generates the nodes. After all, it's just a bunch of
> directories, with symlinks and a few simple text files. Then this will
> be normal text file and git will be able to track changes to it. This
> would a much nicer solution in the long run.

I crafted a script that does that, which isn't complex, although it
isn't simple either.  However, I'm wondering, why not just store the
files directly in git?  It would be simpler than either the tarball or
a script, and git can handle symlinks and binary files, unless there's
some shortcoming that I'm not seeing?

>
> Z.
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Errorneous detection of degraded array

[Luke Pyzowski]

> Does
>   systemctl  list-dependencies  sys-devices-virtual-block-md0.device
> report anything interesting?  I get
>
> sys-devices-virtual-block-md0.device
> ● └─mdmonitor.service

Nothing interesting, the same output as you have above.



> Could you try run with systemd.log_level=debug on kernel command line and 
> upload journal again. We can only hope that it will not skew timings enough 
> but it may prove my hypothesis.

I've uploaded the full debug logs to: 
https://gist.github.com/Kryai/8273322c8a61347e2300e476c70b4d05
In around 20 reboots, the error appeared only twice, certainly with debug 
enabled it is more rare, but it does still occur, but to your correct guess, 
debug logging does affect the exhibition of the race condition.

Reminder of key things in the log:
# cat /etc/systemd/system/mdadm-last-resort@.timer 
[Unit]
Description=Timer to wait for more drives before activating degraded array.
DefaultDependencies=no
Conflicts=sys-devices-virtual-block-%i.device

[Timer]
OnActiveSec=30



# cat /etc/systemd/system/share.mount 
[Unit]
Description=Mount /share RAID partition explicitly
Before=nfs-server.service

[Mount]
What=/dev/disk/by-uuid/2b9114be-3d5a-41d7-8d4b-e5047d223129
Where=/share
Type=ext4
Options=defaults
TimeoutSec=120

[Install]
WantedBy=multi-user.target


Again, if any more information is needed please let me know I'll provide it.


Many thanks,
Luke Pyzowski
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] nspawn --overlay and --read-only

[Fabien Meghazi]

Hi,

With nspawn, when I use the following command:

$ systemd-nspawn --directory=/os --read-only
--overlay=/os/home/foobar:/tmp/home/foobar:/home/foobar
--user=foobar

I expect the user foobar to be able to write in /home/foobar (in the
container) but instead I get a Permission denied.

The man page says:

--read-only:
   Mount the root file system read-only for the container.

Seems like the --read-only is tainting the --overlay option or maybe I
don't get the concept of "root file system" in the nspawn context.
Could someone advice ?

Thanks.

--
Fabien Meghazi
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] How to attach a .socket file to all the network namespaces

[Badrish Adiga H R]

Fixing typos..

On Mon, Jan 30, 2017 at 8:33 PM, Badrish Adiga H R
 wrote:
> Hi,
>
> I want to use socket activated ssh daemon. However currently this is
> working fine only for default namespace.
>
> I just want to make systemd to listen on a tcp port number(22 for ssh)
> on all the network namespaces and to launch sshd@.service on the
> namespace on which ssh request was received. Can you help me in this regard, 
> if there is already a
> solution to this?
>
> regards,
> Badrish
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] How to attach a .socket file to all the network namespaces

[Badrish Adiga H R]

Hi,

I want to use socket activated ssh daemon. However currently this is
working file only for default namespace.

I just want to make systemd to listen on a tcp port number(22 for ssh)
on all the namespaces and to launch sshd@.service on the corresponding
namespace. Can you help me in this regard, if there is already a
solution to this?

regards,
Badrish
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel