Re: [systemd-devel] How to control socket activation when it run respawn infinitely.
the room means a possibility. sorry, I make you confused because of that word. Thanks 2014/1/7 David Timothy Strauss da...@davidstrauss.net On Mon, Jan 6, 2014 at 8:56 AM, Tony Seo tonys...@gmail.com wrote: But, I suspect that systemd has room not to get ACK from the server process executed by service unit. I concentrated on 3-way handshaking when I studied to analyze this problem. Isn't it right when we consider the systemd? I'm not sure what you mean by room here. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] gpt-auto-generator: skip nonexistent devices
Signed-off-by: Łukasz Stelmach l.stelm...@samsung.com
---
Hi,
The devices we work with have eMMC chips for storage. The chips
provide four hardware partitions. The first is /dev/mmcblk0, it
takes almost whole space and holds a GPT with several real partitions
(/dev/mmcblk0p?). Then there are three block devices (mmcblk0boot0,
mmcblk0boot1, rpmb) that are part of the same hardware as mmcblk0 that
are presented by the kernel as children of the latter. That relationship
makes gpt-auto-generator try to peek them but since they are not GPT
partitions blkid_do_safeprobe() returns -2 making verify_gpt_parition()
function return -ENODEV.
I am not sure both -1 and -2 returned by blkid_do_safeprobe() should
result in -ENODEV in verify_gpt_parition(), however, -ENODEV does not
mean IMHO we should stop iterating udev results in enumerate_partitions().
src/gpt-auto-generator/gpt-auto-generator.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/src/gpt-auto-generator/gpt-auto-generator.c
b/src/gpt-auto-generator/gpt-auto-generator.c
index 017c35d..df779ee 100644
--- a/src/gpt-auto-generator/gpt-auto-generator.c
+++ b/src/gpt-auto-generator/gpt-auto-generator.c
@@ -297,6 +297,8 @@ static int enumerate_partitions(struct udev *udev, dev_t
dev) {
r = verify_gpt_partition(node, type_id, nr, fstype);
if (r 0) {
+if (r == -ENODEV)
+goto skip;
log_error(Failed to verify GPT partition %s: %s,
node, strerror(-r));
return r;
--
1.7.9.5
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] sleep.c: fix typo
--- src/sleep/sleep.c.orig2014-01-07 17:13:59.103435340 +0100
+++ src/sleep/sleep.c2014-01-07 17:14:19.895173954 +0100
@@ -90,7 +90,7 @@ static int execute(char **modes, char **
const char* note = strappenda(SLEEP=, arg_verb);
/* This file is opened first, so that if we hit an error,
- * we can abort before modyfing any state. */
+ * we can abort before modifying any state. */
f = fopen(/sys/power/state, we);
if (!f) {
log_error(Failed to open /sys/power/state: %m);
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] journal: how to query journal to see ALL output of given unit?
On 06/01/14 21:52, Zbigniew Jędrzejewski-Szmek wrote: journalctl -o verbose for mysqld-check.sh Zbyszku, Here is output for 'journalctl SYSLOG_IDENTIFIER=mysqld-check.sh -o verbose' Sat 2014-01-04 23:32:07.364159 CET [s=bd641dc956b04278a26115fa814b910a;i=4365;b=1fad31caaf1e48348c9d4403b7d68ff6;m=2689289;t=4ef2c98c3163f;x=dc153004a _TRANSPORT=stdout PRIORITY=6 SYSLOG_FACILITY=3 _UID=0 _GID=0 _MACHINE_ID=beb0f0a1c2c303b17213bb8d4a87a3a6 _HOSTNAME=mythtv _CAP_EFFECTIVE=1f _BOOT_ID=1fad31caaf1e48348c9d4403b7d68ff6 SYSLOG_IDENTIFIER=mysqld-check.sh MESSAGE=-- mysqld: No need to check MythTV DB. Stop was clean... _PID=807 _COMM=mysqld-check.sh And here is exemplary output for mysqld: Mon 2014-01-06 16:24:36.037183 CET [s=6d5ef6e5ef9e413fbcb7fca114dd8465;i=43cb;b=5bbb0bb34be64b14886ed38600badb66;m=41e23ff;t=4ef4edb81a63f;x=b9e5fbfb9 _TRANSPORT=stdout PRIORITY=6 SYSLOG_FACILITY=3 _UID=0 _GID=0 _SYSTEMD_SLICE=system.slice _MACHINE_ID=beb0f0a1c2c303b17213bb8d4a87a3a6 _HOSTNAME=mythtv _CAP_EFFECTIVE=1f SYSLOG_IDENTIFIER=su _COMM=su _EXE=/bin/su _CMDLINE=/bin/su mysql -c /usr/bin/mysqld --defaults-file=/etc/mysql/my.cnf --datadir=/var/lib/mysql --socket=/var/run/mysqld/mysqld.sock _SYSTEMD_CGROUP=/system.slice/mysqld.service _SYSTEMD_UNIT=mysqld.service _BOOT_ID=5bbb0bb34be64b14886ed38600badb66 _PID=1478 MESSAGE=Version: '5.5.24' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution br ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] journal: how to query journal to see ALL output of given unit?
On Tue, Jan 7, 2014 at 11:19 PM, Warpme war...@o2.pl wrote: On 06/01/14 21:52, Zbigniew Jędrzejewski-Szmek wrote: journalctl -o verbose for mysqld-check.sh Zbyszku, Here is output for 'journalctl SYSLOG_IDENTIFIER=mysqld-check.sh -o verbose' Sat 2014-01-04 23:32:07.364159 CET [s=bd641dc956b04278a26115fa814b910a;i=4365;b=1fad31caaf1e48348c9d4403b7d68ff6;m=2689289;t=4ef2c98c3163f;x=dc153004a _TRANSPORT=stdout PRIORITY=6 SYSLOG_FACILITY=3 _UID=0 _GID=0 _MACHINE_ID=beb0f0a1c2c303b17213bb8d4a87a3a6 _HOSTNAME=mythtv _CAP_EFFECTIVE=1f _BOOT_ID=1fad31caaf1e48348c9d4403b7d68ff6 SYSLOG_IDENTIFIER=mysqld-check.sh MESSAGE=-- mysqld: No need to check MythTV DB. Stop was clean... _PID=807 _COMM=mysqld-check.sh And here is exemplary output for mysqld: Mon 2014-01-06 16:24:36.037183 CET [s=6d5ef6e5ef9e413fbcb7fca114dd8465;i=43cb;b=5bbb0bb34be64b14886ed38600badb66;m=41e23ff;t=4ef4edb81a63f;x=b9e5fbfb9 _TRANSPORT=stdout PRIORITY=6 SYSLOG_FACILITY=3 _UID=0 _GID=0 _SYSTEMD_SLICE=system.slice _MACHINE_ID=beb0f0a1c2c303b17213bb8d4a87a3a6 _HOSTNAME=mythtv _CAP_EFFECTIVE=1f SYSLOG_IDENTIFIER=su _COMM=su _EXE=/bin/su _CMDLINE=/bin/su mysql -c /usr/bin/mysqld --defaults-file=/etc/mysql/my.cnf --datadir=/var/lib/mysql --socket=/var/run/mysqld/mysqld.sock _SYSTEMD_CGROUP=/system.slice/mysqld.service _SYSTEMD_UNIT=mysqld.service _BOOT_ID=5bbb0bb34be64b14886ed38600badb66 _PID=1478 MESSAGE=Version: '5.5.24' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution It could be that the script exits before journald has a chance to read its cgroup information – it's a known limitation which AFAIK needs minor kernel changes (or maybe kdbus?). -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] journal: how to query journal to see ALL output of given unit?
On Tue, Jan 07, 2014 at 11:21:41PM +0200, Mantas Mikulėnas wrote: On Tue, Jan 7, 2014 at 11:19 PM, Warpme war...@o2.pl wrote: On 06/01/14 21:52, Zbigniew Jędrzejewski-Szmek wrote: journalctl -o verbose for mysqld-check.sh Zbyszku, Here is output for 'journalctl SYSLOG_IDENTIFIER=mysqld-check.sh -o verbose' Sat 2014-01-04 23:32:07.364159 CET [s=bd641dc956b04278a26115fa814b910a;i=4365;b=1fad31caaf1e48348c9d4403b7d68ff6;m=2689289;t=4ef2c98c3163f;x=dc153004a _TRANSPORT=stdout PRIORITY=6 SYSLOG_FACILITY=3 _UID=0 _GID=0 _MACHINE_ID=beb0f0a1c2c303b17213bb8d4a87a3a6 _HOSTNAME=mythtv _CAP_EFFECTIVE=1f _BOOT_ID=1fad31caaf1e48348c9d4403b7d68ff6 SYSLOG_IDENTIFIER=mysqld-check.sh MESSAGE=-- mysqld: No need to check MythTV DB. Stop was clean... _PID=807 _COMM=mysqld-check.sh And here is exemplary output for mysqld: Mon 2014-01-06 16:24:36.037183 CET [s=6d5ef6e5ef9e413fbcb7fca114dd8465;i=43cb;b=5bbb0bb34be64b14886ed38600badb66;m=41e23ff;t=4ef4edb81a63f;x=b9e5fbfb9 _TRANSPORT=stdout PRIORITY=6 SYSLOG_FACILITY=3 _UID=0 _GID=0 _SYSTEMD_SLICE=system.slice _MACHINE_ID=beb0f0a1c2c303b17213bb8d4a87a3a6 _HOSTNAME=mythtv _CAP_EFFECTIVE=1f SYSLOG_IDENTIFIER=su _COMM=su _EXE=/bin/su _CMDLINE=/bin/su mysql -c /usr/bin/mysqld --defaults-file=/etc/mysql/my.cnf --datadir=/var/lib/mysql --socket=/var/run/mysqld/mysqld.sock _SYSTEMD_CGROUP=/system.slice/mysqld.service _SYSTEMD_UNIT=mysqld.service _BOOT_ID=5bbb0bb34be64b14886ed38600badb66 _PID=1478 MESSAGE=Version: '5.5.24' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution It could be that the script exits before journald has a chance to read its cgroup information. That's what I'd guess too. Does is get fixed if you insert 'sleep 1' in mysql-check.sh before it exits? This seems likely because the output suggests that the script is short-lived. SYSLOG_IDENTIFIER=mysqld-check.sh MESSAGE=-- mysqld: No need to check MythTV DB. Stop was clean... – it's a known limitation which AFAIK needs minor kernel changes (or maybe kdbus?) The addition of additional information in the style of SO_CREDENTIALS for normal sockets was rejected by Eric Biederman with I don't like you as an explanation. So going through kdbus is the next option. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] sleep.c: fix typo
Applied. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
