Re: [systemd-devel] Disabling tomcat8

Am 19.12.2017 um 20:05 schrieb Lennart Poettering: On Mo, 18.12.17 19:40, Cecil Westerhof (cldwester...@gmail.com) wrote: There is a system with tomcat8 installed and enabled. At the moment it is not used, so I thought it better to disable it. When I enter: systemctl disable

Re: [systemd-devel] Default reply to the mailing-list instead of sender

Am 19.12.2017 um 12:43 schrieb Michael Chapman: On Tue, 19 Dec 2017, Cecil Westerhof wrote: With most mailing-lists when replying with GMail a reply is default send to the mailing-list, but with this mailing-list it is default send to the sender. Would it be possible to change this? Just

Re: [systemd-devel] Default reply to the mailing-list instead of sender

Am 19.12.2017 um 12:41 schrieb Lennart Poettering: On Di, 19.12.17 10:30, Cecil Westerhof (cldwester...@gmail.com) wrote: With most mailing-lists when replying with GMail a reply is default send to the mailing-list, but with this mailing-list it is default send to the sender. Would it be

Re: [systemd-devel] Disabling tomcat8

Am 18.12.2017 um 19:40 schrieb Cecil Westerhof:     tomcat8.service is not a native service, redirecting to systemd-sysv-install.     Executing: /lib/systemd/systemd-sysv-install disable tomcat8 Other services I can enable and disable. I can stop (and start) tomcat 8, but then I always

Re: [systemd-devel] journald: why become tabs to #011

Am 25.11.2017 um 15:33 schrieb Reindl Harald: thanks https://bugzilla.redhat.com/show_bug.cgi?id=1517455 however journalctl isn't that smart either: Dez 11 10:57:17 srv-rhsoft.rhsoft.net php[22523]: [19B blob data] /var/log/messages: Dec 11 10:57:17 srv-rhsoft php[22523]: 1#0112#011#003

Re: [systemd-devel] Is this list still active? Where can I get basic help with systemd

Am 05.12.2017 um 19:04 schrieb Doug Snyder: At this point two people have said I have an updated systemd which is strange because I thought I used the latest CentOS minimal install $ systemctl --version systemd 219 +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP

Re: [systemd-devel] Question about service dependency handling in systemd-228

to fi them IMHO it would be justified not to boot at all if there is as example a unit which has itself in After/Before/Requires as example when someone don't read his systemlogs after change units and "systemctl daemon-reload" :-) On Sun, Nov 26, 2017 at 4:53 PM, Reindl Har

Re: [systemd-devel] Question about service dependency handling in systemd-228

Am 26.11.2017 um 10:47 schrieb Bao Nguyen: Regard to your question, "asi-My-5101.socket" depends on "My-sshd.target", I think that in my case it is expected as my socket listens on a specific address IP:port so it should start after a network service to configure and assign IP address before

Re: [systemd-devel] Question

Am 25.11.2017 um 16:24 schrieb Peter Diks: Hello Systemd-devel@lists.freedesktop.org , There is something i do not understand at this point and would like to solve it. A brand new Tumbleweed Kubic, has enable repositories and zypper runs fine,

Re: [systemd-devel] journald: why become tabs to #011

;, iov_len=8096}], msg_iovlen=1, msg_control=[...], msg_controllen=64, msg_flags=0}, MSG_DONTWAIT) = 45 [pid  3351] write(17, "Nov 25 14:20:45 virgule grawity: foo bar#011baz#012quux\n", 56) = 56 On Sat, Nov 25, 2017 at 3:39 PM, Reindl Harald <h.rei...@thelounge.net <mailt

[systemd-devel] journald: why become tabs to #011

this is terrible ugly and it makes little sense - in doubt please convert that to a space and not #011 Nov 25 05:45:02 testserver php[16259]: 2017-11-25 04:45:02 [notice] Daily renewal check started Nov 25 06:30:02 testserver php[16680]: 2017-25-11 06:30:02#011/cms/temp/ecparams.pem#0110,10

Re: [systemd-devel] [systemd memory-leak] leak in systemd version 195

Am 23.11.2017 um 17:30 schrieb Shekhar arya: I am using systemd v195 didn't you find any older version? even CentOS7 has v219 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] How to run forking daemon with systemd in correct way, without errors?

Am 23.11.2017 um 11:40 schrieb Gena Makhomed: On 23.11.2017 2:30, Reindl Harald wrote: i know that all, httpd and postfix are typically forking services and are working fine without any PID file since 2011 # grep PIDFile /usr/lib/systemd/system/postfix.service PIDFile=/var/spool/postfix/pid

Re: [systemd-devel] How to run forking daemon with systemd in correct way, without errors?

Am 23.11.2017 um 10:32 schrieb Gena Makhomed: On 23.11.2017 7:45, Mantas Mikulėnas wrote: This is bug in nginx code? And this bug should be fixed in nginx? But "daemon(); write_pidfile();" is common pattern used by many services and even in library functions. It may be common, but not

Re: [systemd-devel] How to run forking daemon with systemd in correct way, without errors?

Am 23.11.2017 um 00:38 schrieb Gena Makhomed: On 23.11.2017 0:29, Reindl Harald wrote: or just remove the pid-file stuff from the systemd-unit, systemd don't need it really pid-file need for service reload and service stop nonsense You are talking about GuessMainPID= option? https

Re: [systemd-devel] How to run forking daemon with systemd in correct way, without errors?

Am 22.11.2017 um 23:02 schrieb Gena Makhomed: On 22.11.2017 23:27, Reindl Harald wrote: or just remove the pid-file stuff from the systemd-unit, systemd don't need it really pid-file need for service reload and service stop nonsense - if maintain a ton of production servers from web/proxy

Re: [systemd-devel] How to run forking daemon with systemd in correct way, without errors?

Am 22.11.2017 um 21:37 schrieb Gena Makhomed: I am use nginx web server (http://nginx.org/) with systemd. But I see errors in /var/log/messages when running nginx: systemd: Starting nginx - high performance web server... systemd: Failed to read PID from file /var/run/nginx.pid: Invalid

Re: [systemd-devel] How to disable systemd multiseat feature?

Am 14.11.2017 um 05:26 schrieb Farhad Mohammadi Majd: Thanks for answer Mr. Lennart, I thought GDM is always active due to systemd, because in Wikipedia it is written in GNOME article that: "Since GNOME 3.2 multiseat support has been only available on systems using systemd." so I thought it

Re: [systemd-devel] Getting timesync on RO fs

Am 05.11.2017 um 16:41 schrieb Rémi Pincent: Since systemd 235, timesyncd stamp file has been moved to /var/lib/systemd/timesync/clock . As my /var partition is RO is created a symlink to a clock file located in a RW partition, I got this error : /Nov 05 16:05:44 rpi-home-master

Re: [systemd-devel] one shot service exit-code

Am 31.10.2017 um 17:26 schrieb Matt Zagrabelny: On Tue, Oct 31, 2017 at 11:21 AM, Reindl Harald <h.rei...@thelounge.net <mailto:h.rei...@thelounge.net>> wrote: Am 31.10.2017 um 17:06 schrieb Matt Zagrabelny: I have phone that I plug into my computer and have

Re: [systemd-devel] one shot service exit-code

Am 31.10.2017 um 17:06 schrieb Matt Zagrabelny: I have phone that I plug into my computer and have a udev rule to fire off a systemd service. Things work well, but the journal indicates that the command isn't terminating cleanly. However here is the journal when I plug in the phone: Oct 31

Re: [systemd-devel] nginx won't restart

Am 30.10.2017 um 18:38 schrieb Pat Bell: I stopped nginx and then restarted too quickly (or so the logs tell me). But now it still won't start WHat now? this is *not* a systemd problem and the support url was always wrong and removed long ago

Re: [systemd-devel] 回复： 回复： 回复： [systemd-de vel] systemctl can't execute stop actually,whenservice is started by other way

Am 27.10.2017 um 12:25 schrieb 清辰: When executing 'service xxx restart', actually systemd will execute 'service xxx start', and then 'service xxx stop'. But my restart action is different from stop action, can I customize my 'restart'? no - fix the service this sounds somehow as you have

Re: [systemd-devel] 回复： 回复： [systemd-de vel] systemctl can't execute stop actually,whenservice is started by other way

Am 27.10.2017 um 11:53 schrieb 清辰: Where is the 'service xxx status' result stored? Or can I change the service status manually, when start / stop the service outside of systemd just don't start it outside systemd - yes it's really that easy ___

Re: [systemd-devel] systemd vs udev automount

Am 09.10.2017 um 20:00 schrieb Paul D. DeRocco: From: Mantas Mikulenas [mailto:graw...@gmail.com] Just configure "/dev/disk/by-label/FOOBAR" (or possibly "LABEL=FOOBAR") as the mount source. Duh. I never noticed LABEL in the fstab man page. Pretty simple. Thanks LABEL was used for many

Re: [systemd-devel] code=exited, status=226/NAMESPACE

nevermind, it's still https://bugzilla.redhat.com/show_bug.cgi?id=131 because systemd in Fedora is abandonware and /home is on that VM a symlink to the storage-lvm Am 30.09.2017 um 02:41 schrieb Reindl Harald: OS: Fedora 25 Vesion: systemd-231-17.fc25.x86_64 Kernel: 4.12.14-200.fc25

Re: [systemd-devel] SystemCallFilter=~@resources broken in F26/systemd233

Am 30.09.2017 um 14:38 schrieb Lennart Poettering: On Sa, 23.09.17 15:38, Reindl Harald (h.rei...@thelounge.net) wrote: with Fedroa 25 that was no problem, on F26 httpd, mysqld and so on are breaking [root@testserver:~]$ rpm -q systemd systemd-233-6.fc26.x86_64 [root@testserver:~]$ rpm -q

[systemd-devel] code=exited, status=226/NAMESPACE

OS: Fedora 25 Vesion: systemd-231-17.fc25.x86_64 Kernel: 4.12.14-200.fc25.x86_64 what the hell is that? shortly after reboot "systemctl status" says "running" but nothing in /var/log/messages (yes many people don't linke journalctl) [root@fileserver:~]$ systemctl status rsyslog ?

[systemd-devel] SystemCallFilter=~@resources broken in F26/systemd233

with Fedroa 25 that was no problem, on F26 httpd, mysqld and so on are breaking [root@testserver:~]$ rpm -q systemd systemd-233-6.fc26.x86_64 [root@testserver:~]$ rpm -q glibc glibc-2.25-10.fc26.x86_64 @resourcesSystem calls for changing resource limits, memory and scheduling parameters

Re: [systemd-devel] Unsubcribe

Am 07.09.2017 um 19:59 schrieb garyevansbtc: Please unsubribe this email from the mailing list. Recipient is decreased for you and any other person who considers unsubcribe: do you think the link https://lists.freedesktop.org/mailman/listinfo/systemd-devel is there just for fun in the

Re: [systemd-devel] Reliable way to finish system units before termination through systemd shutdown / reboot routines

Am 02.09.2017 um 17:11 schrieb Andrei Borzenkov: 15.08.2017 17:25, Reiner Wenke пишет: Hello, I have running some virtualbox instances under systemd control and use vboxautostart-service for starting and stopping (saving). This is running on Centos7 As long as I use systemctl stop

Re: [systemd-devel] Formatting Execstart= for readability

Am 16.08.2017 um 12:04 schrieb Mantas Mikulėnas: On Wed, Aug 16, 2017 at 12:09 PM, Reindl Harald <h.rei...@thelounge.net <mailto:h.rei...@thelounge.net>> wrote: Am 16.08.2017 um 10:31 schrieb Mantas Mikulėnas: Just put everything in a shell script. (That way

Re: [systemd-devel] Formatting Execstart= for readability

Am 16.08.2017 um 10:31 schrieb Mantas Mikulėnas: Just put everything in a shell script. (That way you can test it directly without systemd, too.) With bash, you can use inline comments in arrays: #!/usr/bin/env bash args=( -X POST # foo -d

Re: [systemd-devel] Reliable way to finish system units before termination through systemd shutdown / reboot routines

Am 15.08.2017 um 16:25 schrieb Reiner Wenke: I have running some virtualbox instances under systemd control and use vboxautostart-service for starting and stopping (saving). This is running on Centos7 As long as I use systemctl stop vboxautostart-service for termination, everything is fine,

Re: [systemd-devel] type=notify not working as intended

Am 15.08.2017 um 05:59 schrieb Kalpa Gunarathna: Hello all, I have scripted a service unit as follow. [Unit] Description="A test service" After=epmd.service epmd.socket [Service] ExecStart=/home/otpuser/bin/start Type=notify NotifyAccess=all WorkingDirectory=~ User=otpuser Group=otp

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

Am 14.08.2017 um 12:31 schrieb Sergei Franco: Admins expect output when starting and stopping services admins should learn to deal with their system This is even more important when there are runbooks and other processes involved. The journalctl output is very messy (because it is a log).

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

Am 11.08.2017 um 04:29 schrieb Sergei Franco: I am trying to retain behaviour of the startup scripts the same as sysvinit. For example, on sysv the script outputs feedback to the console when the stopping and starting is done via console. With systemd all output is "hidden", and to see the

Re: [systemd-devel] Systemd weird behavior after upgrade -

Am 13.07.2017 um 23:40 schrieb arnaud gaboury: (no HTML crapps) still HTML and no meaningful quoting to distinct your "i respond to myself" answer with your initial post - no idea what you expect by sending a bunch of mails with the same content within a few hours nor why you think it's a

Re: [systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

Am 12.07.2017 um 10:23 schrieb Lennart Poettering: On Wed, 12.07.17 09:51, Florian Weimer (f...@deneb.enyo.de) wrote: Fork detection using getpid is not reliable. It gives false negatives in the case of double-forks, where the process can be different but the PID is the same due to reuse.

Re: [systemd-devel] Github systemd issue 6237

Am 10.07.2017 um 12:42 schrieb Lennart Poettering: (I do accept though that it's a valid discussion whether systemd's current behaviour of warning and skipping invalid User= rvalues is the best choice, instead of erroring out completely.) and *that* is the real point of the whole issue - if

Re: [systemd-devel] Github systemd issue 6237

Am 10.07.2017 um 12:55 schrieb Lennart Poettering: On Thu, 06.07.17 10:34, Reindl Harald (h.rei...@thelounge.net) wrote: Am 06.07.2017 um 09:59 schrieb Jonathan de Boyne Pollard: Reindl Harald: > at least fall back to “nobody” Jonathan de Boyne Pollard: > That idea is

Re: [systemd-devel] Is there a reason to run systemd Units with root access?

Am 10.07.2017 um 10:49 schrieb Lennart Poettering: On Tue, 04.07.17 20:33, Mariusz Wojcik (m6woj...@outlook.com) wrote: Hi, I’m just asking because of the latest “not-a-bug” [1]. As far as I know, there aren’t many services that need full root access (maybe for getting a low port number).

Re: [systemd-devel] Github systemd issue 6237

Am 08.07.2017 um 08:29 schrieb Michael Chapman: On Sat, 8 Jul 2017, Kai Krakow wrote: Am Sat, 8 Jul 2017 08:05:44 +0200 schrieb Kai Krakow : Am Sat, 8 Jul 2017 11:39:02 +1000 (AEST) schrieb Michael Chapman : On Sat, 8 Jul 2017, Kai Krakow

Re: [systemd-devel] Github systemd issue 6237

Am 07.07.2017 um 21:55 schrieb Kai Krakow: Am Tue, 4 Jul 2017 21:23:01 + (UTC) schrieb Alexander Bisogiannis : On Tue, 04 Jul 2017 17:21:01 +, Zbigniew Jędrzejewski-Szmek wrote: If you need root permissions to create a unit, then it's not a security issue. An

Re: [systemd-devel] Is there a reason to run systemd Units with root access?

Am 04.07.2017 um 22:33 schrieb Mariusz Wojcik: I’m just asking because of the latest “not-a-bug” [1]. As far as I know, there aren’t many services that need full root access (maybe for getting a low port number). Except for that I don’t see many use cases. Therefore, I think it would be

Re: [systemd-devel] Github systemd issue 6237

Am 06.07.2017 um 09:59 schrieb Jonathan de Boyne Pollard: Reindl Harald: > at least fall back to “nobody” Jonathan de Boyne Pollard: > That idea is wrong. > > https://news.ycombinator.com/item?id=14681377#14682059 Reindl Harald: > better than a stupid [...] Not re

Re: [systemd-devel] Github systemd issue 6237

Am 06.07.2017 um 01:36 schrieb Michael Chapman: Note that the semantic validations you're talking about here -- things like "does the user exist?" -- are _not_ preemptive. They are fatal: the child process will exit unsuccessfully as the command is executed if the settings will not be able

Re: [systemd-devel] Github systemd issue 6237

Am 05.07.2017 um 20:34 schrieb Jonathan de Boyne Pollard: Reindl Harald: at least fall back to "nobody" That idea is wrong. https://news.ycombinator.com/item?id=14681377#14682059 better than a stupid "i fall back to root because i think i make the rules and not the under

Re: [systemd-devel] Bouncing interface once chrony is synced

Am 05.07.2017 um 17:29 schrieb Ian Pilcher: I am using CentOS 7 (systemd 219) on a Banana Pi as my residential firewall/gateway. The Banana Pi does not have a persistent clock, so it has no idea what the time is until it is able to sync via NTP. Thus, the initial DHCP leases that the BPi

Re: [systemd-devel] Github systemd issue 6237

Am 05.07.2017 um 12:32 schrieb Michael Chapman: In Wed, 5 Jul 2017, Reindl Harald wrote: The issue being discussed here is that systemd considers "0day" to be _syntactically_ invalid for a username. See the valid_user_group_name() function in basic/user-util.c. yes and hence

Re: [systemd-devel] Github systemd issue 6237

Am 05.07.2017 um 12:10 schrieb Michael Chapman: On Wed, 5 Jul 2017, Colin Guthrie wrote: Reindl Harald wrote on 04/07/17 19:50: When new configuration options are added, the same unit file can almost always be used with older systemd, and it'll just warn & ignore the parts it doe

Re: [systemd-devel] Github systemd issue 6237

Am 04.07.2017 um 20:39 schrieb Zbigniew Jędrzejewski-Szmek: On Tue, Jul 04, 2017 at 07:36:02PM +0200, Reindl Harald wrote: Am 04.07.2017 um 19:21 schrieb Zbigniew Jędrzejewski-Szmek: My question is: Is this a bug with a BZ against rhel/centos7 (as my understanding is that this affects EL7

Re: [systemd-devel] Github systemd issue 6237

Am 04.07.2017 um 19:21 schrieb Zbigniew Jędrzejewski-Szmek: My question is: Is this a bug with a BZ against rhel/centos7 (as my understanding is that this affects EL7 too)? If there is no BZ and based on the wording of the second to last comment by poettering, will this be fixed/changed in a

Re: [systemd-devel] horrible outout - failed at step NAMESPACE spawning

Am 03.07.2017 um 16:20 schrieb Lennart Poettering: On Mon, 03.07.17 16:12, Reindl Harald (h.rei...@thelounge.net) wrote: Am 03.07.2017 um 15:59 schrieb Lennart Poettering: On Mon, 03.07.17 15:53, Reindl Harald (h.rei...@thelounge.net) wrote: Jul 3 15:48:01 backup-arrakis systemd

Re: [systemd-devel] horrible outout - failed at step NAMESPACE spawning

Am 03.07.2017 um 15:59 schrieb Lennart Poettering: On Mon, 03.07.17 15:53, Reindl Harald (h.rei...@thelounge.net) wrote: Jul 3 15:48:01 backup-arrakis systemd: named.service: Failed at step NAMESPACE spawning /usr/libexec/setup-named-chroot.sh: No such file or directory by all repsect

[systemd-devel] horrible outout - failed at step NAMESPACE spawning

Jul 3 15:48:01 backup-arrakis systemd: named.service: Failed at step NAMESPACE spawning /usr/libexec/setup-named-chroot.sh: No such file or directory by all repsect, this output is completly nonsense when the reason is some "InaccessibleDirectories" no longer exists and is not prefixed with

Re: [systemd-devel] 回复： 回复： [systemd-de vel] systemctl can't execute stop actually,whenservice is started by other way

Am 29.06.2017 um 11:51 schrieb Oliver Neukum: Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald: Am 29.06.2017 um 10:05 schrieb Oliver Neukum: Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering: Well, it's a service manager. As such it keeps track

Re: [systemd-devel] 回复： 回复： [systemd-de vel] systemctl can't execute stop actually,whenservice is started by other way

Am 29.06.2017 um 10:05 schrieb Oliver Neukum: Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering: Well, it's a service manager. As such it keeps track of services, knows when they are started and when they aren't. Why would it stop services that aren't started? Because you

Re: [systemd-devel] About stable network interface names

Am 29.05.2017 um 11:40 schrieb Lennart Poettering: Well, different naming strategies have different advantages and disadvantages. If you use the MAC address, then replacing hardware becomes harder, and you can't cover hardware that doesn't have fixed MAC addresses (or VMs) than KVM or

Re: [systemd-devel] [Debate] Transition from professional to popular?

Am 11.05.2017 um 21:50 schrieb e...@a6.25u.com: On 05/11/17 21:40, Lennart Poettering wrote: On Thu, 11.05.17 21:24, e...@a6.25u.com (e...@a6.25u.com) wrote: Operating systems (that might use the Linux kernel) are being streamlined from being professional into being popular. systemd is a

Re: [systemd-devel] monitoring systemd unit flapping

Am 25.04.2017 um 17:30 schrieb Jeremy Eder: If we have a service that is flapping because it's crashing after startup...what's the right way to monitor for that condition? Eventually it triggers startburstlimit, was thinking that if we hit startburstlimit that the service could set some

Re: [systemd-devel] systemd integration

14∶52 +0200, użytkownik Reindl Harald napisał: Am 22.04.2017 um 13:28 schrieb John Doe: Free and Open-Source (FOSS <http://en.wikipedia.org/wiki/Free_and_open-source_software>) operating systems without systemd http://without-systemd.org/wiki/index.php/Main_Page and who cares

Re: [systemd-devel] systemd integration

Am 22.04.2017 um 13:28 schrieb John Doe: Free and Open-Source (FOSS ) operating systems without systemd http://without-systemd.org/wiki/index.php/Main_Page and who cares about the "i love my decades old mess of

Re: [systemd-devel] what is sd_notify() really for ?

Am 17.04.2017 um 00:47 schrieb Enrico Weigelt, metux IT consult: On 17.04.2017 00:04, Lennart Poettering wrote: Please always check the man pages if you have questions regarding a specific systemd interface: https://www.freedesktop.org/software/systemd/man/sd_notify.html Done so, of

Re: [systemd-devel] My experience with MySQL and systemctl

Am 13.04.2017 um 06:06 schrieb Andrei Borzenkov: Maybe we'd need a new state paramenter, like STARTING=1 which could be sent by the daemon to systemd in regular intervals and would signal systemd that the startup of the daemon is in process and the daemon is not actually hung. You still need

Re: [systemd-devel] Add DATADOS, fat32 to fstab file

Am 06.04.2017 um 22:15 schrieb Gary Evans: I tried to copy UUID=B813-BB28 /boot/efi vfat umask=0077 0 1 for my DOS data partition but it caused Debian not to boot. This is how it's configured: UUID=202E-E8BE /DATADOS vfat umask=0077 0 1 Where did this go awry? Please help.

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

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

Re: [systemd-devel] F25: NAMESPACE spawning: Too many levels of symbolic links

Am 16.03.2017 um 18:21 schrieb Michal Sekletar: On Thu, Mar 16, 2017 at 4:29 PM, Reindl Harald <h.rei...@thelounge.net> wrote: with systemd-229-18.fc24.x86_64 no problem at all - after upgrade to F25 "/usr/bin/vmware-networks" while this is just a phyiscal file and was not t

Re: [systemd-devel] F25: NAMESPACE spawning: Too many levels of symbolic links

Am 16.03.2017 um 16:29 schrieb Reindl Harald: with systemd-229-18.fc24.x86_64 no problem at all - after upgrade to F25 "/usr/bin/vmware-networks" while this is just a phyiscal file and was not touched [root@rh:~]$ rpm -q systemd systemd-231-14.fc25.x86_64 Mar 16 16:25:23 rh systemd

[systemd-devel] F25: NAMESPACE spawning: Too many levels of symbolic links

with systemd-229-18.fc24.x86_64 no problem at all - after upgrade to F25 "/usr/bin/vmware-networks" while this is just a phyiscal file and was not touched [root@rh:~]$ rpm -q systemd systemd-231-14.fc25.x86_64 Mar 16 16:25:23 rh systemd: vmware-vmnet.service: Failed at step NAMESPACE

Re: [systemd-devel] how make systemd NOT to clutter dmesg?

Am 27.02.2017 um 17:18 schrieb lejeczek: yes, correct, something did, in /etc/grub2.cfg systemd.log_level=debug systemd.log_target=kmsg even tough nothing of above is to be found in /etc/default/grub What I found and messaged Centos list about, long agao, but it might be interesting to

Re: [systemd-devel] how make systemd NOT to clutter dmesg?

Am 27.02.2017 um 12:11 schrieb Tomasz Torcz: On Mon, Feb 27, 2017 at 11:03:09AM +, lejeczek wrote: On 27/02/17 10:10, Reindl Harald wrote: Am 27.02.2017 um 10:55 schrieb lejeczek: hi there I'm trying to solve problem which to you guys must be trivial, but it's a puzzle to me. I've

Re: [systemd-devel] how make systemd NOT to clutter dmesg?

Am 27.02.2017 um 10:55 schrieb lejeczek: hi there I'm trying to solve problem which to you guys must be trivial, but it's a puzzle to me. I've searched the net & man pages but ... failed to find how/where systemd is told to put stuff like: Got message type... seriously - could you at least

Re: [systemd-devel] [networkd] Mixing DHCP & static IPs on 1 interface

please keep repsonses on the list Am 22.02.2017 um 15:42 schrieb Ian Pilcher: On 02/21/2017 08:28 PM, Reindl Harald wrote: since this should be all on the LAN side something is *very* unusual on your setup - the firewall i setup at office is just a virtual machine with a single NIC

Re: [systemd-devel] [networkd] Mixing DHCP & static IPs on 1 interface

Am 22.02.2017 um 01:30 schrieb Ian Pilcher: I'm trying to find a way to do this with systemd-networkd. The reason is that my cable modem listens on a 192.168.X.X address. Normally this "just works". My firewall tries to send traffic destined for this address to my ISP's router, and the cable

Re: [systemd-devel] Log output is incomplete or unavailable

Am 20.02.2017 um 22:00 schrieb Patrick B: I'm running Ubuntu 16.04.01 Server and just realised some log files are not being created. Such as: /var/log/kern.log /var/log/postgresql/postgresql.log this is really not a upstream question- maybe your distribution just don#t install

Re: [systemd-devel] Adding "After=network-online.target" via drop-in

Am 19.02.2017 um 13:34 schrieb Mantas Mikulėnas: On Sat, Feb 18, 2017 at 10:32 PM, Ian Pilcher > wrote: I have configured sshd on my firewall to listen only on its internal IP address. This is causing it to fail when it first starts,

Re: [systemd-devel] Start a global service

Am 15.02.2017 um 18:53 schrieb Damien Robert: Lennart Poettering wrote in message <20170215172159.GA10587@gardel-login>: Sorry, but this is unlikely to be added. I understand that this would be handy, but this is semantically very questionable, as this would be transition from privileged

Re: [systemd-devel] systemd-networkd meet the error of "No such file or directory"

Am 15.02.2017 um 01:47 schrieb Zhou, Luwei: Hi Lennart, Thanks for the reply. Is there any command to check whether networkd has been installed in my image. I can find the systemd-nspawn and many system-* in my image. Is the networkd part of systemd package? Sorry, I am new to system.

Re: [systemd-devel] misleadin email Re: Fw: Installing VirtualBox on Debian Jessie - Problem with Linux kernel Name

Am 04.02.2017 um 23:48 schrieb Tomasz Torcz: On Sat, Feb 04, 2017 at 10:34:39PM +, gilesaj wrote: The only reason I posted here is because that is what is in the text of the error. root@ns527415:~#journalctl -xn-- The start-up result is done.Feb 04 15:31:03 ns527415.ip-192-99-6.net

Re: [systemd-devel] Fw: Installing VirtualBox on Debian Jessie - Problem with Linux kernel Name

Am 04.02.2017 um 22:00 schrieb gilesaj: During installation of VirtualBox I got this error. It seems to be a problem with the way the OVH dedicated server displays the Linux Kernel name as 3.14.32--grs-ipv6-64. how is that a systemd problem at all? contact OVH and/or Oracle

Re: [systemd-devel] Any reason why /run and /dev/shm do not have MS_NOEXEC flags set?

Am 01.02.2017 um 11:02 schrieb Hoyer, Marko (ADITG/SW2): a tiny question: - Is there any reason why the mount points /run and /dev/shm do not have MS_NOEXEC flags set? We like to remove execution capabilities from all volatile areas that are writeable to users for security reasons it's all

Re: [systemd-devel] Errorneous detection of degraded array

Am 30.01.2017 um 07:36 schrieb NeilBrown: By virtue of "Following" attribute. dev-md0.device is Following sys-devices-virtual-block-md0.device so stopping the latter will also stop the former. Ahh.. I see why I never saw this now. Two reasons. 1/ My /etc/fstab has

Re: [systemd-devel] "libsystemdexec/systemd-run --exec-from-unit"

Am 29.01.2017 um 07:56 schrieb Colin Walters: Hey so, this is is a half-baked thought, but here goes: One problem I've hit when trying to use systemd unit file features is that they only work when executed by systemd. Let's take the example of User=, but it applies to tons of other ones too.

Re: [systemd-devel] Errorneous detection of degraded array

Am 26.01.2017 um 19:02 schrieb Luke Pyzowski: I have a large RAID6 device with 24 local drives on CentOS7.3. Randomly (around 50% of the time) systemd will unmount my RAID device thinking it is degraded after the mdadm-last-resort@.timer expires, however the device is working normally by

Re: [systemd-devel] Errorneous detection of degraded array

Am 26.01.2017 um 19:02 schrieb Luke Pyzowski: I have a large RAID6 device with 24 local drives on CentOS7.3. Randomly (around 50% of the time) systemd will unmount my RAID device thinking it is degraded after the mdadm-last-resort@.timer expires, however the device is working normally by

Re: [systemd-devel] What information does machine-id leak?

Am 20.01.2017 um 20:54 schrieb Bryan Quigley: But what information is it carrying that is private? none - a UUID is by defintion UNIQUE but random stuff generated once and that's it https://en.wikipedia.org/wiki/Universally_unique_identifier ___

Re: [systemd-devel] Having synchronization between 2 process using systemd.

Am 20.01.2017 um 11:20 schrieb Raghavendra. H. R: I have a scenario in which I have 2 processes and both acts as Server & Client. Process A starts it server & tries to connect as client with Process B. Process B starts it server & tries to connect as client with Process A. We want handle this

Re: [systemd-devel] problem apache2 service

Am 12.01.2017 um 09:12 schrieb Nico - Clicom snc - www.clicom.it: I have this error on my nas: -- Unit apache2-safe.service has begun starting up. Jan 12 08:55:47 ReadyNESSY systemd[5020]: apache2-safe.service: Failed at step EXEC spawning /usr/sbin/apache2: No such file or directory --

Re: [systemd-devel] unit names in systemd log entries

Am 11.01.2017 um 16:11 schrieb Yuri D'Elia: On Wed, Jan 11 2017, Reindl Harald wrote: The description is fine for looking at the status of a service (as the unit name is right there), but it does not help in the log, since I have to go and look which unit has the same description (essentially

Re: [systemd-devel] systemd-networkd in initrd

Am 23.12.2016 um 16:43 schrieb Thijs Cramer: In that case, is there any guide on what's required to get it working? My current scripting only adds the binary (and library dependancies) and adds the systemd-network and resolve users to /etc/passwd. When it starts it says: "Cannot resolve user

Re: [systemd-devel] PrivateNetwork and libusb

Am 14.12.2016 um 10:25 schrieb Richard Hughes: It would be a shame to have PrivateNetwork commented out in fwupd, especially as it's a root daemon that has no business dealing with networking stuff. Is there a way of using PrivateNetwork=yes and allowing AF_NETLINK to correctly work?

Re: [systemd-devel] Best way to limit per-user system-wide units

Am 14.12.2016 um 00:08 schrieb Samuel Williams: Well, given I opened the PR, I'd hope the chance is very low -- at least, no more than sudo. Sudo verifies the configuration using a regular language. It doesn't mean you can't shoot yourself in the foot, but it makes it pretty damn hard.

Re: [systemd-devel] Best way to limit per-user system-wide units

lve not the solution you think is good! On 14 December 2016 at 10:45, Reindl Harald <h.rei...@thelounge.net> wrote: Am 13.12.2016 um 22:40 schrieb Samuel Williams: Reindl, thanks for your ideas. So, I log in as me "bob", but I want to run a task as http, e.g. sud

Re: [systemd-devel] Best way to limit per-user system-wide units

Am 13.12.2016 um 21:41 schrieb Samuel Williams: I wanted to use systemd --user but had trouble getting it to run via sudo- seemed like the environment wasn't getting set up correctly. Any ideas? get rid of sudo and re-consider everything where you are using sudo/su

Re: [systemd-devel] About http://0pointer.net/blog/avoiding-cve-2016-8655-with-systemd.html

Am 09.12.2016 um 01:56 schrieb Michael Biebl: Btw, I think we are lacking a good systemd sandboxing howto/tutorial. The one linked from fdo (http://0pointer.de/blog/projects/security.html) is pretty dated and the systemd.exec man page is not coherent enough with regards to security/sandboxing.

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Am 01.12.2016 um 02:36 schrieb Manuel Amador (Rudd-O): On 09/26/2016 10:31 AM, Reindl Harald wrote: Am 26.09.2016 um 11:27 schrieb Oliver Neukum: On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote: RTFM - when you don't say "nofail" it's ecpected to be crucial your entry

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Am 27.11.2016 um 19:23 schrieb Jonathan de Boyne Pollard: Lennart Poettering: "nofail" has been around as long as fstab has been around really. This is a falsehood. /etc/fstab has a history that goes back to the 20th century. It was in UNIX System 5 Release 3, 4.2BSD, and OSF/1, for

Re: [systemd-devel] after=local-fs not enforced

Am 24.11.2016 um 16:20 schrieb Benoit SCHMID: We have defined the following sap_XXX.service. It contains the following in [Unit]: ### After=local-fs.target network-online.target ora_lsnr_XXX.service remote-fs.target Wants=ora_lsnr_XXX.service ### Stopping and Starting the service with systemd

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

Am 23.11.2016 um 15:19 schrieb Benoit SCHMID: On 11/23/2016 03:03 PM, Reindl Harald wrote: than you need only to adjust "DefaultTimeoutStopSec" to ensure it does not get killed and order services proper In most of my tests, this is set to 5min. Therefore the problem is n

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