[systemd-devel] [PATCH] journal: fix Inappropriate ioctl for device on ext4

2015-03-01 Thread Cristian Rodríguez
Logs constantly show

systemd-journald[395]: Failed to set file attributes: Inappropriate
ioctl for device

This is because ext4 does not support FS_NOCOW_FL.
---
 src/journal/journal-file.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/journal/journal-file.c b/src/journal/journal-file.c
index 9c9a548..ecabfd3 100644
--- a/src/journal/journal-file.c
+++ b/src/journal/journal-file.c
@@ -2610,7 +2610,8 @@ int journal_file_open(
  * checksumming). */
 r = chattr_fd(f-fd, true, FS_NOCOW_FL);
 if (r  0)
-log_warning_errno(errno, Failed to set file 
attributes: %m);
+if(r != -ENOTTY)
+log_warning_errno(errno, Failed to set file 
attributes: %m);
 
 /* Let's attach the creation time to the journal file,
  * so that the vacuuming code knows the age of this
-- 
2.3.0

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] anacron timer for backup job to depend on network-online.target

2015-03-01 Thread Thomas Koch
meta: is it ok to ask user questions on this list?

Hi,

I want my backup job to be triggered only, if my laptop is online. I've a 
service file and a timer file. Should I add a Wants= and After= dependency on 
network-online.target? To which file?

What is the effect, if the laptop is offline for a longer period? Will the 
backup 
jobs accumulate? Will a backup job trigger immediately when a connection is 
established and the job is overdue?

Regards, Thomas Koch

/etc/systemd/system/mybackup.service:
[Unit]
Description=run obnam backup

[Service]
Type=simple
ExecStart=obnam backup

/etc/systemd/system/mybackup.timer:
[Unit]
Description=schedules obnam backup

[Timer]
OnBootSec=5min
OnUnitActiveSec=8h
Unit=mybackup.service
Persistent=true

[Install]
WantedBy=multi-user.target



___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] How to make debug-shell more usable?

2015-03-01 Thread Michael Biebl
2015-03-01 12:17 GMT+01:00 Lennart Poettering lenn...@poettering.net:
 On Thu, 26.02.15 20:22, Michael Biebl (mbi...@gmail.com) wrote:

 2015-02-26 1:12 GMT+01:00 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
  On Thu, Feb 26, 2015 at 01:04:55AM +0100, Michael Biebl wrote:
  2015-02-26 0:55 GMT+01:00 Michael Biebl mbi...@gmail.com:
   To reproduce the problem, add e.g. a non-existing device to /etc/fstab
  
   The Waiting for device to show up ... messages are printed all over 
   tty9.
  We made rescue.service conflict with emergency.service for similar
  reasons some time ago. We could do something similar here. OTOH,
  killing debug-shell.service to start emergency.service does not seem
  useful. So maybe we could hardcode not starting emergency.service in case
  debug-shell.service is already running.

 Hm, I think it's fine to start emergency.service, but it should be
 started on a defined tty, not simply the current active one.

 No. /dev/console is the only right thing this early in the boot, since
 it might point to anything, including serial ports, all depending on
 kernel cmdline params. Hardcoding a VT is not an option.

I wasn't arguing for hard-coding the VT.

Using /dev/console to find out the initial tty is fine. I just would
remember which tty it points to and use that then for the complete
boot process.





-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] [PATCH] journal: fix Inappropriate ioctl for device on ext4

2015-03-01 Thread Ivan Shapovalov
On 2015-03-01 at 21:13 -0300, Cristian Rodríguez wrote:
 Logs constantly show
 
 systemd-journald[395]: Failed to set file attributes: Inappropriate
 ioctl for device
 
 This is because ext4 does not support FS_NOCOW_FL.
 ---
  src/journal/journal-file.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)
 
 diff --git a/src/journal/journal-file.c b/src/journal/journal-file.c
 index 9c9a548..ecabfd3 100644
 --- a/src/journal/journal-file.c
 +++ b/src/journal/journal-file.c
 @@ -2610,7 +2610,8 @@ int journal_file_open(
   * checksumming). */
  r = chattr_fd(f-fd, true, FS_NOCOW_FL);
  if (r  0)
 -log_warning_errno(errno, Failed to set file 
 attributes: %m);
 +if(r != -ENOTTY)

Maybe it's better to just say if (r  0  r != -ENOTTY) here?

Just nitpicking,
-- 
Ivan Shapovalov / intelfx /

 +log_warning_errno(errno, Failed to set file 
 attributes: %m);
  
  /* Let's attach the creation time to the journal file,
   * so that the vacuuming code knows the age of this



signature.asc
Description: This is a digitally signed message part
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Plans to fix or provide alternative for lz4?

2015-03-01 Thread Lennart Poettering
On Thu, 26.02.15 05:55, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:

 On Thu, Feb 26, 2015 at 04:41:48AM +, Laszlo Papp wrote:
  Hi,
  
  it seems that the lz4 headers are broken when getting coredumps
  generated. They cannot even be extracted by the lz4 tool itself, let
  alone using them via the coredump controller util.
  
  My system, which is Archlinux, is using lz4 127 and systemd 219.
  
  My current workaround was to disable compression altogether for
  coredumps in the corresponding config file, but it is suboptimal,
  especially on embedded systems.
 The headers are different because when lz4 support was added, lz4 did
 not provide a library to write the headers so I added custom headers.
 You should be able to use coredumpctl to unpack the file.
 
 Proper lz4 support has been written, but lz4 upstream has trouble
 with keeping .so compatibility: 
 https://code.google.com/p/lz4/issues/detail?id=147.
 So the question is whether to replace lz4 with something more stable
 or to ignore the issue and hope it doesn't happen again.

Maybe gzip might be a good compromise? Due to the importd logic we now
check for libz anyway in configure.ac, we might as well use it for the
journal. To my knowledge gzip is still a good compromise between
compression ratio on one hand and memory use/time on the other...

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] How to make debug-shell more usable?

2015-03-01 Thread Lennart Poettering
On Thu, 26.02.15 20:22, Michael Biebl (mbi...@gmail.com) wrote:

 2015-02-26 1:12 GMT+01:00 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
  On Thu, Feb 26, 2015 at 01:04:55AM +0100, Michael Biebl wrote:
  2015-02-26 0:55 GMT+01:00 Michael Biebl mbi...@gmail.com:
   To reproduce the problem, add e.g. a non-existing device to /etc/fstab
  
   The Waiting for device to show up ... messages are printed all over 
   tty9.
  We made rescue.service conflict with emergency.service for similar
  reasons some time ago. We could do something similar here. OTOH,
  killing debug-shell.service to start emergency.service does not seem
  useful. So maybe we could hardcode not starting emergency.service in case
  debug-shell.service is already running.
 
 Hm, I think it's fine to start emergency.service, but it should be
 started on a defined tty, not simply the current active one.

No. /dev/console is the only right thing this early in the boot, since
it might point to anything, including serial ports, all depending on
kernel cmdline params. Hardcoding a VT is not an option.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] [PATCH] core: downgrade unit type not supported message

2015-03-01 Thread Lennart Poettering
On Wed, 25.02.15 05:39, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:

 On Fri, Feb 20, 2015 at 10:53:28AM +0100, Umut Tezduyar Lindskog wrote:
  Otherwise every daemon reload prints out warnings like:
  
  systemd[1]: Unit type .busname is not supported on this system.
  systemd[1]: Unit type .swap is not supported on this system.
  ---
   src/core/manager.c | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
  
  diff --git a/src/core/manager.c b/src/core/manager.c
  index 4775219..bc9b7ec 100644
  --- a/src/core/manager.c
  +++ b/src/core/manager.c
  @@ -961,7 +961,7 @@ int manager_enumerate(Manager *m) {
   int q;
   
   if (unit_vtable[c]-supported  
  !unit_vtable[c]-supported(m)) {
  -log_info(Unit type .%s is not supported on this 
  system., unit_type_to_string(c));
  +log_debug(Unit type .%s is not supported on this 
  system., unit_type_to_string(c));
   continue;
 
 I think it is correct to print this warning at least once. If unsupported
 units are packaged or created by the admin, this is a sign of some mistake.
 Maybe the warning should be printed only once?

The message is currently printed for every single unit type that isn't
supported, regardless if there's actually a unit of that type
around. Hence I have commited Umut's patch now.

In cases where a unit of an unsupported type is strted we already will
show an error in the usual status output, hence I think we are good
here.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] Service watchdog feature in state ACTIVATING ?

2015-03-01 Thread Hoyer, Marko (ADITG/SW2)
Hi,

I ran into a use case where the activation phase of a service takes 
significantly longer than the desired watchdog period (Activating: 10-20secs, 
Watchdog: 1-5secs).

I found out that the watchdog features starts not before the service is in 
state START_POST. This means for my use case that the system is blind for 
10-20secs (whatever I set as startup timeout here).

Is there any way to activate the watchdog feature already in phase ACTIVATING?
I guess there should be a second watchdog configuration parameter to allow 
services to use different values for the states ACTIVATING and RUNING. 
Otherwise, people who are not interested in having a watchdog observation 
during startup will run into troubles ...

Any opinions on that?

Best regards

Marko Hoyer

Advanced Driver Information Technology GmbH
Software Group II (ADITG/SW2)
Robert-Bosch-Str. 200
31139 Hildesheim
Germany

Tel. +49 5121 49 6948
Fax +49 5121 49 6999
mho...@de.adit-jv.com

ADIT is a joint venture company of Robert Bosch GmbH/Robert Bosch Car 
Multimedia GmbH and DENSO Corporation
Sitz: Hildesheim, Registergericht: Amtsgericht Hildesheim HRB 3438
Geschaeftsfuehrung: Wilhelm Grabow, Katsuyoshi Maeda
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] [PATCH 8/9] shared: AFS is also a network filesystem

2015-03-01 Thread Lennart Poettering
On Fri, 20.02.15 15:35, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:

Thanks!

Applied!

 ---
  src/shared/util.c | 1 +
  1 file changed, 1 insertion(+)
 
 diff --git a/src/shared/util.c b/src/shared/util.c
 index dc65280..6729461 100644
 --- a/src/shared/util.c
 +++ b/src/shared/util.c
 @@ -1692,6 +1692,7 @@ bool chars_intersect(const char *a, const char *b) {
  
  bool fstype_is_network(const char *fstype) {
  static const char table[] =
 +afs\0
  cifs\0
  smbfs\0
  sshfs\0
 -- 
 2.3.0
 
 ___
 systemd-devel mailing list
 systemd-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] [PATCH] machined: use x-machine-unix prefix for the container bus on dbus1

2015-03-01 Thread Lennart Poettering
On Thu, 19.02.15 20:47, Benjamin Franzke (benjaminfran...@googlemail.com) wrote:

 This fixes machinectl login on systems configured with --disable-kdbus.
 
 The error was:
 machinectl login foo
 Failed to get machine PTY: Input/output error

Looks good! Applied!

Sorry for the delay!

Thanks!

 ---
  src/machine/machine-dbus.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/src/machine/machine-dbus.c b/src/machine/machine-dbus.c
 index 116e711..2388c85 100644
 --- a/src/machine/machine-dbus.c
 +++ b/src/machine/machine-dbus.c
 @@ -512,7 +512,7 @@ int bus_machine_method_open_login(sd_bus *bus, 
 sd_bus_message *message, void *us
  #ifdef ENABLE_KDBUS
  asprintf(container_bus-address, x-machine-kernel:pid= PID_FMT 
 ;x-machine-unix:pid= PID_FMT, m-leader, m-leader);
  #else
 -asprintf(container_bus-address, x-machine-kernel:pid= PID_FMT, 
 m-leader);
 +asprintf(container_bus-address, x-machine-unix:pid= PID_FMT, 
 m-leader);
  #endif
  if (!container_bus-address)
  return log_oom();
 -- 
 2.0.5
 
 ___
 systemd-devel mailing list
 systemd-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] How to make debug-shell more usable?

2015-03-01 Thread Lennart Poettering
On Thu, 26.02.15 00:55, Michael Biebl (mbi...@gmail.com) wrote:

 2015-02-26 0:44 GMT+01:00 Lennart Poettering lenn...@poettering.net:
  What precisely is supposedly written there? I have never seen anythign
  like that on FEdora...
 
  Maybe you should reconfigure your kernel to not spew its output always
  on the console?
 
 Well, if you want to debug boot issues, you typically remove the quiet
 flag from the kernel command line. That aside, once systemd hits a
 timeout or a service failure, it switches to verbose mode
 automatically.
 
 To reproduce the problem, add e.g. a non-existing device to /etc/fstab
 
 The Waiting for device to show up ... messages are printed all over tty9.
 
 Also, as mentioned, once the 90 sec timeout has been reached and tty9
 is the active tty, the emergency shell is started on tty9 with the
 aforementioned issues.

Well, not really. emergency.service uses /dev/console, whereever it
might point.

I am pretty sure it's the right behaviour to push status output to
/dev/console, and also run emergency.service on it. Also, I think
running the debug-shell on vt9 is the right thing.

Not entirely sure what the right approach is though to make them
not interfere that much. We could add systemd-analyze
set-show-status the same way we already expose systemd-analyze
set-log-level, to turn of status output, and then recommend usage of
that if people want to turn this off when in the debug shell (maybe by
printing a line recommending this before invoking the shell).

One thing we could also try to do is redirecting /dev/console to VT1, as
soon as emergency.service is spawned on VT9. This is doable with the
TIOCCONS ioctl. We could run a small binary as part of ExecStartPre=
in debug-shell.service that invokes it for /dev/tty1...

WOuld that make sense?

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] [PATCH] po: update Russian translation

2015-03-01 Thread Sergey Ptashnick
Add some forgotten strings for systemd, logind and machined.
---
 po/ru.po |  106 ++---
 1 files changed, 73 insertions(+), 33 deletions(-)

diff --git a/po/ru.po b/po/ru.po
index 1ffeec6..e04934c 100644
--- a/po/ru.po
+++ b/po/ru.po
@@ -7,13 +7,53 @@ msgstr 
 Project-Id-Version: systemd\n
 Report-Msgid-Bugs-To: 0comff...@inbox.ru\n
 POT-Creation-Date: 2013-03-24 19:22+0300\n
-PO-Revision-Date: 2015-02-19 03:27+0300\n
+PO-Revision-Date: 2015-03-02 00:25+0300\n
 Last-Translator: Sergey Ptashnick 0comff...@inbox.ru\n
 Language: ru\n
 MIME-Version: 1.0\n
 Content-Type: text/plain; charset=UTF-8\n
 Content-Transfer-Encoding: 8bit\n
 
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:1
+msgid Send passphrase back to system
+msgstr Отправить пароль системе
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:2
+msgid Authentication is required to send the entered passphrase back to the 
system.
+msgstr Чтобы отправить пароль системе, необходимо пройти аутентификацию.
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:3
+msgid Manage system services or units
+msgstr Управление системными службами и юнитами
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:4
+msgid Authentication is required to manage system services or units.
+msgstr Для управления системными службами и юнитами, необходимо пройти 
аутентификацию.
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:5
+msgid Manage system service or unit files
+msgstr Управление файлами конфигурации системных служб и юнитов
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:6
+msgid Authentication is required to manage system service or unit files.
+msgstr Для управления файлами конфигурации системных служб и юнитов, 
необходимо пройти аутентификацию.
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:7
+msgid Set or unset system and service manager environment variables
+msgstr Настроить переменные окружения для системного менеджера
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:8
+msgid Authentication is required to set or unset system and service manager 
environment variables.
+msgstr Чтобы настроить переменные окружения для системного менеджера, 
необходимо пройти аутентификацию.
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:9
+msgid Reload the systemd state
+msgstr Перечитать конфигурацию systemd
+
+#: ../src/core/org.freedesktop.systemd1.policy.in.in.h:10
+msgid Authentication is required to reload the systemd state.
+msgstr Чтобы заставить systemd перечитать конфигурацию, необходимо пройти 
аутентификацию.
+
 #: ../src/hostname/org.freedesktop.hostname1.policy.in.h:1
 msgid Set host name
 msgstr Настроить имя компьютера
@@ -254,6 +294,22 @@ msgstr Перевести систему в спящий режим, несмо
 msgid Authentication is required for hibernating the system while an 
application asked to inhibit it.
 msgstr Чтобы перевести систему в спящий режим, несмотря на то, что приложение 
запросило блокировку, необходимо пройти аутентификацию.
 
+#: ../src/login/org.freedesktop.login1.policy.in.h:49
+msgid Manage active sessions, users and seats
+msgstr Управление текущими сеансами, пользователями и рабочими местами
+
+#: ../src/login/org.freedesktop.login1.policy.in.h:50
+msgid Authentication is required for managing active sessions, users and 
seats.
+msgstr Для управления текущими сеансами, пользователями и рабочими местами, 
необходимо пройти аутентификацию.
+
+#: ../src/login/org.freedesktop.login1.policy.in.h:51
+msgid Lock or unlock active sessions
+msgstr Заблокировать или разблокировать текущие сеансы
+
+#: ../src/login/org.freedesktop.login1.policy.in.h:52
+msgid Authentication is required to lock or unlock active sessions.
+msgstr Чтобы заблокировать или разблокировать текущие сеансы, необходимо 
пройти аутентификацию.
+
 #: ../src/machine/org.freedesktop.machine1.policy.in.h:1
 msgid Log into a local container
 msgstr Зайти в локальный контейнер
@@ -262,6 +318,22 @@ msgstr Зайти в локальный контейнер
 msgid Authentication is required to log into a local container.
 msgstr Чтобы зайти в локальный контейнер, необходимо пройти аутентификацию.
 
+#: ../src/machine/org.freedesktop.machine1.policy.in.h:3
+msgid Manage local virtual machines and containers
+msgstr Управление виртуальными машинами и контейнерами
+
+#: ../src/machine/org.freedesktop.machine1.policy.in.h:4
+msgid Authentication is required to manage local virtual machines and 
containers.
+msgstr Для управления виртуальными машинами и контейнерами, необходимо пройти 
аутентификацию.
+
+#: ../src/machine/org.freedesktop.machine1.policy.in.h:5
+msgid Manage local virtual machine and container images
+msgstr Управление образами виртуальных машин и контейнеров
+
+#: ../src/machine/org.freedesktop.machine1.policy.in.h:6
+msgid Authentication is required to manage local virtual machine and 
container images.
+msgstr Для управления образами виртуальных машин и контейнеров, необходимо 
пройти 

[systemd-devel] autoconf cache collision in check for gnuefi

2015-03-01 Thread Mirco Tischler
Hi
I get the following error when doing ./configure --enable-gnuefi:
checking for /usr/lib/gnuefi/elf_x86_64_efi.lds... no
checking for /usr/lib/elf_x86_64_efi.lds... (cached) no
configure: error: *** gnuefi support requested but files not found

even though the second file exists on my system.

In the lines: configure.ac:1186
[AS_FOR([DIR], [EFI_LDS_DIR], [${efiroot}/gnuefi
${efiroot}],
[AC_CHECK_FILE([DIR/elf_${EFI_ARCH}_efi.lds],

AC_CHECK_FILE doesn't expand the DIR variable and creates the cached
variable ac_cv_file_DIR_elf_x86_64_efi_lds, which is then falsely
reused for all DIRs. I'm not sure if this is an autotools or systemd
issue.

systemd version: current git
autoconf version: 2.69
on Arch Linux

Thanks
Mirco
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] anacron timer for backup job to depend on network-online.target

2015-03-01 Thread Andrei Borzenkov
В Sun, 01 Mar 2015 22:13:11 +0100
Thomas Koch tho...@koch.ro пишет:

 meta: is it ok to ask user questions on this list?
 
 Hi,
 
 I want my backup job to be triggered only, if my laptop is online. I've a 
 service file and a timer file. Should I add a Wants= and After= dependency on 
 network-online.target? To which file?
 

No, network-online.target is relevant only during boot and even then it
is best effort only. The simplest solution would be to add check of
online state to your backup script and gracefully fail if system is
not online.

 What is the effect, if the laptop is offline for a longer period? Will the 
 backup 
 jobs accumulate? Will a backup job trigger immediately when a connection is 
 established and the job is overdue?
 

systemd does not know anything about network online state. What
software are you using to configure network? 

 Regards, Thomas Koch
 
 /etc/systemd/system/mybackup.service:
 [Unit]
 Description=run obnam backup
 
 [Service]
 Type=simple
 ExecStart=obnam backup
 
 /etc/systemd/system/mybackup.timer:
 [Unit]
 Description=schedules obnam backup
 
 [Timer]
 OnBootSec=5min
 OnUnitActiveSec=8h
 Unit=mybackup.service
 Persistent=true
 
 [Install]
 WantedBy=multi-user.target
 
 
 
 ___
 systemd-devel mailing list
 systemd-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/systemd-devel

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Errors using machinectl pull-tar and machinectl pull-dkr

2015-03-01 Thread Peter Paule
Hi,

is it ok for you to have a configuration file for machined? It would be
wonderful if one could add the dkr index url to that file because for me
it's always the same.

And maybe you could also support multiple values for the url to support
private and public registries at the same time:

1. Lookup the name of the dkr image at the first registry
2. Return if found
3. Go on with info message if not found
4. Lookup the name of the dkr image at the second registry
5. Return if found
6. Fail with error message if not found

Does this makes sense to you?

/pp
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] tmpfiles.d specifier support on argument when operating on files

2015-03-01 Thread Cristian Rodríguez
On Wed, Feb 18, 2015 at 6:17 PM, Cristian Rodríguez
crrodrig...@opensuse.org wrote:

 Is the attached version cool for you ?

Ping ? Any comments about this one ? note that implementing the
specifier expansion in all cases for argument does not make sense to
me unless I am missing something .
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel