[systemd-devel] moving to the meson build system

2017-04-05 Thread Zbigniew Jędrzejewski-Szmek
This is a proposal to move(*) to meson as the build system.
Initial, incomplete, implementation is at 
https://github.com/systemd/systemd/pull/5704.
Please have a look, see if it builds on your system, maybe send
a patch for some of the missing functionality.

Why? I'll just paste the text from the PR.

Reasons:

– simplicity: although the final number of lines is quite large (5k in
meson.builds vs 12k for Makefile.am + configure.ac + Makefile-man.am),
but it's all in a simple semi-declarative language. This was my first
contact with the language, and I got it working without too much
trouble. I hope meson will get even more high-level constructs in the
future, allowing us to simplify our rules.

— better error handling: if the command fails, the last command line
is printed along with stderr. Not intermixed with other output. Not
mangled. Ready to be copied and pasted and debugged. Syntax errors in
meson.build files are caught and reported (although the line numbers
are off).

— speed: full configuration and compilation from scratch:

$ time bash -c 'meson build && cd build && ninja-build'
...
bash -c 'meson build && cd build && ninja-build'  130.80s user 12.49s system 
357% cpu 40.080 total

and partials builds are near-instantaneous:

$ touch ../src/login/logind.c && time nj
[2/2] Linking target systemd-logind
ninja-build  0.04s user 0.03s system 98% cpu 0.076 total

Michael Biebl provides some more detailed comparisons with autotools:
https://github.com/systemd/systemd/pull/5704#issuecomment-291875938

So far the meson build is not complete, but those results suggest that a full
build will be 5-12 times faster on a modern machine.

I'll be working on adding the missing pieces and fixing any bugs that
people encounter and once the patches are merged, I propose to release
systemd 234 with dual build systems, and drop autotools support a
few weeks later.

Zbyszek

(*) "move" and not "add another build system" because — realistically
— once the new stuff is working, assuming developers like it more,
the other build system will quickly atrophy.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] systemd/automount for multiple users using Kerberos

2017-04-05 Thread Sebastian Treiber
Dear members of the Systemd mailing list,

for a long time I have been struggling with a problem which sounds
relatively easy:
I have a cifs file server and a Linux (CentOS 7) client. On the client I
want to mount a share from the file server using Kerberos.
Only the root user can perform the mount but typically it has no
Kerberos ticket. A user, on the other hand, has a Kerberos ticket but
must not mount anything.
That means the mount has to be done by the root user and the uid of a
user who has a valid Kerberos ticket has to be used as an option. For
example:
mount.cifs //path_to_file_server/share /mount_point -o sec=krb5,cruid=123456
So far so good. However, on the client there are multiple users and each
one wants to be able to mount the share to the same directory.
As to my knowledge, autofs is the only tool which provides a solution
for that (you can use something like "$USER" in the autofs configuration
file).

Systemd has a automount functionality as well and I was hoping to
replace autofs by systemd/automount since autofs is very unstable (as to
my experience).
Despite heavy googling I could not find a solution using
systemd/automount (or any other than autofs). My problem is that I
cannot specify the user-ID dynamically but only as a static string in
the ".mount" unit file (or fstab).
Does anyone of you know if this is possible with systemd?

Kind regard,

Sebastian

-- 

Mit freundlichen Grüßen
*Dr. Sebastian Treiber* | Systemanalytiker


GNS Systems - IT Dienstleistungen für Engineering


GNS Systems GmbH
Fronäckerstraße 36/1
71063 Sindelfingen
Tel.: +49 (0)7031/68838-66
Fax: +49 (0)7031/68838-11


Geschäftsführer: Christopher Woll
Sitz des Unternehmens: Braunschweig
Registergericht: Amtsgericht Braunschweig
Registernummer: HRB 4890
gns-systems.de 





signature.asc
Description: OpenPGP digital signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] mount-on-demand for backups; hooks for indicating success/failure

2017-04-05 Thread Jonathan Dowland
On Fri, Mar 31, 2017 at 12:01:11PM +0200, Lennart Poettering wrote:
> On recent systemd versions you can plug in a script in ExecStop= of
> your backup service, and check the $SERVICE_RESULT env var which tells
> you the success state of the service, which you can then use to set
> any LEDs you like.

This looks very useful, thanks - but the issue here is that I don't
think systemd provides a guarantee that if my backup service Requires
a mount unit, and that mount unit is marked StopWhenUnneeded=true, that
the this script will fire after the unmount has finished (and
succeeded).

I think Michal's solution of having a separate service for the LEDs
might work, perhaps with After=media-ipod.mount, but I need to
experiment some more.

-- 
Jonathan Dowland
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Failed to start apache :

2017-04-05 Thread Lennart Poettering
On Wed, 05.04.17 11:55, Gary Lock (g...@postiekiddo.com) wrote:

> Hi All
> 
>  
> 
> Please help!
> 
> Failed to start apache :
> 
> Job for httpd.service failed. See 'systemctl status httpd.service' and
> 'journalctl -xn' for details.


Sorry, but the "Support:" lines in the output are a bit misleading,
you won't find support for Apache at this mailing list. More recent
systemd version won't direct you here anymore like this.

Please contact the Apache community or your downstream distro for help
on this one.

Lennart

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


Re: [systemd-devel] Failed to start apache :

2017-04-05 Thread Reindl Harald



Am 05.04.2017 um 03:55 schrieb Gary Lock:

Please help!


wrong mailing list


*Failed to start apache :*

*Job for httpd.service failed. See 'systemctl status httpd.service' and
'journalctl -xn' for details.*


well, just read the outputs you posted and learn to use "apachectl -t" 
after config changes


Apr 05 11:53:16 postiekiddo.com httpd[21055]: httpd: Syntax error on 
line 350 of /etc/httpd/conf/httpd.conf: Syntax error on line 148 of 
/etc/httpd/conf.d/system-config-httpd.conf: 
/etc/httpd/conf.d/system-config-httpd.conf:150:  was not 
closed.\n/etc/httpd/conf.d/system-config-httpd.conf:148:  was 
not closed

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