Re: [systemd-devel] systemd-sysusers

Am 05.02.2018 um 10:47 schrieb Michael Chapman: On Mon, 5 Feb 2018, Reindl Harald wrote: Am 05.02.2018 um 06:56 schrieb Michael Chapman:  On Mon, 5 Feb 2018, Johannes Ernst wrote:  It appears systemd-sysusers does not create home directories. On the  other hand, it picks (largely

Re: [systemd-devel] systemd-sysusers

Am 05.02.2018 um 19:35 schrieb Johannes Ernst: On Feb 5, 2018, at 10:31, Zbigniew Jędrzejewski-Szmek wrote: systemd-sysusers [[ -d /var/lib/foo ]] && mkdir -m755 /var/lib/foo chown $(id -u foo):$(id -g foo) /var/lib/foo # /usr/lib/tmpfiles.d/foo.conf d /var/lib/foo 0755 foo foo - (BTW,

Re: [systemd-devel] Hints for upgrading systemd on a running system

Am 20.02.2018 um 20:00 schrieb Paul Menzel: Dear systemd folks, We finally are going to upgrade from a very old systemd version 27 from 2011 to the current systemd v237. (Historical reasons.) hopefully you have a working backup Anyway, I already was told about `systemctl daemon-reexec`, an

Re: [systemd-devel] Hints for upgrading systemd on a running system

Am 20.02.2018 um 22:04 schrieb Mantas Mikulėnas: On Tue, Feb 20, 2018, 21:06 Reindl Harald <mailto:h.rei...@thelounge.net>> wrote: Am 20.02.2018 um 20:00 schrieb Paul Menzel: > Dear systemd folks, > > We finally are going to upgrade from a very old syst

Re: [systemd-devel] Xorg is continuously crashing and dumping core, this is the stack trace from journalctl -p 3 -xb

but how is that a systemd-problem and even if you mail this to the correct list you don't share any useful informations (OS, software-versions..) so what do you expect other than "no, mine works" Am 11.03.2018 um 05:23 schrieb Dude And: Process 737 (Xorg) of user 0 dumped core.  

[systemd-devel] systemd-shutdown: Failed to parse /proc/self/moutinfo

see https://bugzilla.redhat.com/show_bug.cgi?id=1554943 including screenshot ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd-shutdown: Failed to parse /proc/self/moutinfo

release what do you expect? if you have some problem create a users-list - until now *this* is also the users list and in the meantime learn to use your mail-clients reply-to-list button 2018-03-13 16:54 GMT+01:00 Reindl Harald : see https://bugzilla.redhat.com/show_bug.cgi?id=1554943 including

Re: [systemd-devel] systemd-shutdown: Failed to parse /proc/self/moutinfo

screen too - you don't care: well, ignore it and be done - what exactly is your problem? On Tue, Mar 13, 2018 at 1:09 PM, Reindl Harald <mailto:h.rei...@thelounge.net>> wrote: Am 13.03.2018 um 19:04 schrieb Michael Biebl: My problem is sooo important, I need to pe

Re: [systemd-devel] safe and fast shutdown/reboot

Am 16.03.2018 um 11:36 schrieb prashantkumar dhotre: Thanks I understand that 'systemctl isolate other.target' will stop all present services and start services of other.target My thinking is : I can put all my apps in my.target and my.target can start after multi-user.target. that are all

Re: [systemd-devel] systemd-shutdown: Failed to parse /proc/self/moutinfo

Am 20.03.2018 um 17:26 schrieb Lennart Poettering: On Mi, 14.03.18 00:22, Reindl Harald (h.rei...@thelounge.net) wrote: Am 14.03.2018 um 00:00 schrieb Ryan Gonzalez: You literally sent this out 1 minute after posting the bug. At least give it time to breath first... what the hell - sorry

Re: [systemd-devel] systemd-shutdown: Failed to parse /proc/self/moutinfo

Am 20.03.2018 um 18:13 schrieb Lennart Poettering: On Di, 20.03.18 18:06, Reindl Harald (h.rei...@thelounge.net) wrote: Am 20.03.2018 um 17:26 schrieb Lennart Poettering: On Mi, 14.03.18 00:22, Reindl Harald (h.rei...@thelounge.net) wrote: Am 14.03.2018 um 00:00 schrieb Ryan Gonzalez

Re: [systemd-devel] GPL and unit/conf files

Am 11.05.2018 um 15:48 schrieb Paul Jakma: > On Fri, 11 May 2018, Reindl Harald wrote: > >> that's not how you are supposed to work with systemd-configs > > Agreed. The technicalities in the app concerned of how it delivers these > settings probably could be do

Re: [systemd-devel] GPL and unit/conf files

Am 11.05.2018 um 15:21 schrieb Paul Jakma: > logind.conf has a GPL header, as do things like getty@.service. > > If I needed to make changes to logind.conf, and wanted to bundle a > modified logind.conf with a GPL-incompatible application, is that > allowed? that's not how you are supposed to

Re: [systemd-devel] Disabling package-managed user units

https://wiki.archlinux.org/index.php/Systemd/User Similarly to system units, user units are located in the following directories (ordered by ascending precedence): /usr/lib/systemd/user/ where units provided by installed packages /etc/systemd/user/ where system-wide user units are placed by the s

Re: [systemd-devel] Running “telinit u” on glibc update

Am 16.05.2018 um 15:01 schrieb Florian Weimer: > In Fedora, for historic reasons, we run “/sbin/telinit u” after > installing a new glibc RPM package version. > > Does this still make sense?  Should we remove the code which invokes > telinit from the glibc package? how do you come to that concl

Re: [systemd-devel] option to wait for pid file to appear

Am 17.05.2018 um 11:25 schrieb Igor Bukanov: > I have a service unit for nginx that uses Type=forking and PIDFile. > That works, but occasionally I see in the log a message like > > nginx.service: PID file /run/nginx/nginx.pid not readable (yet?) after > start: No such file or directory > > Aft

Re: [systemd-devel] option to wait for pid file to appear

Am 17.05.2018 um 12:12 schrieb Igor Bukanov: > On 17 May 2018 at 11:58, Mantas Mikulėnas wrote: >> Have you tried without the PIDFile= setting at all? > > As far as I can see that breaks live updates that nginx supports where > it starts a new process and workers and then gracefully terminates

Re: [systemd-devel] option to wait for pid file to appear

Am 17.05.2018 um 22:54 schrieb Igor Bukanov: > On 17 May 2018 at 19:23, Lennart Poettering wrote: > >> So yes, this is a bug in nginx. They really should fix that. And this >> is not only broken when you use systemd, but on sysvinit too, as a >> command like this would likely fail there too: "s

Re: [systemd-devel] systemd DB2 StartUp/Shutdown service on Red Hat Enterprise Linux Server release 7.4 (Maipo)

Am 25.05.2018 um 17:32 schrieb Leonard Rofman: > Hello aleivag, > > Thank you for answering my email. > > I’ve made some changes to db2.service file but unfortunately the problem > on reboot still persists. > > Please review the contents of the service file and hopefully you have > some other r

Re: [systemd-devel] Core dump

Am 10.06.2018 um 14:50 schrieb Povilas Brilius: > Process 613 (plymouthd) crashed and dumped core. > > This usually indicates a programming error in the crashing program and > should be reported to its vendor as a bug why don't you then report it to your distribution? __

Re: [systemd-devel] Graphical session targets as standard

what problem needs to be solved? [root@srv-rhsoft:/usr/lib/systemd/system]$ ls | grep graphical drwxr-xr-x. 2 root root 4,0K 2018-05-04 12:46 graphical.target.wants lrwxrwxrwx 1 root root 16 2018-05-04 10:40 default.target -> graphical.target -rw-r--r-- 1 root root 558 2018-02-21 12:29 graphi

Re: [systemd-devel] starting a service before anything else....

Am 28.06.2018 um 16:55 schrieb MALET Jean-Luc: > I'm in charge of setting up an embedded solution based on debian, so on > systemd, I'm more used to old init process, that was easy to tweak > because based on script... but well... times seems now on systemd. > > I'm really puzzled because since t

Re: [systemd-devel] starting a service before anything else....

Am 02.07.2018 um 10:50 schrieb MALET Jean-Luc: > Le 28/06/2018 à 17:02, Reindl Harald a écrit : >> Am 28.06.2018 um 16:55 schrieb MALET Jean-Luc: >>> I'm in charge of setting up an embedded solution based on debian, so on >>> systemd, I'm more used to old

Re: [systemd-devel] How to build only udev

Am 04.07.2018 um 20:36 schrieb Kevin Greene: > 2018-07-03 18:18 GMT-07:00 Mike Gilbert >: > > On Tue, Jul 3, 2018 at 7:55 PM, Kevin Greene > wrote: > > I am building libusb, and I want to build it with udev support. I don't > ne

Re: [systemd-devel] upower fails with PrivateNetwork=true

Am 07.07.2018 um 14:35 schrieb Michael Biebl: > Tbh, I find it a bit confusing that we have three mechanisms now > (PrivateNetwork, RestrictAddressFamilies, IPAddressDeny) and when one > is supposed to use which one of these. why * PrivateNetwork -> big hammer service needs no network stuff a

Re: [systemd-devel] Failed to start Apache Tomcat Web Application Container

-- Subject: Unit tomcat.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel this is nonsense pointing out that you are using a real old systemd (it was removed long ago and never made any sense) - this is SYSTEMD and not Apache Tomcat -

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

Am 25.07.2018 um 17:01 schrieb Lennart Poettering: > On Mi, 25.07.18 11:23, George Xie (george...@gmail.com) wrote: > >> thanks for your reply. >> >> odds enough, on both aforementioned boxes, MemoryAccounting is set >> to no: > > On old systemd versions we'd fill in the account props if the ke

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

Am 25.07.2018 um 17:49 schrieb Lennart Poettering: > On Mi, 25.07.18 17:06, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Am 25.07.2018 um 17:01 schrieb Lennart Poettering: >>> On Mi, 25.07.18 11:23, George Xie (george...@gmail.com) wrote: >>> >>>

Re: [systemd-devel] systemctl show outputs incorrect MemoryCurrent value

Am 26.07.2018 um 05:20 schrieb George Xie: >> dealing internally with surch arbiatry numbers is still a differnt world >> than ouput it in a user-tool like "systemctl show" which could simply >> translate it to some meaningful string >> no user cares about UINT64_MAX in such outputs > > quoted f

[systemd-devel] CtrlAltDelBurstAction

CtrlAltDelBurstAction= Defines what action will be performed if user presses Ctrl-Alt-Delete more than 7 times in 2s. Can be set to "reboot-force", "poweroff-force", "reboot-immediate", "poweroff-immediate" or disabled with "none". Defaults to "reboot-force" [root@srv-rhsoft:~]$ 7~7~ 7~7~7~7~7~7~7

Re: [systemd-devel] Restarting a service as user instead as root

Am 13.08.2018 um 11:28 schrieb Cecil Westerhof: > I have a service that is run as a different user as root. But only root > can restart the service. Is there a way to make 'systemctl restart' work > for the user that runs the service? not for system services just because a service binary drops

Re: [systemd-devel] PrivateDevices= together with DevicePolicy=

Am 21.08.2018 um 09:57 schrieb Umut Tezduyar Lindskog: > I am turning on PrivateDevices and as a result getting a minimal /dev > tree for my service. Then I would like to add some selected devices > with DevicePolicy=auto & DeviceAllow=/dev/cam0. As a result, I don't > see the device /dev/cam0 in

Re: [systemd-devel] non-dev systemd-devel package for Linux

Am 31.08.18 um 16:51 schrieb Sayeed hyder: > Where can I get the link of available non-dev packages for different > Linux distros? I am specifically looking for rhel version  of libudev > package. from the package repo of teh distribution? just download the CentOS one which is identical to RHEL _

Re: [systemd-devel] non-dev systemd-devel package for Linux

nd package > yum install libudev-devel    works > > Is there any runtime (non-dev) package for rhel/centos distro? If so, > what is the package name I should look for? > > > thanks, > Sayeed > > > On Fri, Aug 31, 2018 at 8:24 AM, Reindl Harald <mailto:h.re

Re: [systemd-devel] non-dev systemd-devel package for Linux

Am 31.08.18 um 19:52 schrieb Sayeed hyder: > Thanks Silvio. Unfortunately, I cannot use devel. IIUC, rhel/centos does > not provide a non-dev systemd package? That does not sound right WTF is a "non-dev" package to begin with? ___ systemd-devel mailing

Re: [systemd-devel] non-dev systemd-devel package for Linux

Am 31.08.18 um 23:41 schrieb Sayeed hyder: > Thanks, I am not confused between udev and devel. Let me explain a bit > more. My understanding is with the devel package, when I include in my > project, I am downloading all the header files and redistributing the > code. With the non-devel runtime p

Re: [systemd-devel] blocking service on shutdown

Am 02.09.18 um 15:37 schrieb Ralf Sieger: > I want my system to pause on shutdown to wait till my backup has > finished if it is running. > For this I've created this small service: >   > [Unit] > Description=borg shutdown wait > [Service] > Type=oneshot > ExecStart=/bin/true > RemainAfterExit=tr

Re: [systemd-devel] blocking service on shutdown

Am 02.09.18 um 16:41 schrieb Ralf Sieger: > Hi Harald, >   >> what exactly does "/usr/local/bin/wait_borg"? > Small script which terminates whn no "borg" processes exist any more. > >> why are the no dependecnies to the services it waits for? > The process it waits for is not a service but a nor

Re: [systemd-devel] blocking service on shutdown

Am 03.09.18 um 00:04 schrieb Amit Saha: > > I had to achieve something similar a while back and this is how I ended > up doing:  > > https://echorand.me/doing-something-before-systemd-shuts-your-supervisord-down.html when "ExecStop=/bin/sleep 300" is the solution if want my problems back _

Re: [systemd-devel] How to keep the new kernel running features ?

Am 17.09.18 um 15:57 schrieb Tomasz Torcz: > On Mon, Sep 17, 2018 at 09:27:20AM +, Dorian ROSSE wrote: >> Hello Dear IT team worker, >> >> Since yesterday my running kernel is 4.18.8 instead 4.17.2 but at each >> reboot I have a system crashed, >> How to keep this laster running kernel witho

Re: [systemd-devel] exim4 only queues mails sent by systemd service

Am 24.09.18 um 22:07 schrieb Dan Nicholson: > This is exactly what exim does when run via sendmail (which mail and > mutt likely use behind the scenes). I had a very similar setup to the > OP using exim on one of our servers and was perplexed why the queue > wasn't being flushed immediately. Here

Re: [systemd-devel] require=? to prevent premature session termination

Am 05.10.18 um 14:52 schrieb Ralf Sieger: > my service needs to delay the stop of ssh during shutdown. > New ssh connections while my service is still runnign must be accpted, too. >   > So far I was able to postpone the stop of ssh and allow new connections: > [Unit] > BindsTo=ssh.service getty.

Re: [systemd-devel] require=? to prevent premature session termination

Am 05.10.18 um 18:07 schrieb Ralf Sieger: > Hm, according to the docs this is not the case: > "if a unit is configured with |After=| on another unit, the former is > stopped before the latter if both are shut down " > I read this as: > a has After=b > then the start ording should be: > 1. start b

[systemd-devel] why don't "/usr/bin/systemd-run -t" finish within a cronjob anymore?

Fedora 28: root7902 0.0 0.0 75008 3532 ?SN 00:07 0:00 /usr/bin/systemd-run -t -p ProtectSystem=full -p ProtectHome=yes -p PrivateDevices=yes -p PrivateTmp=yes -p NoNewPrivileges=yes --quiet --nice=19 --uid=wwwcron --gid=apache /usr/bin/bash /usr/local/scripts/webalizer.sh

Re: [systemd-devel] Systemd not able to spawn Exec permission denied

Am 07.10.18 um 10:12 schrieb Krunal Patel: > My systemdctl script not able to start service as non root user > sdc. It gives error with not able to spawn /path/to/streamsets : > Permission Denied.   /path/to/streamsets has root ownership and group > streamsets has execute permission as root user.

Re: [systemd-devel] help me

you are simply wrong here and should blame your distribution for such an old systemd which still links to the devel mailing list just because a random service fails in case of "Failed to start Tracker metadata" systemd is only the messenger Am 10.10.18 um 00:33 schrieb g.david...@gmail.com: > sal

Re: [systemd-devel] why don't "/usr/bin/systemd-run -t" finish within a cronjob anymore?

> I am interested in finding out the solution to your problem. > > Have you had any results off-list perhaps because I do not see any > replies to your message. > > Thank you > On Sun, Oct 7, 2018 at 12:26 AM Reindl Harald wrote: >> >> Fedora 28: >> >>

Re: [systemd-devel] Sudo program broken

Am 12.10.18 um 09:40 schrieb Dorian ROSSE: > My sudo program is broken how to repair It ? > > Thank you in advance to answer my problem > > Command line « su » answer « authentification Failure » and command line > « sudo -i » answer « sudo : /usr/bin/sudo must be owned by uid 0 and > have the s

Re: [systemd-devel] Sudo program broken

no sorry > > *De :* systemd-devel de la > part de Reindl Harald > *Envoyé :* vendredi 12 octobre 2018 10:45 > *À :* systemd-devel@lists.freedesktop.org > *Objet :* Re: [systemd-devel] Sudo program broken >   > > Am 12.10.18 u

Re: [systemd-devel] mdadm doesn't works

hell - stop sending every unrelated shit to the systemd-mailing-list this is not your "Dear IT support" Am 13.10.18 um 21:29 schrieb Dorian ROSSE: > #*/systemctl status mdadm/* > > */● mdadm.service/* > > */   Loaded: masked (/dev/null; bad)/* > > */   Active: inactive (dead) > > > /*thank yo

Re: [systemd-devel] dependency-only .service

Am 16.10.18 um 00:09 schrieb Johannes Ernst: > I have several programs A, B and C that, while they are running, require > memcached.service to be running. > When none of A, B, or C is running, I want memcached.service to not run > either. > A, B and C should share the same memcached instance. >

Re: [systemd-devel] Upower service fails to start

Am 16.10.18 um 12:20 schrieb Malcolm White: > I am running openSUSE Tumbleweed with KDE on a x86-64 desktop. The > system was updated (zypper dup) today, but I've been having an issue > with the upower service for a couple of months and have not been able to > discover a resolution amongst the op

Re: [systemd-devel] Upower service fails to start

Am 16.10.18 um 12:43 schrieb Reindl Harald: >> pepper:/usr/lib/systemd # systemctl status upower.service >> ● upower.service - Daemon for power management >>    Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled; >> vendor preset: disabled) >>    Act

[systemd-devel] journald / NFLOG

because Fedora don't provide ulogd or at least it is unmaintrained and iptables "-j LOG" spit to dmesg instead just to the logging system: -j NFLOG --nflog-group 32 --nflog-prefix "Firewall Outbound: " logs to nowhere with out a userspace daemon when you google for systemd /journald and NFLOG you

Re: [systemd-devel] journald / NFLOG

Am 27.10.18 um 20:35 schrieb Mantas Mikulėnas: > On Sat, Oct 27, 2018 at 1:44 AM Reindl Harald <mailto:h.rei...@thelounge.net>> wrote: > > because Fedora don't provide ulogd or at least it is unmaintrained and > iptables "-j LOG" spit to dmes

Re: [systemd-devel] Mailing List List-Id Header

Am 30.10.18 um 16:17 schrieb Esben Stien: > Is there supposed to be a List-Id in the headers of email that comes from > this mailing list? > > I don't see any. Any other headers you use? List-Id: systemd Development Mailing List mostly you looked at one the famous "reply-all" instead "reply-l

Re: [systemd-devel] A question about the race condition between two service

Am 01.11.18 um 09:34 schrieb piliu: > I encounter an issue during the poweroff. In my bash script, firstly I > use poweroff cmd to start systemd-poweroff.service, and use reboot cmd > as a bake up if the poweroff fails. But during tests, many times, the > machine is rebooted directly, without wai

Re: [systemd-devel] Environment-variable security?

Am 12.11.18 um 21:41 schrieb aleivag: > You can define those secrets on /etc/robotsecret.txt, and then on your > unit you do `EnvironmentFile=/etc/robotsecret.txt` > > then you protect /etc/robotsecret.txt as you would normally do and how does that protect anything? on a webserver running php

Re: [systemd-devel] Environment-variable security?

Am 13.11.18 um 18:22 schrieb David Parsley: > You're correct that's not a Unix security standard, and I couldn't find > one - it's just a fairly common practice because environment variables > are easy to use. "common practice" and "easy to use" is in most case sthe opposite of security, even o

Re: [systemd-devel] Environment-variable security?

Am 14.11.18 um 02:17 schrieb Marek Howard: >> It's quite handy way to pass secrets and as I said above, there's >> really no risk if it's done in cases where it makes sense. Of course >> systemd leaking it to everyone makes it not usable with systemd, but >> that's not really a problem with envir

Re: [systemd-devel] Systemd logging..

Am 21.11.18 um 09:53 schrieb deepan muthusamy: > How to log systemd service into log.txt file. > This file should be available after system  restart also. > How to do this? just use rsyslog a all the years before rsyslog.conf: $MainMsgQueueSize 10 $WorkDirectory /var/lib/rsyslog module(load=

Re: [systemd-devel] Systemd logging..

Am 21.11.18 um 15:08 schrieb deepan muthusamy: > Hi, > Still iam not clear about what to do in service. > > Can u please tell me what are all the things I have to add in .service what exactly did you not understand in my repsonse that you need to use rsyslog for traditional logfiles and why do

Re: [systemd-devel] Systemd service consuming 100% cpu

Am 23.11.18 um 14:03 schrieb deepan muthusamy: > If I start my application manually, CPU consumption is less than 2%. > If I start same application as system service, CPU consumption is more > than 100%. > > There is no cout statements in my application.  > > I tried to start under a */screen/*

Re: [systemd-devel] Disable message "A start job is running for myservice"

Am 10.12.18 um 13:47 schrieb Paolo Minazzi: > Dear all, > I'm studying systemd to write a service that start and is executed > before a local-fs.target. > To do my test, I have written a simple service. > > > [Unit] > Description=myservice > DefaultDepende

Re: [systemd-devel] Disable message "A start job is running for myservice"

Am 10.12.18 um 14:09 schrieb Paolo Minazzi: > Il 10/12/2018 14:00, Reindl Harald ha scritto: >> no and this all sounds like seeking a solution for a non existing >> problem! what in the world do you achieve whne your system hangs around >> at boot and don&

Re: [systemd-devel] Systemd dependencies

Am 10.12.18 um 21:26 schrieb Boyce, Kevin P [US] (AS): > I seem to be struggling with what should be a very basic operation.  > I’ve seen similar questions posted to the list here and none of them are > really adequate. > > I’m trying to prompt the user to ask a question as the system is coming

Re: [systemd-devel] EXT :Re: Systemd dependencies

Am 10.12.18 um 22:06 schrieb Boyce, Kevin P [US] (AS): > I'm sure Redhat has implemented some services of type Simple. > > However, my service is oneshot, and what you're saying is there's no way for > me to force any other service to wait until my service exits before bootup > continues? Typ

[systemd-devel] IPAddressDeny/IPAddressAllow is too limited ot be useful

http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html "All traffic from and to this address will be prohibited for processes of the service" is nice in theory but let's say we have a internal webserver which needs to make curl calls to the internet IPAddressDeny=any IPAddressA

Re: [systemd-devel] Suspend issues

Am 24.12.18 um 18:53 schrieb Pratyush Das: > OS - Gentoo > Kernel - 4.14.83-gentoo > My laptop is an optimus laptop if that is relevant. > > Configuration- > reik@localhost ~ $ systemctl --version > systemd 239 > +PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP > -LIBCRYPTSETUP +GCRYPT

Re: [systemd-devel] IPAddressDeny/IPAddressAllow is too limited ot be useful

Am 27.12.18 um 12:38 schrieb Lennart Poettering: > On So, 23.12.18 02:17, Reindl Harald (h.rei...@thelounge.net) wrote: > >> http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html >> >> "All traffic from and to this address will be prohibited fo

Re: [systemd-devel] Requires and After

Am 01.01.19 um 12:44 schrieb Jérémy Rosen: > The short answer is that Requires without after makes little sense, > since you can't reliably know if your dependency is here without it > (if it fails at startup, you might or might not be started, depending > on the startup order systemd chooses) >

Re: [systemd-devel] Requires and After

Am 01.01.19 um 20:24 schrieb Tomasz Torcz: > On Tue, Jan 01, 2019 at 08:20:19PM +0100, Olaf van der Spek wrote: >> On Tue, Jan 1, 2019 at 8:17 PM Ian Pilcher wrote: >>> >>> On 1/1/19 5:44 AM, Jérémy Rosen wrote: The short answer is that Requires without after makes little sense, since

Re: [systemd-devel] Requires and After

Am 02.01.19 um 04:13 schrieb James Feeney: >> It's about Requires and After. I think a unit in Requires should imply >> that unit in After too, otherwise the requirement isn't really met. >> Is there a use case for Requires but not After? > > Olaf, previously, on GitHub, you had said: > >>> I t

Re: [systemd-devel] Requires and After

Am 02.01.19 um 05:22 schrieb James Feeney: > On 1/1/19 8:33 PM, Reindl Harald wrote: >> "After" is a soft dependency, if that unit isn't enabled or don#t exist >> at all it don't matter >> >> "Requires" is a hard dependency and it makes no

Re: [systemd-devel] Requires and After

Am 02.01.19 um 09:14 schrieb Michael Chapman: > I have two services on my system, A.service and B.service, where A.service > Wants=B.service but is ordered Before=B.service. The reason for this is > that when I start A I want B to be automatically started too, but B cannot > function without A

Re: [systemd-devel] .service and .socket

Am 02.01.19 um 11:05 schrieb Lennart Poettering: > On Di, 01.01.19 13:46, Olaf van der Spek (m...@vdspek.org) wrote: >> AFAIK socket units require a separate file, which seems more complex >> then it has to be. > > The main reason why socket and service units are separate is that this > way they

Re: [systemd-devel] .service and .socket

Am 02.01.19 um 11:49 schrieb Michael Chapman: > On Wed, 2 Jan 2019, Reindl Harald wrote: > [...] >> agreed, but why can't have socket simply optional a [Service] section to >> save the "demo@.service" in cases like below? >> >> [root@client:/

Re: [systemd-devel] Crash with extra space after Exec prefix

Am 13.05.2015 um 19:11 schrieb Martin Pitt: Lennart Poettering [2015-05-13 17:55 +0200]: On Wed, 13.05.15 17:01, Martin Pitt (martin.p...@ubuntu.com) wrote: So, obviously we need to fix the crash; but I was wondering what the desired behaviour should be? In the sense of "be liberal what you a

Re: [systemd-devel] Automatic user ACL management

Am 17.05.2015 um 12:46 schrieb Mikhail Morfikov: Is that possible? I'm asking because I often listen to the music and I don't really need my monitor to be on most of the time, so I just lock the screen. But when I lock the screen, the active session becomes inactive and amarok stops playing. An

Re: [systemd-devel] Automatic user ACL management

Am 17.05.2015 um 14:20 schrieb Mikhail Morfikov: On Sun, 17 May 2015 12:55:18 +0200 Reindl Harald wrote: Am 17.05.2015 um 12:46 schrieb Mikhail Morfikov: Is that possible? I'm asking because I often listen to the music and I don't really need my monitor to be on most of the time,

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Am 26.05.2015 um 16:17 schrieb Lennart Poettering: On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Or will there be a v220.1 release shortly with releasy fix-ups? Well, we don't do point releases in systemd. and why? just "because don't do" is not enough

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Am 26.05.2015 um 17:29 schrieb Lennart Poettering: On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote: which shows that a important project like systemd playing on the same level as the linux kernel *just needs* point releases, there is a reason that the kernel has point

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Am 26.05.2015 um 18:22 schrieb Lennart Poettering: On Tue, 26.05.15 17:57, Reindl Harald (h.rei...@thelounge.net) wrote: Am 26.05.2015 um 17:29 schrieb Lennart Poettering: On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote: which shows that a important project like systemd

Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]

Am 27.05.2015 um 23:03 schrieb Roger Binns: My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't) sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1217969 signature.asc Description: OpenPGP digit

Re: [systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]

Am 28.05.2015 um 07:24 schrieb Martin Pitt: Reindl Harald [2015-05-28 1:00 +0200]: Am 27.05.2015 um 23:03 schrieb Roger Binns: My immediate problem is a boot failure with systemd on Ubuntu 15.04 because of fsck issues (systemd timing out fscking something it shouldn't) sounds like

Re: [systemd-devel] Why we need to read/save random seed?

Am 17.06.2015 um 05:06 schrieb cee1: 2015-06-16 0:21 GMT+08:00 Lennart Poettering : On Mon, 15.06.15 23:33, cee1 (fykc...@gmail.com) wrote: Hi, I maybe got confused. First, systemd-random-seed.service will save a "seed" from /dev/urandom when shutdown, and load that "seed" to /dev/urandom wh

Re: [systemd-devel] Why we need to read/save random seed?

Am 17.06.2015 um 14:21 schrieb cee1: 2015-06-17 16:40 GMT+08:00 Reindl Harald : systemd-random-seed.service will load the "seed on disk" to /dev/urandom, and save a "seed" to disk when shutdown, right? The article at http://www.2uo.de/myths-about-urandom/ suggests us sav

Re: [systemd-devel] Why we need to read/save random seed?

Am 17.06.2015 um 14:51 schrieb Kay Sievers: On Wed, Jun 17, 2015 at 2:28 PM, Reindl Harald wrote: Am 17.06.2015 um 14:21 schrieb cee1: 2015-06-17 16:40 GMT+08:00 Reindl Harald : systemd-random-seed.service will load the "seed on disk" to /dev/urandom, and save a "see

Re: [systemd-devel] Why we need to read/save random seed?

Am 17.06.2015 um 17:08 schrieb cee1: 2015-06-17 22:03 GMT+08:00 Lennart Poettering : On Wed, 17.06.15 20:21, cee1 (fykc...@gmail.com) wrote: What I means is: 1. Load a saved seed to /dev/urandom. 2. The service read /dev/random, which will block until kernel thinks there's enough entropy - t

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

Am 19.06.2015 um 16:06 schrieb Lennart Poettering: * If there's a systemd unit and a SysV init script for the same service name, and the user executes "systemctl enable" for it (or a related call), then this will now enable both (or execute the related

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

Am 19.06.2015 um 16:32 schrieb Lennart Poettering: On Fri, 19.06.15 16:15, Reindl Harald (h.rei...@thelounge.net) wrote: Am 19.06.2015 um 16:06 schrieb Lennart Poettering: * If there's a systemd unit and a SysV init script for the same service name, and the user exe

Re: [systemd-devel] How to get used to systemd vs init

Am 23.06.2015 um 21:45 schrieb Chad: The new systemd way would be to type (23 total characters, no tab complete): systemctl restart httpd Maybe I could tab complete systemctl, but I don't currently have a CentOS 7 system to test on. maybe you should just install CentOS inside a VM and test it

Re: [systemd-devel] How to get used to systemd vs init

Am 24.06.2015 um 01:07 schrieb Chad: You could do something like: systemctl start htt systemctl st or else, and it will complete it. I use bash. This is a cool trick that systemd has over init.d. I know not all programs can do that shell completion, for example /etc/init.d/httpd res does not

Re: [systemd-devel] howto handle one time shutdown programs

Am 26.06.2015 um 09:31 schrieb Andrei Borzenkov: How is that different from the user executing: systemctl start your.service systemctl stop your.service systemctl start your.service without reboot? Those initscripts I am aware of avoided this issue by not stopping anything on restart the

Re: [systemd-devel] Question about ExecStartPost= and startup process

Am 28.06.2015 um 12:00 schrieb Francis Moreau: Hello, For services with Type=Forking, I'm wondering if systemd proceeds starting follow-up units when the command described by ExecStart= exits or when the one described by ExecStartPost= exits ? I tried to read the source code to figure this o

Re: [systemd-devel] Question about ExecStartPost= and startup process

Am 28.06.2015 um 19:02 schrieb Francis Moreau: On 06/28/2015 01:01 PM, Reindl Harald wrote: Am 28.06.2015 um 12:00 schrieb Francis Moreau: Hello, For services with Type=Forking, I'm wondering if systemd proceeds starting follow-up units when the command described by ExecStart= exi

Re: [systemd-devel] SysVInit service migration to systemd

Am 29.06.2015 um 15:58 schrieb Lesley Kimmel: Jonathan; Thanks for the background and information. Since you clearly seem to have a grasp of systemd please humour me with a few more questions (some of them slightly ignorant): a) Why are PID bad? what are they good for when the supervisor kn

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

Am 29.06.2015 um 21:36 schrieb jon: On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote: On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote: Reversing the logic by adding a "mustexist" fstab option and keeping the default behaviour would fix it. At this time, systemd has been

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

Am 29.06.2015 um 17:01 schrieb jon: On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote: On 06/29/2015 02:08 PM, jon wrote: https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system I just installed debian 8.1, on the who

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

Am 29.06.2015 um 18:50 schrieb jon: On Mon, 2015-06-29 at 17:54 +0200, Reindl Harald wrote: Am 29.06.2015 um 17:01 schrieb jon: On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote: On 06/29/2015 02:08 PM, jon wrote: https://www.debian.org/releases/stable/amd64/release-notes/ch

<    1   2   3   4   5   6   7   8   9   10   >