[systemd-devel] [PATCH] Reword the polish translation a bit
s/siedzenie/stanowisko/: they both translate to seat in English, but 'stanowisko' is a place where you work, while 'siedzenie' is like a chair. s/podłączanie/podłączenie/: we are doing it now, now sometime in the future. --- po/pl.po | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/po/pl.po b/po/pl.po index 52a21c8..3816864 100644 --- a/po/pl.po +++ b/po/pl.po @@ -53,7 +53,7 @@ msgstr Ustawienie lokalizacji systemu #: ../src/org.freedesktop.login1.policy.in.h:1 msgid Allow attaching devices to seats -msgstr Zezwolenie na podłączanie urządzeń do siedzeń +msgstr Zezwolenie na podłączanie urządzeń do stanowisk #: ../src/org.freedesktop.login1.policy.in.h:2 msgid Allow non-logged-in users to run programs @@ -69,8 +69,8 @@ msgstr #: ../src/org.freedesktop.login1.policy.in.h:4 msgid Authentication is required to allow attaching a device to a seat msgstr -Wymagane jest uwierzytelnienie, aby zezwolić na podłączanie urządzeń do -siedzeń +Wymagane jest uwierzytelnienie, aby zezwolić na podłączenie urządzenia do +stanowiska #: ../src/org.freedesktop.login1.policy.in.h:5 msgid Authentication is required to allow powering off the system @@ -103,11 +103,11 @@ msgid seats msgstr Wymagane jest uwierzytelnienie, aby zezwolić na ponowne ustawianie sposobu -podłączenia urządzeń do siedzeń +podłączenia urządzeń do stanowisk #: ../src/org.freedesktop.login1.policy.in.h:10 msgid Flush device to seat attachments -msgstr Czyszczenie podłączeń urządzeń do siedzeń +msgstr Usunięcie podłączenia urządzeń do stanowisk #: ../src/org.freedesktop.login1.policy.in.h:11 msgid Power off the system -- 1.7.5.4 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] Reword the polish translation a bit
s/siedzenie/stanowisko/: they both translate to seat in English, but 'stanowisko' is a place where you work, while 'siedzenie' is like a chair. s/podłączanie/podłączenie/: we are doing it now, now sometime in the future. --- po/pl.po | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/po/pl.po b/po/pl.po index 52a21c8..3816864 100644 --- a/po/pl.po +++ b/po/pl.po @@ -53,7 +53,7 @@ msgstr Ustawienie lokalizacji systemu #: ../src/org.freedesktop.login1.policy.in.h:1 msgid Allow attaching devices to seats -msgstr Zezwolenie na podłączanie urządzeń do siedzeń +msgstr Zezwolenie na podłączanie urządzeń do stanowisk #: ../src/org.freedesktop.login1.policy.in.h:2 msgid Allow non-logged-in users to run programs @@ -69,8 +69,8 @@ msgstr #: ../src/org.freedesktop.login1.policy.in.h:4 msgid Authentication is required to allow attaching a device to a seat msgstr -Wymagane jest uwierzytelnienie, aby zezwolić na podłączanie urządzeń do -siedzeń +Wymagane jest uwierzytelnienie, aby zezwolić na podłączenie urządzenia do +stanowiska #: ../src/org.freedesktop.login1.policy.in.h:5 msgid Authentication is required to allow powering off the system @@ -103,11 +103,11 @@ msgid seats msgstr Wymagane jest uwierzytelnienie, aby zezwolić na ponowne ustawianie sposobu -podłączenia urządzeń do siedzeń +podłączenia urządzeń do stanowisk #: ../src/org.freedesktop.login1.policy.in.h:10 msgid Flush device to seat attachments -msgstr Czyszczenie podłączeń urządzeń do siedzeń +msgstr Usunięcie podłączenia urządzeń do stanowisk #: ../src/org.freedesktop.login1.policy.in.h:11 msgid Power off the system -- 1.7.5.4 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 00/14] systemadm updates
On 09/19/2011 05:57 PM, Frederic Crozat wrote: Le lundi 19 septembre 2011 à 17:49 +0200, Kay Sievers a écrit : 2011/9/19 Zbigniew Jędrzejewski-Szmekzbys...@in.waw.pl: On 09/19/2011 02:02 PM, microcai wrote: Can you send git pull request and just mail diff state ? Will do so in the future. The commits are here: git://in.waw.pl/git/systemd systemadm_changes I think it's time to move that tool out to its on tarball and we get rid of the gtk and vala dependencies in the basic systemd package. The broken vala autotools integration really stand in our way to do the Indeed.. There's a bug submitted upstream (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8753) and it looks like automake is on its way to be fixed. long overdue cleanup of Makefile.am. Is there maybe a plan to convert Makefile.am to use bin_PROGRAMS-$(HAVE_GTK) ala kernel Makefiles instead of if HAVE_GTK bin_PROGRAMS += ... endif Is this even allowed with automake? Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
Le lundi 19 septembre 2011 à 23:02 +0200, Lennart Poettering a écrit : On Sun, 18.09.11 18:20, Reindl Harald (h.rei...@thelounge.net) wrote: Sep 18 18:18:04 rh dbus-daemon: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out this happens on all my machines upgraded to F15 i think this is the reason why if i login to fast after boot in KDE the whole desktop sucks - but how to fix this problem? Seems for some reason CK fails to show up on the bus. what does systemctl status console-kit-daemon.service say after boot? Strangely, I got similar bug report from KDE users on openSUSE Factory (didn't had time to investigate myself) : https://bugzilla.novell.com/show_bug.cgi?id=715467 -- Frederic Crozat fcro...@suse.com SUSE ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
Am 20.09.2011 10:07, schrieb Frederic Crozat: Le lundi 19 septembre 2011 à 23:02 +0200, Lennart Poettering a écrit : On Sun, 18.09.11 18:20, Reindl Harald (h.rei...@thelounge.net) wrote: Sep 18 18:18:04 rh dbus-daemon: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out this happens on all my machines upgraded to F15 i think this is the reason why if i login to fast after boot in KDE the whole desktop sucks - but how to fix this problem? Seems for some reason CK fails to show up on the bus. what does systemctl status console-kit-daemon.service say after boot? Strangely, I got similar bug report from KDE users on openSUSE Factory (didn't had time to investigate myself) : https://bugzilla.novell.com/show_bug.cgi?id=715467 yes - exactly my error on F15 so my pulsed.service was only a blind guess from myself and is not the issue on systems with auto-login this is a major bug finally kde starts if you wait not long enough, but plasma has a lets say strange status and the best is kill the running login with sysrq, take a breath and login again signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Restart and RestartSec in packaged .service files
Am 01.09.2011 16:25, schrieb Lennart Poettering: if i say Restart=always i want a mail if this happens not a own unit-file write a unit file that sends a mail, something like this: send-mail-on-failure@.service: snip [Unit] Description=Send mail on failure of %I [Service] ExecStart=/path/to/my/script.sh %I /snip /path/to/my/script.sh: snip #!/bin/sh ( echo $1 crashed, do something, sir! echo here's the systemctl status output: systemctl status $1 ) | mail lennart -s OMG! PONIES! /snip And then add OnFailure=send-mail-on-failure@%P to your units where you want a mail to be sent this seems not to work because after systemctl --system daemon-reload the first error hits /var/log/messages and again the question why not simplify this with OnFailure=send-mail instead writing scripts and services to send a simple mail - this is the exact opposite of simplify what systemd should do like Lennart always says [root@rh:~]$ cat messages Sep 20 12:24:36 rh systemd[1]: Reloading. Sep 20 12:24:36 rh systemd[1]: Failed to add dependency on send-mail-on-failure@%P, ignoring: Invalid argument [root@rh:~]$ cat /lib/systemd/system/send-mail-on-failure@.service [Unit] Description=Send mail on failure of %I [Service] ExecStart=/scripts/send-mail-on-failure.sh %I [root@rh:~]$ cat /scripts/send-mail-on-failure.sh #!/bin/bash logger SYSTEMD FAILURE $1 [root@rh:~]$ cat /lib/systemd/system/httpd.service [Unit] Description=HTTP Server (prefork MPM) After=syslog.target local-fs.target network.target mysqld.service OnFailure=send-mail-on-failure@%P signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] Circumvent autofs_v5_packet_union size bug
On Tue, 20.09.11 11:36, Ian Kent (ra...@themaw.net) wrote: This is a bug in the kernel, and it should be fixed in the kernel (which would mean the kernel folks have to define a new version of this struct/ioctl which fixes this). If that's defined we can then add support for this into systemd. Could you file a bug about this please on the kernel bugzilla? (please cc me, or post the url here!) Yes, it is a mistake that I made but it is a bad idea to change something that will cause widespread failure of existing binaries and that's why the discrepancy persists and will continue to do so. I am not expecting this to be changed in the kernel. Instead I expect that the kernel API is extended with a correct version of the same data structure. If the kernel broke it the kernel should fix it. I chose to compensate for it in user space and to advise anyone that encountered the problem on how to handle it and I have had no reports of problems in autofs since I added the size calculation (which was a long time ago now). Well, it's a workaround in userspace. Fix the kernel. Add a second union or something which can be used by newer clients. I am sorry but I am pretty sure I want to keep the compat kludges for broken things in systemd at a minimum, adding such a work around looks like the wrong way to me. We generally try to fix problems where they are these days, not where we notice them. Sure, it is unfortunate but, as far as the autofs kernel module is concerned the decision about this was made a long time ago and, yes it isn't what we want but the breakage it would have caused then and the breakage it would cause now is too great. Adding a corrected version will not break anything. This is not about replacing the current borked interface, but simply by adding a fixed version that we can use from userspace without ugly compat glue. Fix the problems where they are, don't work around them where they aren't. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Fwd: mail-notify on service-restart
even a try with OnFailure=send-mail-on-failure.service does not work yes systemctl start send-mail-on-failure.service calls the script well, this is nothing anybody wants killall httpd [root@rh:~]$ tail -f messages Sep 20 14:10:48 rh systemd[1]: httpd.service holdoff time over, scheduling restart. so why is OnFailure not executed in case Restart=always? what does the %P mean in Lennart's sample send-mail-on-failure@%P.service the file is not called so and i hope the intention is not creating send-mail-on-failure@httpd.service send-mail-on-failure@mysqld.service . because systemd lacks the capability send-mail-on-failure.service %servicename to have a generic restart-option for all services - there is nothing usable to find for OnFailure nor how should anybody imagine what a service is in the case of an error - for me a service is an application which is started and runs after that Original-Nachricht Betreff: [systemd-devel] mail-notify on service-restart Datum: Tue, 20 Sep 2011 13:56:12 +0200 Von: Reindl Harald h.rei...@thelounge.net Organisation: the lounge interactive design An: Mailing-List systemd systemd-devel@lists.freedesktop.org OnFailure=send-mail-on-failure@%P.service OnFailure=send-mail-on-failure@%P this does not work, independent of using .service or not the whole internet has no information additional to the following thread http://lists.freedesktop.org/archives/systemd-devel/2011-June/002699.html After x restarts have happened, the OnFailure unit will start (if specified) but only after all unsuccessfull restarts (after x restarts reached). i maybe do not understand the context - but i do NOT need OnFailure if restart fails - i want simply a mail EVERYTIME systemd restarts a service even if Restart=always is defined and root types killall httpd _ [root@rh:~]$ systemctl status send-mail-on-failure@.service Failed to issue method call: Unit name send-mail-on-failure@.service is not valid i do simply not understand why in the world here is a service needed OnFailure=/usr/bin/anyapp %P is that what hardly is needed to get the service-name as $1 to a script and not a additional service in error-cases there are actions needed and not services, the targeted shell-script could start a service if needed for whatever reason Original-Nachricht Betreff: Re: [systemd-devel] Restart and RestartSec in packaged .service files Datum: Tue, 20 Sep 2011 12:30:23 +0200 Von: Reindl Harald h.rei...@thelounge.net CC: systemd-devel@lists.freedesktop.org Am 01.09.2011 16:25, schrieb Lennart Poettering: if i say Restart=always i want a mail if this happens not a own unit-file write a unit file that sends a mail, something like this: send-mail-on-failure@.service: snip [Unit] Description=Send mail on failure of %I [Service] ExecStart=/path/to/my/script.sh %I /snip /path/to/my/script.sh: snip #!/bin/sh ( echo $1 crashed, do something, sir! echo here's the systemctl status output: systemctl status $1 ) | mail lennart -s OMG! PONIES! /snip And then add OnFailure=send-mail-on-failure@%P to your units where you want a mail to be sent this seems not to work because after systemctl --system daemon-reload the first error hits /var/log/messages and again the question why not simplify this with OnFailure=send-mail instead writing scripts and services to send a simple mail - this is the exact opposite of simplify what systemd should do like Lennart always says [root@rh:~]$ cat messages Sep 20 12:24:36 rh systemd[1]: Reloading. Sep 20 12:24:36 rh systemd[1]: Failed to add dependency on send-mail-on-failure@%P, ignoring: Invalid argument [root@rh:~]$ cat /lib/systemd/system/send-mail-on-failure@.service [Unit] Description=Send mail on failure of %I [Service] ExecStart=/scripts/send-mail-on-failure.sh %I [root@rh:~]$ cat /scripts/send-mail-on-failure.sh #!/bin/bash logger SYSTEMD FAILURE $1 [root@rh:~]$ cat /lib/systemd/system/httpd.service [Unit] Description=HTTP Server (prefork MPM) After=syslog.target local-fs.target network.target mysqld.service OnFailure=send-mail-on-failure@%P -- Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
