Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 19:52 schrieb Manuel Amador (Rudd-O): On 12/10/2015 03:20 PM, Reindl Harald wrote: Apache: Include "conf/local/testserver.conf" and now you can use the same systemd-unit on a dozens of machines and include specific config snippets WITOUT touch the syste

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:02 schrieb Manuel Amador (Rudd-O): On 12/16/2015 09:47 AM, Reindl Harald wrote: "normal people" - what's wrong with you? Us "normal people" use configuration management systems to properly do what you do with ugly hacks. It's 2015. cfengin

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:04 schrieb Manuel Amador (Rudd-O): On 12/16/2015 09:47 AM, Reindl Harald wrote: because i know how to configure servers and don't need handholding tools since i develop my own admin backends for many years and services helping on repeatly needed taks but don't c

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:07 schrieb Manuel Amador (Rudd-O): On 12/26/2015 06:58 PM, Reindl Harald wrote: uhm - "EnvironmentFile" don't change often and so reload is possible all the time I never said you couldn't reload. I said that reload would not enact your environmen

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:19 schrieb Manuel Amador (Rudd-O): On 12/26/2015 07:06 PM, Reindl Harald wrote: people needing handholding - bah See, your problem is more a limited mindset / perspective problem. From your attitude, you believe it's demeaning to use the proper tool for the job, t

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:39 schrieb Manuel Amador (Rudd-O): On 12/26/2015 07:28 PM, Reindl Harald wrote: impressive what a arrgoant asshole you are while talking about "Arrogant" is the guy who refuses to accept new ways of doing things, because he thinks that the way he does things

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:39 schrieb Manuel Amador (Rudd-O): On 12/26/2015 07:28 PM, Reindl Harald wrote: my infrastructure is most likely better managed than anyone leses So says the person with a limited perspective and a refusal to learn modern tools and processes the person with a limited

[systemd-devel] "StandardOutput=console" don't work as expected

why is there only logging instead "TEST" written to the terminal starting a oneshot-service or in case it's a entry in /etc/crontab triggering a cronmail becaus the output? that's not helpful when try to migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions

Re: [systemd-devel] "StandardOutput=console" don't work as expected

fine, on a real TTY (CTRL+ALT+F2) the echo appears (cluttered with echo and the PID instead just the output) but that don't help much in a SSH-Session.. Am 30.12.2015 um 01:26 schrieb Reindl Harald: why is there only logging instead "TEST" written to the terminal sta

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 10:37 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 2:40 AM, Reindl Harald mailto:h.rei...@thelounge.net>> wrote: fine, on a real TTY (CTRL+ALT+F2) the echo appears (cluttered with echo and the PID instead just the output) but that don't help much

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald mailto:h.rei...@thelounge.net>> wrote: Do you really have cronjobs which need to output stuff to ssh ptys? i have hundrets cronjobs which are running silent and if th

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:24 schrieb Martin Pitt: Reindl Harald [2015-12-30 11:10 +0100]: i just want systemd *not to touch* the stdout behavior when asked to do so - it don't need to know anything about ssh ptys, just don't touch stdout i am asking for StandardOutput=console get pi

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:25 schrieb Michael Chapman: On Wed, 30 Dec 2015, Reindl Harald wrote: Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald mailto:h.rei...@thelounge.net>> wrote: Do you really have cronjobs which need to output

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:52 schrieb Michael Chapman: On Wed, 30 Dec 2015, Reindl Harald wrote: Standard mailing list etiquette is to reply-to-all on which mailing-list is that the case? be assured it's NOT standard on the majority on most it is considered rude OK. I'm not going to

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 12:09 schrieb Martin Pitt: Reindl Harald [2015-12-30 11:35 +0100]: in the first mail i wrote: "migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions" OK, I suggest to use systemd-run -t then, like Michael Chapman already sugge

[systemd-devel] systemd-run via crond: status=208/STDIN

systemd-219-26.fc22.x86_64 * in a ssh shell on Fedora 22 the script below works fine * called via /etc/crontab it fails * Unknown assignment StandardInput=null WHY? the intention is finally spwan namespaces (sadly not possible with F22/F23 and systemd-run at all) to protect the OS and replace

Re: [systemd-devel] empty a directory in service file as ExecStartPre

Am 02.01.2016 um 13:43 schrieb arnaud gaboury: ExecStartPre=/usr/bin/rm -f ${REPORTDIR}/ ExecStartPre=/usr/local/scripts/emptydir.sh $REPORTDIR signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@list

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

Am 10.01.2016 um 18:15 schrieb Mantas Mikulėnas: I remember this discussed before, I think one suggestion was to split into two targets, and only hold the login until the first target. Nobody implemented it though. But yes, pulseaudio.socket would be a requirement of that. If you don't want to

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

at 01:30, Reindl Harald wrote: Am 10.01.2016 um 18:15 schrieb Mantas Mikulėnas: I remember this discussed before, I think one suggestion was to split into two targets, and only hold the login until the first target. Nobody implemented it though. But yes, pulseaudio.socket would be a requireme

Re: [systemd-devel] Variables in the [Unit] section of a server

Am 13.01.2016 um 16:51 schrieb Steve Dickson: Is is possible to set a variable in the [Unit] section of a service? For example in rpc-gssd.service there is ConditionPathExists=/etc/krb5.keytab but for some installation the krb5.keytab is in a different place. The rpc.gssd daemon can be t

Re: [systemd-devel] known but not-listed units

Am 13.01.2016 um 17:26 schrieb Stijn De Weirdt: i'm having following situation on a centos 7.2 system (systemd-219-19.el7) there is a sysvinit service called netconsole that is not listed as a unit or unitfile, but the unitfile was generated and systemctl seems to be able to handle the unit

Re: [systemd-devel] Variables in the [Unit] section of a server

Am 14.01.2016 um 15:58 schrieb Lennart Poettering: And no, unit files are not supposed to be a templating language and do not support generlized variable expansion and quite frankly I should never even have added the limited env var expansion via EnvironmentFile= that ExecStart= supports, since

Re: [systemd-devel] Variables in the [Unit] section of a server

Am 14.01.2016 um 21:44 schrieb Lennart Poettering: On Thu, 14.01.16 19:52, Reindl Harald (h.rei...@thelounge.net) wrote: Am 14.01.2016 um 15:58 schrieb Lennart Poettering: And no, unit files are not supposed to be a templating language and do not support generlized variable expansion and

Re: [systemd-devel] No maintenance shell on local fs failure (/bin/sh: no such file or directory)

Am 15.01.2016 um 11:40 schrieb Frank Steiner: This didn't mean that /bin/echo was not found, but the CHDIR failed! That was caused by /root being a symbolic link to /local/home/root (we strictly separate any user data including root from the system, so that we can reformat / on reinstalling or

[systemd-devel] PrivateDevices=yes - /dev(u)random read-only

i recently faced a update for prosody (jabber-server) with the following change: Prosody: * Di Jan 12 2016 Robert Scheck 0.9.9-2 - Added upstream patch to open /dev/urandom read-only given that my systemd-unit has "PrivateDevices=yes" i would like to ask if the systemd-namespace is read-only

Re: [systemd-devel] Environment and additional command line options

Am 01.02.2016 um 10:54 schrieb arnaud gaboury: On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas wrote: Search systemd.unit(5) for "drop-in". There is no special syntax, the additional .conf files act exactly like a part of the main unit file. Yes I have seen it. This mechanism uses /etc/sy

Re: [systemd-devel] [ANNOUNCE] systemd v229

Am 11.02.2016 um 17:50 schrieb Lennart Poettering: * A new service setting RuntimeMaxSec= has been added that may be used to specify a maximum runtime for a service. If the timeout is hit, the service is terminated and put into a failure state failure state mak

Re: [systemd-devel] [ANNOUNCE] systemd v229

Am 11.02.2016 um 18:48 schrieb Lennart Poettering: On Thu, 11.02.16 19:47, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: 11.02.2016 19:32, Jóhann B. Guðmundsson пишет: * A new service setting RuntimeMaxSec= has been added that may be used to specify a maximum runt

Re: [systemd-devel] [RFC] the chopping block

Am 11.02.2016 um 19:18 schrieb Matthias Urlichs: On 11.02.2016 18:49, Lennart Poettering wrote: Again: this does not break systems with split off /var, as I tried to make very clear in my original mail. All that's needed is that the initrd mounts /var before handing off control to the main sys

Re: [systemd-devel] [RFC] the chopping block

Am 11.02.2016 um 20:37 schrieb Jóhann B. Guðmundsson: Arguably you should chop away the environment files support in the process since you are already wielding the axe... no - damned there are a ton of reasons to use them where it *do not matter* if you would do whatever this way or not th

Re: [systemd-devel] [RFC] the chopping block

Am 11.02.2016 um 22:11 schrieb Martin Pitt: Martin Pitt [2016-02-11 21:59 +0100]: This would apply if you boot with systemd, then install sysvinit, and want to reboot the machine (using SysV's /sbin/reboot), right? Or the other way around? This is still somewhat relevant for Debian, but maybe

Re: [systemd-devel] [ANNOUNCE] systemd v229

Am 11.02.2016 um 22:19 schrieb Dave Reisner: On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: I just tagged the v229 release of systemd. Enjoy! CHANGES WITH 229: * When the stacktrace is extracted from processes of system users, this is now done as "sy

Re: [systemd-devel] [RFC] the chopping block

Am 13.02.2016 um 13:01 schrieb Lennart Poettering: My maingoal here is really about having read-access to things, and being able to schedule stuff based on configuration and existance of things, even if that stuff cannot be written to yet. If /var is mounted this late it makes things a lot more

Re: [systemd-devel] [RFC] the chopping block

Am 13.02.2016 um 14:17 schrieb Christian Seiler: On 02/13/2016 01:44 PM, Reindl Harald wrote: [root@mail-gw:~]$ cat /etc/fstab | grep log UUID=a8fc620d-8046-47a3-8b63-102c525ce5e8 /var/log ext4 defaults, noexec 0 1 To be fair to Lennart: your specific use case, if /var/log is just a

Re: [systemd-devel] systemd-devel Digest, Vol 71, Issue 19

Am 19.03.2016 um 13:29 schrieb Marcos DeSousa: How to i unsubscribe from this list? by read mail-headers or click on the link in list-footers as for any other mailing-list List-Unsubscribe: ,

[systemd-devel] systemd-run: why is output buffered now?

please take a look at https://bugzilla.redhat.com/show_bug.cgi?id=1319475 - this is a unlucky behavior change, not only for usability but for scripts with heavy output it's also a memory usage problem signature.asc Description: OpenPGP digital signature __

Re: [systemd-devel] systemctl --user fails because no D-BUS.

Am 24.03.2016 um 20:26 schrieb Tomasz Torcz: On Thu, Mar 24, 2016 at 08:01:23PM +0200, Mantas Mikulėnas wrote: On Thu, Mar 24, 2016 at 6:21 PM, Flavio Leitner wrote: Hi, I am trying to create services and timers per user but on a recent CentOS minimal installation it doesn't work out of th

Re: [systemd-devel] Different behavior when OpenVPN is started as a service through systemd

Am 31.03.2016 um 23:07 schrieb Piotr Dobrogost: When I start OpenVPN as a deamon from command line like this: `sudo OPENSSL_ENABLE_MD5_VERIFY=1 openvpn --daemon --config /etc/openvpn/xxx.conf` the tunnel comes up with no problem. However, when I start it as a systemd service I get this error:

Re: [systemd-devel] systemd-run: why is output buffered now?

Am 01.04.2016 um 21:40 schrieb Lennart Poettering: On Sun, 20.03.16 14:22, Reindl Harald (h.rei...@thelounge.net) wrote: please take a look at https://bugzilla.redhat.com/show_bug.cgi?id=1319475 - this is a unlucky behavior change, not only for usability but for scripts with heavy output

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Am 10.04.2016 um 10:17 schrieb Martin Pitt: Any user running a system with multiple NICs should be willing and capable of choosing and assigning these names. To be frank, this is the attitude of the 90's when you had to sit down with a thick book and spend a week until your Linux system was u

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Am 10.04.2016 um 16:57 schrieb Martin Pitt: Andrei Borzenkov [2016-04-10 11:31 +0300]: It had been working out of the box for quite a lot of users actually. Because we had a mechanism for stable (but not predictable) interfaces names, the 75-persistent-net-generator.rules thingy. Without eit

Re: [systemd-devel] on the default for PredictableNetworkInterfaceNames

Am 11.04.2016 um 10:40 schrieb Martin Pitt: Reindl Harald [2016-04-10 17:44 +0200]: Because we had a mechanism for stable (but not predictable) interfaces names, the 75-persistent-net-generator.rules thingy. Without either, the first time you plugged in a second card/USB dongle/add an ibmveth

Re: [systemd-devel] ReadOnlyDirectories and new mounts

Am 11.04.2016 um 21:22 schrieb Yuriy M. Kaminskiy: I have long-running service with tight restrictions: ReadOnlyDirectories=/ ReadWriteDirectories=-/proc ReadWriteDirectories=-/var/lib/foobar ReadWriteDirectories=-/var/log/foobar ReadWriteDirectories=-/var/run I mounted so

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 04:26 schrieb Xen: Greg KH schreef op 12-04-16 00:14 How you determine if a device is "onboard" or "offboard"? Are you going to know when all "onboard" devices are found before you do anything else? How? I don't know, do you know? I am just a nitwit right. The distinction

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 14:00 schrieb Xen: Martin Pitt schreef op 12-04-16 12:57: Xen [2016-04-12 3:37 +0200]: The trick to turn it off on the website doesn't work: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules It does (at least on Debian, Ubuntu, and Fedora), but you need to rebuild

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 20:37 schrieb Xen: Reindl Harald schreef op 12-04-16 11:24: Regular hardware should not suddenly appear out of nowhere, but I do not know about that Thunderbolt thing you mentioned that is nonsense * USB hardware is often *onboard* like SD-card slots on ProLiant

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 12.04.2016 um 21:24 schrieb Xen: However currently for me, biosdev renumbers these, while my scheme wouldn't wow - you even don't realise that "biosdevname" and https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ are two completly different things si

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 13.04.2016 um 00:03 schrieb Xen: Reindl Harald schreef op 12-04-16 21:35: Am 12.04.2016 um 21:24 schrieb Xen: However currently for me, biosdev renumbers these, while my scheme wouldn't wow - you even don't realise that "biosdevname" and https://www.freedeskt

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 13.04.2016 um 01:20 schrieb Xen: Greg KH schreef op 13-04-16 01:16: On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote: All you need to do is wait a few seconds before you start renaming Most machines boot to login faster than a "few seconds", so: Most machines boot to login faster th

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 13.04.2016 um 02:42 schrieb Xen: Greg KH schreef op 13-04-16 01:29: On Wed, Apr 13, 2016 at 01:20:05AM +0200, Xen wrote: All execpt for 4-socket and larger servers. They take tens of minutes in the BIOS and then less than a minute in the kernel/userspace, depending on the amount of memo

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 13.04.2016 um 03:08 schrieb Xen: Reindl Harald schreef op 13-04-16 02:06: Am 13.04.2016 um 01:20 schrieb Xen: Greg KH schreef op 13-04-16 01:16: On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote: All you need to do is wait a few seconds before you start renaming Most machines boot

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 13.04.2016 um 02:15 schrieb pgndev: On Tue, Apr 12, 2016 at 5:06 PM, Reindl Harald wrote: Is there a ML anywhere on which you don't sputter, fume, rant and insult? interesting that you say that to me in this thread while the OP started very early to call people "Idiot"

Re: [systemd-devel] on the default for, PredictableNetworkInterfaceNames

Am 13.04.2016 um 18:51 schrieb Sam Tresler: I didn't make it through the rest of your post, but thought I'd chime in with `ifconfig` has been deprecated since 2009. 2009. I don't get deep into the distros, but I really wish they'd stop shipping it. `man ip` should give you info on the right t

Re: [systemd-devel] on the default for, PredictableNetworkInterfaceNames

Am 14.04.2016 um 11:45 schrieb Jetchko Jekov: On Thu, Apr 14, 2016 at 10:57 AM Reindl Harald can iterate over. > > $ ip -o a | awk '{print $2}' | uniq blub - gives a (incomplete) list of the current interfaces - so what is the advantage you wnated to dem

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 15.04.2016 um 17:48 schrieb Xen: Reindl Harald schreef op 13-04-16 10:24: 4xHDD raid-10, hardware from 2011 Startup finished in 660ms (kernel) + 5.380s (initrd) + 12.769s (userspace) = 18.810s os on sd-card Startup finished in 375ms (kernel) + 4.306s (initrd) + 8.323s (userspace

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 15.04.2016 um 17:54 schrieb Xen: Reindl Harald schreef op 13-04-16 10:26: What are you on about? Just because I don't have a superfast system, I cannot say anything? no beause of "hmm let wait 3 seconds for something we don't know if it ever appears and how long it would

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 15.04.2016 um 17:42 schrieb Xen: Greg KH schreef op 13-04-16 05:04: You are lying to me and trying to lead me in the woods. The stuff you say is stuff people say that in the end don't end up being true. It does not even agree with the reality of how the system works currently. They are nons

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 15.04.2016 um 18:02 schrieb Xen: Reindl Harald schreef op 15-04-16 17:55: so 3 seconds is unacceptable and the idea ist a joke in general because you wait for something possibly happen while you don't know how long you have to wait and jsut hope for luck - that's not a good

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 15.04.2016 um 21:06 schrieb Xen: If you cannot give me a default mapping automatically, why not allow me to generate one easily? Is there a tool that can take the current device and produce the list I proposed? just use network.service aka /etc/init.d/network, enter the MAC and you are do

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 16.04.2016 um 06:46 schrieb Andrei Borzenkov: 16.04.2016 03:14, Reindl Harald пишет: Am 15.04.2016 um 21:06 schrieb Xen: If you cannot give me a default mapping automatically, why not allow me to generate one easily? Is there a tool that can take the current device and produce the list

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 16.04.2016 um 14:20 schrieb Xen: So I deleted your email that belonged to this piece and then tried to find what you wrote about myself. But the beginning of it is of course that Debian/Ubuntu doesn't have "sysconfig" directory. I know OpenSUSE does, but Debian doesn't. that is all complet

Re: [systemd-devel] Network Interface Names: solution for a desktop OS

Am 16.04.2016 um 16:15 schrieb Xen: The backlash against this renaming may have been enormous but people just say "oh, that's political". Systemd in general has been the single thing with the most opposition in the history of Linux that I'm aware of. stop spreading uneducated nonsense, the NI

Re: [systemd-devel] PredictableInterfaceNames and Debian

honestly: what about just create your own operating system and leave us all in peace with endless mails mixing a dozen of rarely topics or just use a distribution like RHEL/CentOS/Fedora where you can just use ifup/ifdown scripts and tie MAC-address and interface-names togehter? > The only ot

Re: [systemd-devel] PredictableInterfaceNames and Debian

Am 16.04.2016 um 21:23 schrieb Xen: Tobias Hunger schreef op 16-04-16 21:13: Am 16.04.2016 18:46 schrieb "Xen" mailto:l...@xenhideout.nl>>: And if you did need to write stuff: why not queue the changes and then apply them after the remount rw, if that is necessary? Create an overlay to /etc ;

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

Am 19.04.2016 um 12:10 schrieb Lennart Poettering: > On Mon, 18.04.16 23:19, James Hogarth (james.hoga...@gmail.com) wrote: > >> Hi all, >> >> There's been some discussion today about the impact of >> https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the problem >> actually lies. >> >>

Re: [systemd-devel] Fwd: Stopping a service at a specific time or after a specific duration

Am 20.04.2016 um 17:29 schrieb Jamie Kitson: For stopping after a duration you can use RuntimeMaxSec=, introduced in v229. Thanks. The man page says: If this is used and the service has been active for longer than the specified time it is terminated and put into a failure state and i

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

On 20.04.2016 06:47, Chris Murphy wrote: > On Tue, Apr 19, 2016 at 4:10 AM, Lennart Poettering > wrote: > >> >> So what precisely are you proposing? That we actively search for the >> swap partition in the hibernate-resume generator? > > I think the main thing James is after, I know I'm in this

Re: [systemd-devel] Fwd: Stopping a service at a specific time or after a specific duration

Am 22.04.2016 um 17:03 schrieb Lennart Poettering: On Thu, 21.04.16 10:32, Reindl Harald (h.rei...@thelounge.net) wrote: Thanks. The man page says: If this is used and the service has been active for longer than the specified time it is terminated and put into a failure state and i call

Re: [systemd-devel] Fwd: Stopping a service at a specific time or after a specific duration

Am 22.04.2016 um 17:07 schrieb Reindl Harald: Am 22.04.2016 um 17:03 schrieb Lennart Poettering: On Thu, 21.04.16 10:32, Reindl Harald (h.rei...@thelounge.net) wrote: Thanks. The man page says: If this is used and the service has been active for longer than the specified time it is

Re: [systemd-devel] Require a systemd.unit to finish completely before other services(units) are started

Am 26.04.2016 um 16:37 schrieb Mantas Mikulėnas: On Tue, Apr 26, 2016 at 3:14 PM, george Karakou mailto:mad-proffes...@hotmail.com>> wrote: It's actually NetworkManager-dispatcher whose actual job is -if i am not mistaken- to run some scripts after NetworkManager main process. Thou

Re: [systemd-devel] MYSQL SERVICE FAILED

how is that a systemd-topic? complain at Ubuntu for theri broken package! Am 30.04.2016 um 20:32 schrieb Alessandro Cellini: invoke-rc.d: initscript mysql, action "start" failed. dpkg: error processing package mysql-server-5.7 (--configure): subprocess installed post-installation script returne

Re: [systemd-devel] Is there a way to see if a script is run from systemd

Am 07.05.2016 um 15:00 schrieb Cecil Westerhof: I have written a Bash script to be used for a service. Is it possible to see in the script if it is run from systemd? I could use this for debugging purposes just set a environment variable in the systemd unit or check against a lot of env-vars

Re: [systemd-devel] Failed to restart ntpd

Am 12.05.2016 um 09:17 schrieb liuxueping: Hi: It failed when i restarted ntpd service,the log showed:ntpd[3163]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING,and the ps command result showed: ntp 3993 0.0 0.0 0 0 ?Ds 10:21 0:

Re: [systemd-devel] Failed to restart ntpd

Main PID: 981 (ntpd) CGroup: /system.slice/ntpd.service └─981 /usr/sbin/ntpd -4 -d -u ntp:ntp -p /var/run/ntpd.pid -g 在 2016/5/12 16:51, Reindl Harald 写道: Am 12.05.2016 um 09:17 schrieb liuxueping: Hi: It failed when i restarted ntpd service,the log showed:ntpd[3163]: unable to bind to wild

Re: [systemd-devel] when/where was support for assigning "ethX" names removed?

Am 12.05.2016 um 19:20 schrieb Chris Friesen: Could someone point me to the commit that removed support for assigning "ethX" names based on MAC addresses? Alternately, can someone suggest a way to get equivalent behaviour (the ability to set "ethX" names based on MAC address) using the current

Re: [systemd-devel] when/where was support for assigning "ethX" names removed?

Am 12.05.2016 um 19:52 schrieb Chris Friesen: On 05/12/2016 11:35 AM, Reindl Harald wrote: Am 12.05.2016 um 19:20 schrieb Chris Friesen: Could someone point me to the commit that removed support for assigning "ethX" names based on MAC addresses? Alternately, can someone sugges

Re: [systemd-devel] when/where was support for assigning "ethX" names removed?

Am 12.05.2016 um 20:34 schrieb Chris Friesen: So I guess the question is, how do I rename a device to a name that already exists? (Like supposing I want to swap the names of eth0 and eth1.) you don't - if it works - be lucky - i am on some machines but you can't do that relieable on many mac

Re: [systemd-devel] when/where was support for assigning "ethX" names removed?

Am 12.05.2016 um 21:46 schrieb Chris Friesen: So...anyone have any ideas why this isn't working? Is it because I'm trying to use the "eth" namespace which could possibly collide with the kernel naming? likely yes the config below has a reason while using network.service and classical ifcfg

Re: [systemd-devel] systemctl how to stop a service

Am 14.05.2016 um 10:55 schrieb liuxueping: The result of "ps aux" before sleep 5 shows: root 6698 0.0 0.0 0 0 ?Ds 08:45 0:00 [ntpd] After 5 seconds,there is no ntpd process in system. the stop status is 0,the execution of the stop command is successful,the PID of the

[systemd-devel] SuccessExitStatus not correctly refelected in "systemctl status"

unit has "SuccessExitStatus=1" and correctly is not in failed-state but "systemctl status" is plain wrong: Process: 19572 ExecStart=/usr/share/spamassassin/sa-update.cron (code=exited, status=1/FAILURE) signature.asc Description: OpenPGP digital signature

Re: [systemd-devel] mounting the root file system using systemd unit file

Am 15.05.2016 um 15:34 schrieb Mantas Mikulėnas: What should be the way to mount the root file system using systemd unit file (i.e: without any `/etc/fstab` configuration file)? Asking the system to mount anything at / doesn't make much sense, because the fact that systemd is running a

Re: [systemd-devel] mounting the root file system using systemd unit file

Am 15.05.2016 um 16:48 schrieb fb.dev.gen: @Mikhail: thank you for your answer. @killermoehre: my special reason to not use `/etc/fstab` is that I'm testing Clear Linux which do not provides any `/etc/fstab` configuration file and uses extensively all systemd versatil

Re: [systemd-devel] systemctl how to stop a service

since unit was started. Log output is incomplete or unavailable. 在 2016/5/14 18:32, Reindl Harald 写道: Am 14.05.2016 um 10:55 schrieb liuxueping: The result of "ps aux" before sleep 5 shows: root 6698 0.0 0.0 0 0 ?Ds 08:45 0:00 [ntpd] I'm not sure how

Re: [systemd-devel] This patch adds SELinux support to systemd for socket creation.

On 07/23/2010 01:39 PM, Kay Sievers wrote: On Fri, Jul 23, 2010 at 13:21, Daniel J Walsh wrote: On 07/23/2010 06:56 AM, Kay Sievers wrote: On Fri, Jul 23, 2010 at 12:30, Daniel J Walsh wrote: I though I saw avc's caused because systemd creating some devices with the wrong labels? I searched

Re: [systemd-devel] [PATCH] var-run.service: create console dir needed by pam

On 09/24/2010 05:35 PM, Kay Sievers wrote: > On Fri, Sep 24, 2010 at 16:26, wrote: >> +ExecStart=/bin/mkdir /var/run/console ; /bin/chmod 0755 /var/run/console ; >> -/sbin/restorecon /var/run/console > > Please let the broken pam_console finally die. It was never correct do that. > > The last

Re: [systemd-devel] [PATCH 2/2] Adding binary to shutdown the system

On 10/06/2010 04:15 PM, Gustavo Sverzut Barbieri wrote: From: Fabiano Fidencio This functions are working as follows: - Send a SIGTERM to all processes that may be finished - Send a SIGKILL to all processes that still live and may be finished - Try to unmount all mount points

Re: [systemd-devel] Trying systemd in Fedora 14

On 11/11/2010 12:03 AM, Lennart Poettering wrote: On Wed, 03.11.10 11:03, Felix Braun (felix.br...@mail.mcgill.ca) wrote: Hi there, heya, while systemd wasn't chosen as a default init system for F14, it is included in the repositories. That way, it was argued, more people could give it a tr

Re: [systemd-devel] [PATCH] vconsole: properly set terminal UTF-8 mode

Am 17.02.2011 19:52, schrieb Andrey Borzenkov: > As it stands now, dracut 008 in generic (not hostonly) mode explicitly > disables UTF-8 because UNICODE is not set: > > modules.d/10i18n/console_init: > > set_keyboard() { > local param > > [ "${UNICODE}" = 1 ] && param=-u || param=-a >

Re: [systemd-devel] [PATCH] vconsole: properly set terminal UTF-8 mode

Am 18.02.2011 09:13, schrieb Harald Hoyer: > Am 17.02.2011 19:52, schrieb Andrey Borzenkov: >> As it stands now, dracut 008 in generic (not hostonly) mode explicitly >> disables UTF-8 because UNICODE is not set: >> >> modules.d/10i18n/console_init: >> >&

Re: [systemd-devel] systemd console messages (crippled)

Am 06.01.2015 um 15:42 schrieb Zbigniew Jędrzejewski-Szmek: On Tue, Jan 06, 2015 at 02:51:50PM +0300, Nikolai Zhubr wrote: Hi people, I'm now fighting with opensuse 13.2 failing to mount some or all disks at boot, obviously resulting in unusable system. This distribution is systemd-based, henc

Re: [systemd-devel] systemd console messages (crippled)

Am 06.01.2015 um 16:04 schrieb Elias Probst: On 01/06/2015 03:53 PM, Reindl Harald wrote: Messages are truncated because there's only so much space on 80 column text displays, and filling the screeen with wrapped unit names is not useful anyway. This is supposed to give you an overview of

Re: [systemd-devel] Second (erroneous) check of rootfs?

On 08.01.2015 07:18, Andrei Borzenkov wrote: > В Wed, 07 Jan 2015 23:23:27 -0300 > Cristian Rodríguez пишет: > >> El 07/01/15 a las 22:55, Nikolai Zhubr escribió: >>> 08.01.2015 4:12, Cristian Rodríguez: El 07/01/15 a las 21:43, Lennart Poettering escribió: > Maybe suse forgot to in

Re: [systemd-devel] Second (erroneous) check of rootfs?

On 08.01.2015 16:55, Lennart Poettering wrote: > On Thu, 08.01.15 16:34, Harald Hoyer (harald.ho...@gmail.com) wrote: > >> IMHO >> >> systemd-fsck-root.service should be removed entirely and generated by the >> fstab-generator in the real root like all the other

Re: [systemd-devel] Second (erroneous) check of rootfs?

On 08.01.2015 18:30, Andrei Borzenkov wrote: > В Thu, 08 Jan 2015 17:12:25 +0100 > Harald Hoyer пишет: > >> On 08.01.2015 16:55, Lennart Poettering wrote: >>> On Thu, 08.01.15 16:34, Harald Hoyer (harald.ho...@gmail.com) wrote: >>> >>>> IMHO >>

Re: [systemd-devel] Second (erroneous) check of rootfs?

Am 11.01.2015 um 12:48 schrieb Nikolai Zhubr: I suppose this traditional (historical) technique of maintaining mount-count, running fsck at boot time before remount r/w, etc, should not be so much attributed specifically to ext filesystem. Most probably it existed long before even ext2 appeared.

Re: [systemd-devel] systemctl status not showing still running processes in inactive .mount unit cgroups (NFS specifically)

On 15.01.2015 10:28, Colin Guthrie wrote: > Although if the script is in bash I'd use "if [ -d ..." rather than "if > test -d ..." as (and bash experts (Harald?) can correct me here if I'm > wrong) I believe [ is a bash built in (even if it is a binary in

Re: [systemd-devel] Readahead collect - root filesystem only?

Am 15.01.2015 um 14:40 schrieb Nikolai Zhubr: 15.01.2015 16:07, Cristian Rodríguez: The readahead collector is no longer included in systemd. Hm. It is still there in not-very-old opensuse 13.2 ... Anyway. Where has it gone then? Is it a separate tool now or got obsoleted by something else? I

Re: [systemd-devel] Readahead collect - root filesystem only?

Am 15.01.2015 um 14:33 schrieb Zbigniew Jędrzejewski-Szmek: On Thu, Jan 15, 2015 at 02:31:22PM +0100, Reindl Harald wrote: Am 15.01.2015 um 14:40 schrieb Nikolai Zhubr: 15.01.2015 16:07, Cristian Rodríguez: The readahead collector is no longer included in systemd. Hm. It is still there in

Re: [systemd-devel] [PATCH] Add support for "ROOT=" on the kernel command line

On 15.01.2015 16:24, har...@redhat.com wrote: > From: Harald Hoyer > > "ROOT=" mounts the initial ramdisk with a tmpfs filesystem. Ok, not true. Omitting "root=" will mount the initial ramdisk as a tmpfs filesystem, if tmpfs support is compiled in the kernel. Se

Re: [systemd-devel] [PATCH] Add support for "ROOT=" on the kernel command line

On 15.01.2015 16:45, Harald Hoyer wrote: > On 15.01.2015 16:24, har...@redhat.com wrote: >> From: Harald Hoyer >> >> "ROOT=" mounts the initial ramdisk with a tmpfs filesystem. > > Ok, not true. Omitting "root=" will mount the initial ramdisk as a t

<    5   6   7   8   9   10   11   12   13   14   >