Re: [systemd-devel] [ANNOUNCE] Git development moved to github

2015-07-31 Thread Jonathan Liu 

Hi,

On 2/06/2015 8:27 PM, Dimitri John Ledkov wrote:

On 1 June 2015 at 19:12, David Herrmann  wrote:

Hi

As of today we've disabled git-push to fd.o. The official development
git repository is now at github [1]. The old repository will still be
back-synced, but we had to disable push-access to avoid getting
out-of-sync with github.

[1] https://github.com/systemd-devs/systemd

And where will be the stable repository / branches?

I am also interested to know if the systemd-stable repository will 
continue to be maintained on either freedesktop or after being moved to 
GitHub.
OpenEmbedded uses systemd 219 from systemd-stable repository which 
hasn't seen any activity in the last few months.


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

Re: [systemd-devel] How to debug this strange issue about "systemd"?

2015-07-31 Thread sean 
On Fri, 2015-07-17 at 10:43 +0100, Colin Guthrie wrote:
> >> See "man dracut" and the "Debugging dracut" section. Also see "man
> >> dracut.cmdline" and the "rd.break" bits.
> >>
> > 
> > Was it not man dracut.kernel?
> 
> dracut.kernel == dracut.cmdline here (the latter seems to be the
> preferred name as it's the title in the manpage) and indeed:
> 
> lrwxrwxrwx 1 root root 19 Jun  5 17:11
> /usr/share/man/man7/dracut.kernel.7.xz -> dracut.cmdline.7.xz
Thanks very much for all help.
The root cause is that 64 bit libraries were not included in the real
ext4 file system.

But now a new issue appears, Boot failed at "[ ok ] Reached target
System Initialization".
How to debug it?


The attachment is the full log message. 

[FAILED] Failed to start Postfix Mail Transport Agent.
See "systemctl status postfix.service" for details.
 Starting Command Scheduler...
[  OK  ] Started Command Scheduler.
 Starting smfpd.service...
[  OK  ] Started smfpd.service.
 Starting /etc/init.d/boot.local Compatibility...
[  OK  ] Started /etc/init.d/boot.local Compatibility.
 Starting Wait for Plymouth Boot Screen to Quit...
 Starting Terminate Plymouth Boot Screen...


-- 
Sean. XinRong Fu
Dedicate System Engineer
SUSE
x...@suse.com
(P)+86 18566229618


line

SUSE


[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.1.0-rc2-7-desktop+ (s...@linux-dunz.site) (gcc 
version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #7 SMP 
PREEMPT Sat Jul 4 23:39:33 CST 2015
[0.00] Command line: root=UUID=20059b62-2542-4a85-80cf-41da6e0c1137 
rootflags=rw rootfstype=ext4 console=ttyS0,115200n8 console=tty0 
systemd.unit=default.target systemd.confirm_spawn=auto systemd.show_status=ture 
systemd.log_level=debug
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x3ffd] usable
[0.00] BIOS-e820: [mem 0x3ffe-0x3fff] reserved
[0.00] BIOS-e820: [mem 0xfeffc000-0xfeff] reserved
[0.00] BIOS-e820: [mem 0xfffc-0x] reserved
[0.00] earlycon: no match for ttyS0,115200n8
[0.00] earlycon: no match for tty0
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.8 present.
[0.00] Hypervisor detected: KVM
[0.00] AGP: No AGP bridge found
[0.00] e820: last_pfn = 0x3ffe0 max_arch_pfn = 0x4
[0.00] PAT not supported by CPU.
[0.00] found SMP MP-table at [mem 0x000f0ec0-0x000f0ecf] mapped at 
[880f0ec0]
[0.00] Scanning 1 areas for low memory corruption
[0.00] init_memory_mapping: [mem 0x-0x000f]
[0.00] init_memory_mapping: [mem 0x3d80-0x3d9f]
[0.00] init_memory_mapping: [mem 0x2000-0x3d7f]
[0.00] init_memory_mapping: [mem 0x0010-0x1fff]
[0.00] init_memory_mapping: [mem 0x3da0-0x3ffd]
[0.00] RAMDISK: [mem 0x3da25000-0x3ffe]
[0.00] Allocated new RAMDISK: [mem 0x3b45a000-0x3da2417f]
[0.00] Move RAMDISK from [mem 0x3da25000-0x3ffef17f] to [mem 
0x3b45a000-0x3da2417f]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F0CD0 14 (v00 BOCHS )
[0.00] ACPI: ?ɳ� 0x3FFE1854 8A476AE6 (v251 �??� ? ??�&�^�? 
318ACCAB e8�? 6D99E0DB)
[0.00] [ cut here ]
[0.00] WARNING: CPU: 0 PID: 0 at mm/early_ioremap.c:136 
__early_ioremap.constprop.0+0x11f/0x1f2()
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.0-rc2-7-desktop+ #7
[0.00] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.7.5-0-ge51488c-20141015_183547-build31 04/01/2014
[0.00]  81a3ad65 81c03ca8 8169d79b 
0198
[0.00]   81c03ce8 81066d8a 
30783020cfb3c93f
[0.00]  0008a478 8163  
ca45833a
[0.00] Call Trace:
[0.00]  [] dump_stack+0x4c/0x6e
[0.00]  [] warn_slowpath_common+0x8a/0xc0
[0.00]  [] warn_slowpath_null+0x1a/0x20
[0.00]  [] __early_ioremap.constprop.0+0x11f/0x1f2
[0.00]  [] early_ioremap+0x13/0x15
[0.00]  [] __acpi_map_table+0x13/0x18
[0.00]  [] acpi_os_map_iomem+0x27/0x151
[0.00]  [] acpi_os_map_memory+0xe/0x10
[0.00]  [] acpi_tb_parse_root_table+0x16d/0x29b
[0.00]  [] acpi_initialize_tables+0xcc/0xf8
[0.00]  [] acpi_table_init+0x50/0xc

[systemd-devel] [ANNOUNCE] systemd v224

2015-07-31 Thread Kay Sievers 
Here's the next version of systemd, v224:
https://github.com/systemd/systemd/archive/v224.tar.gz

This is mostly a bugfix release, containing many important fixes for kdbus.

IMPORTANT: Please don't forget to sign up quickly to systemd.conf
2015, if you plan to attend. There's only a limited number of tickets
available. For details see:
https://systemd.events/

CHANGES WITH 224:

* The systemd-efi-boot-generator functionality was merged into
  systemd-gpt-auto-generator.

* systemd-networkd now supports Group Policy for vxlan devices. It can
  be enabled via the new boolean configuration option called
  'GroupPolicyExtension='.

Contributions from: Andreas Kempf, Christian Hesse, Daniel Mack, David
Herrmann, Herman Fries, Johannes Nixdorf, Kay Sievers, Lennart
Poettering, Peter Hutterer, Susant Sahani, Tom Gundersen

-- Berlin, 2015-07-31
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Complicated SysVInit Migration

2015-07-31 Thread Lesley Kimmel 
The problem is that I'd like to get all of the same features out of systemd as 
I did with SysV. I don't see how, in this instance, I'd be able to get an 
accurate status of my service. I also want to be able to stop the service with 
the same unit file. I guess to do this I could just use the 
'RemainAfterExit=yes' but then I don't think I have the ability to get an 
accurate status from systemd.

> Date: Fri, 31 Jul 2015 06:25:43 +0300
> From: arvidj...@gmail.com
> To: ljkimme...@hotmail.com
> CC: graw...@gmail.com; systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] Complicated SysVInit Migration
> 
> В Thu, 30 Jul 2015 16:53:43 -0500
> Lesley Kimmel  пишет:
> 
> > I can't really change anything about the way that the Node Manager does 
> > it's job. That all takes place outside of systemd. If I used the PIDFile 
> > option in the original systemd service (executing the WLST process), let's 
> > call this weblogic.service, and the PIDFile pointed to the PID file created 
> > by the final Java process, would that work or does the process that I'm 
> > ultimately starting have to descend directly from whatever it is that the 
> > unit file executes?
> 
> Process has to be part of cgroup of original systemd service; and for
> all practical purposes this means it has to be direct descendant of one
> of ExecStart* commands. There is no systemd API to move processes
> between cgroups.
> 
> What exactly is wrong in how it behaves currently? It is no worse
> than it was before, with sysvinit, right? Do you observe any problems?  
> 
> > 
> > Date: Thu, 30 Jul 2015 23:47:03 +0300
> > Subject: Re: [systemd-devel] Complicated SysVInit Migration
> > From: graw...@gmail.com
> > To: ljkimme...@hotmail.com
> > CC: systemd-devel@lists.freedesktop.org
> > 
> > On Thu, Jul 30, 2015 at 9:40 PM, Lesley Kimmel  
> > wrote:
> > 
> > 
> > 
> > All;
> > 
> > I'm struggling with figuring out how to migrate some SysVInit scripts to 
> > systemd. Specifically, this service launches WebLogic Managed Server (Java) 
> > instances Let me describe the process flow of my current service to you:
> > 
> > -The init service/script launches a Java process called WLST which executes 
> > a simple script
> > -This WLST process connects to an already running Java process called the 
> > Node Manager and issues a start command for the application server it 
> > wishes to start
> > -The Node Manager process executes a shell script as a subprocess. This 
> > shell script sets up a bunch of environment variables, etc.
> > -Ultimately the shell script launches a Java process which is a child of 
> > the shell script.
> > -When this Java process reports itself as running, the initial WLST Java 
> > process exits.
> > -In the end the actual service/process that we started, and want to manage, 
> > is actually the GRANDCHILD of a completely separate process from the 
> > initial Java process that systemd launched. How, would systemd track that 
> > process?
> > 
> > systemd would see it as an extra process belonging to NodeManager.service, 
> > nothing more.
> > If you want systemd to track it as an independent service, go back to step 
> > #3 (where the Node Manager executes a shell script), and make that shell 
> > script merely run "systemctl start ..." instead of creating the new 
> > instance directly. (Make a template foo@.service unit for the WLMS 
> > instances.)
> 
  ___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] starting processes for other users

2015-07-31 Thread Michał Zegan 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The thing is, if the user does it, then after he leaves, the process
is running under the user's session.
If I log in to my own account, su to the other user and start the
process and then logout, this process, even though running as the
other user, is in my own session.
Actually it is sometimes confusing to see utmp entries saying
different things than loginctl ;)

W dniu 2015-07-31 o 05:35, Andrei Borzenkov pisze:
> В Fri, 31 Jul 2015 00:19:06 +0200 Michał Zegan
>  пишет:
> 
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> 
>> Hello. What is the recommended easy way to start processes that
>> stay longer like screen in case I want to do it by first
>> executing su to change to the target user?
> 
> This is controlled by KillUserProcesses, see man logind.conf. But 
> default is to leave them running, so it should just work.
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBAgAGBQJVu13nAAoJEHb1CzgxXKwYH5IP/2ylY+6YSmmh/O0bXR3t49DO
EVjD01PtEzXjfmA9HFfZ3ybyoQlABvdO3PP3k6SnoR+kdgQTHOP86LdbWhf5sNZQ
KbLnG2pnuli4XB4Dg+ueMa3B2nomOX+CNu3arBpMDVTvcOUAAF4bJBF06urx+0KX
sTT6T37prJUrhjhAJ5K4YHo8+zoqU+u1zM51e0gNACn8DCb9A4l71GnpN6Zml+fY
fJCmXKgkzfavWECm4qCvEIR0X7K0lkD/MihF/ritFNd1Qh9qHPUcubLkr/DFSKcU
Artu7JWdGMID3y41brEJ+b/iXFCt63/gJLE3WSFjT4c0OfAr16vPRW6iGioflNn4
jd9YfAzugSXkZNdiaAJ8RArH3ue1CULctIq7SE/QR2MZ2IPDMmzdVGvkl/0hQ31r
ZG4MsSfsyPWrrC9EfQCX/taSgEouUapMic5cFSLfEFljxGN2ldHZyrWmBobFvmHt
dOpqtU3iH06qOb4C5Q7N32nbGJnNeN6UstqYryQYOiobL4ydLBGnpm/GPQP/hjha
5xirMkPTy8MpaR+3fPMsMOXLK5NYMMDjHv3wuv/jLbgaVSs/ZM6VArYikR1DHgut
/DwSLbuwK/f/m9TtonSBk1nHPBkShx5GQLJb1J8VRuJOZFi2p7U4bj0EwXeALNCW
YH06jKDeMl0nezItvCfP
=PWnk
-END PGP SIGNATURE-
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] logind: add standard gpio power button support

2015-07-31 Thread Lennart Poettering 
On Fri, 31.07.15 17:51, Kefeng Wang (wangkefeng.w...@huawei.com) wrote:

>   looking at parent device '/devices/platform/gpio_keys':
> KERNELS=="gpio_keys"
> SUBSYSTEMS=="platform"
> DRIVERS=="gpio-keys"
> ATTRS{keys}=="116"
> ATTRS{switches}==""
> ATTRS{driver_override}=="(null)"
> ATTRS{disabled_keys}==""
> ATTRS{disabled_switches}==""
> 
>   looking at parent device '/devices/platform':
> KERNELS=="platform"
> SUBSYSTEMS==""
> DRIVERS==""
> 
> Signed-off-by: Kefeng Wang 

We do not do "S-o-b" on systemd. Please do not include this line in
your pacthes.

> ---
>  src/login/70-power-switch.rules |1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/src/login/70-power-switch.rules b/src/login/70-power-switch.rules
> index 695d246..9299738 100644
> --- a/src/login/70-power-switch.rules
> +++ b/src/login/70-power-switch.rules
> @@ -11,5 +11,6 @@ SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="acpi", 
> TAG+="power-switch"
>  SUBSYSTEM=="input", KERNEL=="event*", KERNELS=="thinkpad_acpi", 
> TAG+="power-switch"
>  SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="twl4030_pwrbutton", 
> TAG+="power-switch"
>  SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="tps65217_pwr_but", 
> TAG+="power-switch"
> +SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="platform", 
> ATTRS{keys}=="116", TAG+="power-switch"

I am pretty sure this should include a DRIVERS=="gpio-keys" check,
since only then the "keys" attribute really makes sense.

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] logind: add standard gpio power button support

2015-07-31 Thread systemd github import bot 
Patchset imported to github.
To create a pull request, one of the main developers has to initiate one via:


--
Generated by https://github.com/haraldh/mail2git
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] [PATCH] logind: add standard gpio power button support

2015-07-31 Thread Kefeng Wang 
Many boards like hisilicon D02 board use standard gpio key to power down system.
A description of gpio-key in dts shown below,

gpio_keys {
compatible = "gpio-keys";
#address-cells = <1>;
#size-cells = <0>;

pwrbutton {
label = "Power Button";
gpios = <&porta 8 1>;
linux,code = <116>;  // KEY_POWER, used by SC System Power Down
};
};

-bash-4.3# udevadm info -a /dev/input/event3

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/gpio_keys/input/input3/event3':
KERNEL=="event3"
SUBSYSTEM=="input"
DRIVER==""

  looking at parent device '/devices/platform/gpio_keys/input/input3':
KERNELS=="input3"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="gpio_keys"
ATTRS{phys}=="gpio-keys/input0"
ATTRS{uniq}==""
ATTRS{properties}=="0"

  looking at parent device '/devices/platform/gpio_keys':
KERNELS=="gpio_keys"
SUBSYSTEMS=="platform"
DRIVERS=="gpio-keys"
ATTRS{keys}=="116"
ATTRS{switches}==""
ATTRS{driver_override}=="(null)"
ATTRS{disabled_keys}==""
ATTRS{disabled_switches}==""

  looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""

Signed-off-by: Kefeng Wang 
---
 src/login/70-power-switch.rules |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/src/login/70-power-switch.rules b/src/login/70-power-switch.rules
index 695d246..9299738 100644
--- a/src/login/70-power-switch.rules
+++ b/src/login/70-power-switch.rules
@@ -11,5 +11,6 @@ SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="acpi", 
TAG+="power-switch"
 SUBSYSTEM=="input", KERNEL=="event*", KERNELS=="thinkpad_acpi", 
TAG+="power-switch"
 SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="twl4030_pwrbutton", 
TAG+="power-switch"
 SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="tps65217_pwr_but", 
TAG+="power-switch"
+SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="platform", 
ATTRS{keys}=="116", TAG+="power-switch"
 
 LABEL="power_switch_end"
-- 
1.7.1


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