[systemd-devel] systemd-networkd - Could not append VLANs / operation not permitted

2016-08-11 Thread arnaud gaboury
- Systemd version 213-1 - OS: Arch linux - a systemd nspawn container is running - host network is managed by systemd-networkd After an upgrade, systemd-networkd is broken, exactly the way descibed in this issue #3876[0] Everything was working pefectly before. Config files: /etc/systemd/system/n

[systemd-devel] nspawn container: network broken

2016-08-12 Thread arnaud gaboury
Host distro: arch linux running systemd 230 container distro Fedora 24 running systemd 229 I broke systemd-networkd on the host after an upgrade to 231-1. The issue was the one described here[0]. In order to get back my network, I downgraded to 230 and now network is working on host, BUT still bro

Re: [systemd-devel] nspawn container: network broken

2016-08-12 Thread arnaud gaboury
On Fri, Aug 12, 2016 at 2:20 PM, arnaud gaboury wrote: > Host distro: arch linux running systemd 230 > container distro Fedora 24 running systemd 229 > > I broke systemd-networkd on the host after an upgrade to 231-1. The > issue was the one described here[0]. In order to get back

[systemd-devel] Timer: time format

2016-08-23 Thread arnaud gaboury
I am really sorry for this post as this may sound like a trivial one, but honestly the timer topic is difficult to understand for me (at least the time format). I am looking to run a service twice a day, never mind the time. I understand I must use OnCalendar, but I have no idea for the rest. I w

Re: [systemd-devel] Timer: time format

2016-08-23 Thread arnaud gaboury
On Tue, Aug 23, 2016 at 3:52 PM, arnaud gaboury wrote: > On Tue, Aug 23, 2016 at 3:39 PM, Michael Chapman > wrote: >> On Tue, 23 Aug 2016, arnaud gaboury wrote: >>> >>> I am really sorry for this post as this may sound like a trivial one, >>> but h

Re: [systemd-devel] Timer: time format

2016-08-23 Thread arnaud gaboury
On Tue, Aug 23, 2016 at 3:39 PM, Michael Chapman wrote: > On Tue, 23 Aug 2016, arnaud gaboury wrote: >> >> I am really sorry for this post as this may sound like a trivial one, >> but honestly the timer topic is difficult to understand for me (at >> least the time for

Re: [systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

2016-09-01 Thread arnaud gaboury
On Thu, Sep 1, 2016 at 12:47 PM arnaud gaboury wrote: > I have been moving directories and files between my host and my container > many times since more than one year with no issues. Host is Archlinux and > container Fedora 24 (upgrade to 24 is quite recent: no more than 2 months). &g

[systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

2016-09-01 Thread arnaud gaboury
I have been moving directories and files between my host and my container many times since more than one year with no issues. Host is Archlinux and container Fedora 24 (upgrade to 24 is quite recent: no more than 2 months). I moved a directory today from host to container and this let me, for the

Re: [systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

2016-09-01 Thread arnaud gaboury
On Thu, Sep 1, 2016 at 2:02 PM Lennart Poettering wrote: > On Thu, 01.09.16 10:47, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > > I have been moving directories and files between my host and my container > > many times since more than one year with no issues. Hos

Re: [systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

2016-09-01 Thread arnaud gaboury
On Thu, Sep 1, 2016 at 4:24 PM arnaud gaboury wrote: > On Thu, Sep 1, 2016 at 2:02 PM Lennart Poettering > wrote: > >> On Thu, 01.09.16 10:47, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >> >> > I have been moving directories and files between my host and m

[systemd-devel] Broken network in container

2016-11-18 Thread arnaud gaboury
A recent change (upgrade ?) in my setup broke the network in my container. Network is OK on the host, but not on the container. My setup: Host: Archlinux - % systemctl --version systemd 231 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SE

Re: [systemd-devel] Broken network in container

2016-11-18 Thread arnaud gaboury
On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury wrote: > A recent change (upgrade ?) in my setup broke the network in my container. > Network is OK on the host, but not on the container. > > My setup: > > Host: Archlinux - > % systemctl --version > systemd 231 >

Re: [systemd-devel] Broken network in container

2016-11-18 Thread arnaud gaboury
On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury wrote: > On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury > wrote: > > A recent change (upgrade ?) in my setup broke the network in my container. > Network is OK on the host, but not on the container. > > My setup: > > Host

Re: [systemd-devel] Broken network in container

2016-11-18 Thread arnaud gaboury
On Fri, Nov 18, 2016 at 6:52 PM arnaud gaboury wrote: > On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury > wrote: > > On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury > wrote: > > A recent change (upgrade ?) in my setup broke the network in my container. > Network is OK on

[systemd-devel] systemd-networkd: broken network in container

2016-11-22 Thread arnaud gaboury
Since a few days, after some upgrades, I don't have anymore network in my container. Network is OK on my host --- Host: Archlinux - % systemctl --version systemd 231 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4

Re: [systemd-devel] systemd-networkd: broken network in container

2016-11-22 Thread arnaud gaboury
On Tue, Nov 22, 2016 at 4:54 PM arnaud gaboury wrote: > Since a few days, after some upgrades, I don't have anymore network in my > container. Network is OK on my host > > --- > Host: Archlinux - > % systemctl --version > systemd 231 &

[systemd-devel] UID/GID broken on container

2016-12-12 Thread arnaud gaboury
I am refering here to issue #4078[0] and see if I missed any progress. I am still with a broken UID on my container on some directories. Example: >From inside the container: --- $ ls -la /proc -rw-r--r-- 1 nobody nobody 0 Dec 12 11:4

[systemd-devel] news on Issue # 4078 ?

2016-12-15 Thread arnaud gaboury
I am still with a broken UID/GID container for some specific directories. This is described in issue #4078 [0]. It start to be annoying as I can't upgrade some packages on the Fedora container. At least, I think failed upgrades are related to this issue. Let's take one example: # dnf upgrade iput

[systemd-devel] UID/GID in nspawn container

2016-12-16 Thread arnaud gaboury
Arch host running a nsapwn Fedora 25 container. On host, % systemctl --version systemd 232 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN % uname -r 4.8.13-1-hortensia <<--- custom one ---

Re: [systemd-devel] news on Issue # 4078 ?

2016-12-16 Thread arnaud gaboury
On Thu, Dec 15, 2016 at 7:27 PM Tomasz Torcz wrote: > On Thu, Dec 15, 2016 at 04:37:19PM +0000, arnaud gaboury wrote: > > I am still with a broken UID/GID container for some specific directories. > > This is described in issue #4078 [0]. > > > > It start to be annoy

[systemd-devel] nsapwned container terminal background color

2017-03-19 Thread arnaud gaboury
I am trying with no success to have one background terminal color for the host and another one for the container. Some settings: - on host: window manager : i3 terminal : urxvt-256 -on container: no X, it is a server. Until now, I have tried to write a wrapper script to urxvt on host. This scrip

Re: [systemd-devel] nsapwned container terminal background color

2017-03-20 Thread arnaud gaboury
On Mon, Mar 20, 2017 at 5:12 AM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Sun, Mar 19, 2017 at 09:30:05PM +, Zbigniew Jędrzejewski-Szmek > wrote: > > On Sun, Mar 19, 2017 at 04:37:53PM +0000, arnaud gaboury wrote: > > > I am trying with no suc

[systemd-devel] Systemd weird behavior after upgrade

2017-07-13 Thread arnaud gaboury
OS= Fedora 26 Linux container managed by machinectl % systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list MACHINE CLASS SERVICE

Re: [systemd-devel] Systemd weird behavior after upgrade

2017-07-13 Thread arnaud gaboury
On Thu, Jul 13, 2017 at 2:27 PM arnaud gaboury wrote: > > OS= Fedora 26 > Linux container managed by machinectl > > % systemctl --version > systemd 233 > +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP > +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOM

Re: [systemd-devel] Systemd weird behavior after upgrade

2017-07-13 Thread arnaud gaboury
On Thu, Jul 13, 2017 at 11:02 PM arnaud gaboury wrote: > On Thu, Jul 13, 2017 at 2:27 PM arnaud gaboury > wrote: > >> >> OS= Fedora 26 >> Linux container managed by machinectl >> >> % systemctl --version >> systemd 233 >> +PAM -A

[systemd-devel] Systemd weird behavior after upgrade -

2017-07-13 Thread arnaud gaboury
(no HTML crapps) OS= Fedora 26 Linux container managed by machinectl % systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list MACHINE

Re: [systemd-devel] Systemd weird behavior after upgrade -

2017-07-14 Thread arnaud gaboury
On Thu, Jul 13, 2017 at 11:58 PM Reindl Harald wrote: > > > Am 13.07.2017 um 23:40 schrieb arnaud gaboury: > > (no HTML crapps) > > still HTML and no meaningful quoting to distinct your "i respond to > myself" answer with your initial post - no idea what you ex

[systemd-devel] no user dbus session in container

2017-07-14 Thread arnaud gaboury
% systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list MACHINE CLASS SERVICEOS VERSION ADDRESSES poppy container sys

Re: [systemd-devel] no user dbus session in container

2017-07-19 Thread arnaud gaboury
On Tue, Jul 18, 2017 at 3:09 PM Simon McVittie wrote: > On Fri, 14 Jul 2017 at 12:36:12 +0000, arnaud gaboury wrote: > > After upgrade from Fedora 25 to 26, there is no more user dbus session > for user > > in container. > ... > > On container, user can't connec

[systemd-devel] permissions issues in systemd machine

2017-07-19 Thread arnaud gaboury
Here is my environment: Linux kernel 4.11.3 with usernamespace set to YES % systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list MACH

Re: [systemd-devel] no user dbus session in container

2017-07-19 Thread arnaud gaboury
On Wed, Jul 19, 2017 at 2:18 PM Simon McVittie wrote: > On Wed, 19 Jul 2017 at 09:31:36 +0000, arnaud gaboury wrote: > > Do I really need a per user dbsu session in my container? > > I don't know. Do you? You haven't said anything about how you start the > containe

[systemd-devel] access /proc of nspwan container

2017-09-20 Thread arnaud gaboury
For some reasons (custom kernel with user namespace activated) my container filesystem owners and permissions has lots of errors. In short, some files/folders belong to nobody/nobody when in fact they should be owned by root:root. I can manage to partially fix things from the host where I can chown

[systemd-devel] container /proc/filesystems owned by nobody:can't upgrade

2017-10-03 Thread arnaud gaboury
My host is Archlinux, nspawn container is Fedora 26. Kernel is 4.13.3 I can't fully upgrade my container as some files are owned by nobody:nobody and can't change to root. An example is filesystems. When upgrading, it returns error: < error: unpacking of archive failed on file /proc: cpio: chown >

Re: [systemd-devel] container /proc/filesystems owned by nobody:can't upgrade

2017-10-03 Thread arnaud gaboury
On 10/03/2017 04:35 PM, Anthony Joseph Messina wrote: > On Tuesday, October 3, 2017 3:01:25 AM CDT arnaud gaboury wrote: >> My host is Archlinux, nspawn container is Fedora 26. Kernel is 4.13.3 >> I can't fully upgrade my container as some files are owned by >> nobody:

Re: [systemd-devel] container /proc/filesystems owned by nobody:can't upgrade

2017-10-03 Thread arnaud gaboury
On 10/03/2017 05:19 PM, Mike Gilbert wrote: > On Tue, Oct 3, 2017 at 4:01 AM, arnaud gaboury > wrote: >> My host is Archlinux, nspawn container is Fedora 26. Kernel is 4.13.3 >> I can't fully upgrade my container as some files are owned by >> nobody:nobody and can&#x

Re: [systemd-devel] Basic network with Fedora conatiner

2015-04-29 Thread arnaud gaboury
On Wed, Apr 29, 2015 at 4:48 PM, Dan Williams wrote: > > On Wed, 2015-04-29 at 15:36 +0200, arnaud gaboury wrote: > > After installation of Fedora 22 container, the container (poppy) boots > > but no network. > > > > # journalctl -b -M poppy > > ..

[systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
I already used for a while a container (Arch on Arch). I had two distinct IP and a working setup thanks to good help from Tom Gundersen I am trying to replicate my network settings on a new setup (Fedora on Arch). For now, I am just trying with DHCP. Here the setup on host: -

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering wrote: > On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> I used to boot the container this way : >> # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container >> >> I

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury wrote: > On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering > wrote: >> On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >> >>> I used to boot the container this way : >>> # sys

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015 at 12:48 PM, arnaud gaboury wrote: > On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury > wrote: >> On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering >> wrote: >>> On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:

Re: [systemd-devel] network interface down in container

2015-04-30 Thread arnaud gaboury
On Thu, Apr 30, 2015, 2:22 PM Lennart Poettering wrote: On Thu, 30.04.15 12:48, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > <97><8F> 2: host0 > >Link File: n/a > > Network File: n/a > > Type: ether > >State: off (unma

[systemd-devel] mount crypto_LUKS device in conatiner

2015-05-01 Thread arnaud gaboury
My container will need access to a Luks encrypted device (/dev/sdd4) for its DB. Here is the setup on the host : - # cryptsetup --key-file /etc/keys/poppy.luks luksOpen /dev/bcache0 sdd4_crypt $ lsblk -o NAME,KNAME,MAJ:MIN,FSTYPE,LABEL

[systemd-devel] networkd must start before nspawn@container

2015-05-02 Thread arnaud gaboury
My host/conatiner networking are both managed by systemd-netwrokd. I have a bridge Br0 on host and vb-MyContainer for the conatiner. Both have a fix local IP. I boot container at host boot this way: -- $ cat /etc/systemd/system/systemd-nspawn@.service

Re: [systemd-devel] networkd must start before nspawn@container

2015-05-03 Thread arnaud gaboury
On Sat, May 2, 2015 at 11:27 AM, arnaud gaboury wrote: > > My host/conatiner networking are both managed by systemd-netwrokd. I > have a bridge Br0 on host and vb-MyContainer for the conatiner. Both > have a fix local IP. > > I boot container at h

[systemd-devel] dbus inside nspawn container

2015-05-15 Thread arnaud gaboury
Maybe a stupid question, but shall every container user start a per user dbus session ? Host has a dbus and user session activated, shall it be same in container? Thank you for hints -- google.com/+arnaudgabourygabx ___ systemd-devel mailing list syst

Re: [systemd-devel] dbus inside nspawn container

2015-05-15 Thread arnaud gaboury
On Fri, May 15, 2015 at 2:21 PM, Dimitri John Ledkov wrote: > On 15 May 2015 at 13:07, arnaud gaboury wrote: >> Maybe a stupid question, but shall every container user start a per >> user dbus session ? >> Host has a dbus and user session activated, shall it be same in conta

Re: [systemd-devel] dbus inside nspawn container

2015-05-15 Thread arnaud gaboury
On Fri, May 15, 2015, 4:22 PM Simon McVittie < simon.mcvit...@collabora.co.uk> wrote: On 15/05/15 14:17, Lennart Poettering wrote: > On Fri, 15.05.15 14:07, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >> Maybe a stupid question, but shall every container user start a p

[systemd-devel] error when starting the service : Bad message

2015-05-19 Thread arnaud gaboury
I maybe did a typo, but looking carefully it doesn't seems so. Starting this unit file gives me: - ● gunicorn.service - gunicorn daemon Loaded: error (Reason: Bad message) Active: inactive (dead) May 19 08:45:53 poppy systemd[1]

Re: [systemd-devel] error when starting the service : Bad message

2015-05-19 Thread arnaud gaboury
On Tue, May 19, 2015 at 9:05 AM, arnaud gaboury wrote: > I maybe did a typo, but looking carefully it doesn't seems so. > Starting this unit file gives me: > - > ● gunicorn.service - gunicorn daemon >Loaded

[systemd-devel] SElinux in container

2015-08-23 Thread arnaud gaboury
Here is my setup: Host: Archlinux systemd 224-1 Container: Fedora 22 systemd 219 The container is a server and has vocation to be one day deployed on a dediacted server for production. In this way, I would like to set SElinux (default in Fedora). Unfortunately, doing it in Arch host is not a tri

Re: [systemd-devel] SElinux in container

2015-08-24 Thread arnaud gaboury
On Mon, Aug 24, 2015 at 1:30 PM, Daniel J Walsh wrote: > > > On 08/23/2015 08:10 AM, arnaud gaboury wrote: >> Here is my setup: >> >> Host: Archlinux systemd 224-1 >> Container: Fedora 22 systemd 219 >> >> The container is a server and has vocation to

[systemd-devel] Multi seats

2015-08-28 Thread arnaud gaboury
One year ago, I tried to setup multi seats, see this thread[0]. By that time, I gave up as my configuration was not made for such a fetaure. Now I am back with all the needed tools to do it easily (I think so): - Fedora 22 - lightdm & GDM - an USB 3 plugable dockin station As good how-to on this t

Re: [systemd-devel] Multi seats

2015-08-28 Thread arnaud gaboury
able xorg.conf for your NVIDIA card, not forgetting to put > MatchSeat entries in Device/Screen/ServerLayout sections. > > * Have LightDM 1.12 or newer installed (if you don't use GNOME) In fact I was wrong in my presentation. Login window is now managed by GDM in Fedora 22, not L

[systemd-devel] Kdbus - dbus daemon

2015-08-30 Thread arnaud gaboury
Distro : Arch Systemd : 224 Kdbus AUR package installed (kdbus module is not in default Arch Kernel) nspawn container : Fedora 22, systemd 219 I want to give a try to kdbus. If I read correctly the kdbus[0] website: . Am I right to understand I will no more need dbus.service and I can disable it

Re: [systemd-devel] Multi seats

2015-09-03 Thread arnaud gaboury
IP. > > 2015-08-28 8:42 GMT-03:00 arnaud gaboury : > >> On Fri, Aug 28, 2015 at 1:37 PM, Laércio de Sousa >> wrote: >> > Hi Arnaud! >> > >> > I've been researching systemd-based multi-seat setups with non-KMS video >> > drivers for a

[systemd-devel] Multi seats setup How-to

2015-09-03 Thread arnaud gaboury
I plan to use the systemd mutli-seat features, but I am not sure at all how I must proceed and in waht order. I understand the main principle for mouse and keyboard: detect the device then $ loginctl attach seatNumber DevicePath As for the graphic card, I am lost. OS: Fedora 22 gdm 1 nvidia card 1

Re: [systemd-devel] Multi seats setup How-to

2015-09-03 Thread arnaud gaboury
On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury wrote: > I plan to use the systemd mutli-seat features, but I am not sure at > all how I must proceed and in waht order. I understand the main > principle for mouse and keyboard: detect the device then > $ loginctl attach seatNumber Dev

Re: [systemd-devel] Multi seats setup How-to

2015-09-03 Thread arnaud gaboury
On Thu, Sep 3, 2015 at 2:12 PM, Floris wrote: > Op Thu, 03 Sep 2015 13:51:06 +0200 schreef arnaud gaboury > : > >> On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury >> wrote: >>> >>> I plan to use the systemd mutli-seat features, but I am not sure at >>

Re: [systemd-devel] Multi seats setup How-to

2015-09-03 Thread arnaud gaboury
On Thu, Sep 3, 2015, 3:46 PM Floris wrote: > > I was missing one piece of the puzzle. My USB dock station is > Plugable® UD-3900 USB 3.0 > > > 1- > I had to install the kernel driver for it, following instructions per > this displaylink for

Re: [systemd-devel] Multi seats setup How-to

2015-09-04 Thread arnaud gaboury
On Thu, Sep 3, 2015 at 5:06 PM, arnaud gaboury wrote: > > On Thu, Sep 3, 2015, 3:46 PM Floris wrote: > >> >> I was missing one piece of the puzzle. My USB dock station is >> Plugable® UD-3900 USB 3.0 >> >> ---

Re: [systemd-devel] Multi seats setup How-to

2015-09-05 Thread arnaud gaboury
On Fri, Sep 4, 2015 at 9:36 PM, Floris wrote: > >> I can't create a new seat1, no idea why. >> >> Here is my current configuration: >> >> -nvidia card + nvidia driver + nouveau blacklisted >> - USB 3 dock station with displaylink driver + systemd service >> - gdm >> - systemd 219 >> >> >>

Re: [systemd-devel] Systemd 226: Neither machinectl login nor machinectl shell works

2015-09-05 Thread arnaud gaboury
On Sat, Sep 5, 2015 at 4:20 PM, Tobias Hunger wrote: > Hello, > > I just upgraded to systemd 226 in the hope that machinectl shell will > work better for me than machinectl login. Unfortunately it is not and > machinectl login is also unusable:-/ > > Both produce the "Connected to machine X. Press

Re: [systemd-devel] Multi seats setup How-to

2015-09-06 Thread arnaud gaboury
On Sun, Sep 6, 2015 at 12:53 PM, Lennart Poettering wrote: > On Thu, 03.09.15 13:26, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> I plan to use the systemd mutli-seat features, but I am not sure at >> all how I must proceed and in waht order. I understand the main >

Re: [systemd-devel] Multi seats setup How-to

2015-09-06 Thread arnaud gaboury
On Sun, Sep 6, 2015 at 1:08 PM, Lennart Poettering wrote: > On Sun, 06.09.15 13:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> On Sun, Sep 6, 2015 at 12:53 PM, Lennart Poettering >> wrote: >> > On Thu, 03.09.15 13:26, arnaud gaboury (arnaud.gabo...@gmail.co

Re: [systemd-devel] Multi seats setup How-to

2015-09-06 Thread arnaud gaboury
On Sun, Sep 6, 2015 at 3:36 PM, Lennart Poettering wrote: > On Sun, 06.09.15 13:14, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> On Sun, Sep 6, 2015 at 1:08 PM, Lennart Poettering >> wrote: >> > On Sun, 06.09.15 13:01, arnaud gaboury (arnaud.gabo...@gmail.co

Re: [systemd-devel] Multi seats setup How-to

2015-09-06 Thread arnaud gaboury
On Sun, Sep 6, 2015 at 4:19 PM, Lennart Poettering wrote: > On Sun, 06.09.15 16:02, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> > That's awfully generic... >> > >> > I'd really just be interested in vendor/product ids if the usb hub >>

Re: [systemd-devel] Multi seats setup How-to

2015-09-06 Thread arnaud gaboury
On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering wrote: > On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > I fear this newer Plugable device is not as carefully designed as the > older ones, and uses non-recognizable vendor/product ids... Thus we > ca

Re: [systemd-devel] containers

2015-09-06 Thread arnaud gaboury
On Sun, Sep 6, 2015 at 6:00 PM, Lennart Poettering wrote: > On Sun, 06.09.15 17:49, Michał Zegan (webczat_...@poczta.onet.pl) wrote: > >> Hello. >> >> Is systemd-nspawn intended to eventually become usable for full system >> containers/general use with enough security to run things like vps hostin

Re: [systemd-devel] Multi seats setup How-to

2015-09-06 Thread arnaud gaboury
On Sun, Sep 6, 2015 at 6:53 PM, Lennart Poettering wrote: > On Sun, 06.09.15 18:24, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering >> wrote: >> > On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.c

[systemd-devel] machinectl shell

2015-10-04 Thread arnaud gaboury
First, thank you for this new feature. I do think this is a much more clean way to log as root. I just can't get the correct shell, which is /bin/zsh: /etc/passwd --- root:x:0:0:root:/root:/usr/bin/zsh - $ machinectl shell brings me to sh.

Re: [systemd-devel] machinectl shell

2015-10-04 Thread arnaud gaboury
On Sun, Oct 4, 2015 at 11:34 AM, Tobias Hunger wrote: > Hi Arnaud, > > Am 04.10.2015 11:27 schrieb "arnaud gaboury" : >> >> First, thank you for this new feature. I do think this is a much more >> clean way to log as root. >> >> I just can'

Re: [systemd-devel] machinectl shell

2015-10-04 Thread arnaud gaboury
On Sun, Oct 4, 2015 at 11:49 AM, Tomasz Torcz wrote: > On Sun, Oct 04, 2015 at 11:27:20AM +0200, arnaud gaboury wrote: >> First, thank you for this new feature. I do think this is a much more >> clean way to log as root. >> >> I just can't get the correct shel

[systemd-devel] /etc/dbus-1/session-local.conf

2015-10-04 Thread arnaud gaboury
As I am trying to improve my knowledges in how dbus work, I discovered this file in /etc/dbus-1/session-local.conf unix:path=/run/user/1000/dbus/user_bus_socket -- I Can't remember editing it, but I must have done it. I understand it overrides

Re: [systemd-devel] Machinectl shell/login do not attach to console

2015-10-12 Thread arnaud gaboury
On Mon, Oct 5, 2015 at 2:30 PM, Chris Bell wrote: > Hi all, > > I have an Arch machine with systemd 226, which arch version exactly? I had the same issue with 226. It is gone with 226-3. setup: Arch host running Fedora container. running an Arch container, also > with systemd 226. For whatever re

Re: [systemd-devel] Machinectl shell/login do not attach to console

2015-10-17 Thread arnaud gaboury
Honestly, I don't think your issue has to do with the container systemd version. On my host, archlinux: systemd 227-1 On my container, Fedora 22: sysetemd 219 - # machinectl login poppy [sudo] password for gabx: Connected to machine poppy. Press ^] three time

[systemd-devel] upgrade a Fedora container 22 > 23

2015-11-07 Thread arnaud gaboury
For those of us who are wondering if this can be tricky, I just want to testify you just have to follow Fedora instruction[1] and restart the machine. No issues at all and Fedora will be upgraded to 23. You need to wait a little bit (~ 5-10 mn) after you run # dnf system-upgrade reboot for the sys

[systemd-devel] modules in container

2015-11-08 Thread arnaud gaboury
I am trying to understand how kernel modules are "passed" to nspawn container. My setup: Archlinux host, Fedora 23 container (function = server). Example of what I would like to solve: On container: -- $ systemctl statu

Re: [systemd-devel] modules in container

2015-11-08 Thread arnaud gaboury
On Sun, Nov 8, 2015 at 2:57 PM Richard Weinberger < richard.weinber...@gmail.com> wrote: > On Sun, Nov 8, 2015 at 1:17 PM, arnaud gaboury > wrote: > > I am trying to understand how kernel modules are "passed" to nspawn > container. > > A container must n

[systemd-devel] systemd nspawn container - download speed slow

2015-12-04 Thread arnaud gaboury
Here is my setup: Arch host Fedora 23 nspawn container Network: From host: --- % ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever pref

[systemd-devel] empty a directory in service file as ExecStartPre

2016-01-02 Thread arnaud gaboury
I can't manage to empty a directory as a Exec in a service file. Here is part: --- [Service] User=postgres Environment=REPORTDIR=/storage/psqlReport ExecStartPre=/usr/bin/rm -f ${REPORTDIR}/* ExecStart=MyCommand -

Re: [systemd-devel] empty a directory in service file as ExecStartPre

2016-01-02 Thread arnaud gaboury
post elsewhere as it is OT in this list. Thank you for your help. > > Alternatively 'sh -c "rm .../*" to handle wildcards. > > > On Sat, Jan 2, 2016, 13:39 arnaud gaboury wrote: >> >> I can't m

Re: [systemd-devel] empty a directory in service file as ExecStartPre

2016-01-02 Thread arnaud gaboury
On Sat, Jan 2, 2016 at 1:57 PM, Reindl Harald wrote: > > > Am 02.01.2016 um 13:43 schrieb arnaud gaboury: >> >> ExecStartPre=/usr/bin/rm -f ${REPORTDIR}/ > > > ExecStartPre=/usr/local/scripts/emptydir.sh $REPORTDIR Thank you, but I would prefer to avoid any externa

[systemd-devel] On calendar timer

2016-01-06 Thread arnaud gaboury
I am not sure about how to express date/time in a timer unit. I want the timer to be start every year(*), on month 1,3,5,7,9,11, first day of month at 02:00:00 AM. Here is what I wrote: [Timer] OnCalendar=*-1,3,5,7,9,11-01 02:00:00 Is this correct ? Now if I want instead not the first day of th

Re: [systemd-devel] On calendar timer

2016-01-12 Thread arnaud gaboury
On Tue, Jan 12, 2016 at 6:46 PM, Lennart Poettering wrote: > On Wed, 06.01.16 17:17, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> I am not sure about how to express date/time in a timer unit. >> >> I want the timer to be start every year(*), on month 1,3,5,7,9,1

[systemd-devel] messing with .mount/.automount units

2016-01-25 Thread arnaud gaboury
I run once a week a simple backup with rsync. For that purpose, I wrote a service file (rsync) and a timer unit. They both work with no issues. /etc/systemd/system/backup-external.service [Unit] Description=Backup system to external drive Requi

[systemd-devel] Fwd: messing with .mount/.automount units

2016-01-29 Thread arnaud gaboury
BUMP. I run once a week a simple backup with rsync. For that purpose, I wrote a service file (rsync) and a timer unit. They both work with no issues. /etc/systemd/system/backup-external.service [Unit] Description=Backup system to external driv

Re: [systemd-devel] Fwd: messing with .mount/.automount units

2016-01-30 Thread arnaud gaboury
On Sat, Jan 30, 2016 at 8:11 AM, Andrei Borzenkov wrote: > 29.01.2016 23:07, arnaud gaboury пишет: >> BUMP. >> >> I run once a week a simple backup with rsync. For that purpose, I >> wrote a service file (rsync) and a timer unit. They both work with no >> issues.

Re: [systemd-devel] Fwd: messing with .mount/.automount units

2016-01-30 Thread arnaud gaboury
On Sat, Jan 30, 2016, 5:28 PM Andrei Borzenkov wrote: > 30.01.2016 13:44, arnaud gaboury пишет: > >>> My first attempt was to add this line in my /etc/fstab: > >>> --- > >>> UUID=868560c1-ab69-423f-b76d-b8

[systemd-devel] Environment and additional command line options

2016-02-01 Thread arnaud gaboury
$ systemctl --version systemd 22 One way to pass additional options is to add one of these lines in the [Service] part of the unit file: Environment=ONE='one' EnvironmentFile=/path/to --- If I am right, there is another possible mechanism since recent versions by ad

Re: [systemd-devel] Environment and additional command line options

2016-02-01 Thread arnaud gaboury
On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas wrote: > On Mon, Feb 1, 2016 at 11:37 AM, arnaud gaboury > wrote: >> >> $ systemctl --version >> systemd 22 > > > v22 was released five years ago, are you sure? 222, sorry for the typo > >> >>

[systemd-devel] sshd.socket: connection closed by remote host

2016-03-19 Thread arnaud gaboury
OS: fedora 23 server systemd: 222 I gave a try at sshd.socket instead of the usual sshd.service. The latter was working well on my server but I can't ssh with sshd.socket. % systemctl cat sshd.socket -- # /usr/lib/systemd/system/sshd.socket [Unit] Descr

Re: [systemd-devel] sshd.socket: connection closed by remote host

2016-03-19 Thread arnaud gaboury
On Sat, Mar 19, 2016 at 3:00 PM, arnaud gaboury wrote: > OS: fedora 23 server > systemd: 222 > > I gave a try at sshd.socket instead of the usual sshd.service. The latter > was working well on my server but I can't ssh with sshd.socket. > > %

Re: [systemd-devel] sshd.socket: connection closed by remote host

2016-03-19 Thread arnaud gaboury
On Sat, Mar 19, 2016 at 3:00 PM, arnaud gaboury wrote: > OS: fedora 23 server > systemd: 222 > > I gave a try at sshd.socket instead of the usual sshd.service. The latter > was working well on my server but I can't ssh with sshd.socket. > > %

[systemd-devel] Disable dbus-daemon for a service

2015-04-12 Thread arnaud gaboury
When I start Firefox, it starts , part of the Gnome's Accessibility Project. I guess it is tarts with: < /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session> I would like to get rid of this dbus daemon. I found one solution was to export NOT_AT_BRIDGE=1, but it doesn't work for me. I can

[systemd-devel] install a fedora container

2015-04-22 Thread arnaud gaboury
I am little confused how to install Fedora on a container on my Archlinux box. Here is my setup : a whole ssd for Fedora server. Btrfs with 3 subvolumes for snapshots: /etc, /var, and /rootvol. No nested subvolumes. This ssd will then be mounted on /var/lib/container/MyContainer. Shall i install

Re: [systemd-devel] install a fedora container

2015-04-22 Thread arnaud gaboury
On Wed, Apr 22, 2015 at 7:26 PM, arnaud gaboury wrote: > I am little confused how to install Fedora on a container on my Archlinux box. > > Here is my setup : a whole ssd for Fedora server. Btrfs with 3 > subvolumes for snapshots: > /etc, /var, and /rootvol. No nested subvolume

Re: [systemd-devel] install a fedora container

2015-04-22 Thread arnaud gaboury
On Wed, Apr 22, 2015 at 7:39 PM, Lennart Poettering wrote: > On Wed, 22.04.15 19:26, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> I am little confused how to install Fedora on a container on my Archlinux >> box. >> >> Here is my setup : a whole ssd f

[systemd-devel] install Fedora systemd-nspawn container on btrfs

2015-04-23 Thread arnaud gaboury
Not sure what I did wrong, but I can't install/boot my nspawn container. Here is my setup: Archlinux box- updated 1- created 3 btrfs subvol on /dev/sdb1 (SSD). The goal is to manage snapshots easily. no nested subvol. -- # btrfs subvolume list . ID 266 gen

Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs

2015-04-23 Thread arnaud gaboury
On Thu, Apr 23, 2015 at 1:50 PM, Lennart Poettering wrote: > On Thu, 23.04.15 13:45, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> Not sure what I did wrong, but I can't install/boot my nspawn container. >> Here is my setup: >> >> Archlinux box- updated

Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs

2015-04-23 Thread arnaud gaboury
On Thu, Apr 23, 2015 at 2:00 PM, Lennart Poettering wrote: > On Thu, 23.04.15 14:57, Andrei Borzenkov (arvidj...@gmail.com) wrote: > >> On Thu, Apr 23, 2015 at 2:50 PM, Lennart Poettering >> wrote: >> > On Thu, 23.04.15 13:45, arnaud gaboury (arnaud.gabo...@gmail.com)

  1   2   >