[systemd-devel] [PATCH] man/systemctl.xml: Add missing space for »stopcommand«
Date: Thu, 24 May 2012 22:20:39 +0200 --- I do not know if that has been fixed already. $ git remote update Fetching origin fatal: The remote end hung up unexpectedly error: Could not fetch origin with `url = git://anongit.freedesktop.org/systemd`. man/systemctl.xml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/systemctl.xml b/man/systemctl.xml index 2ea6fe9..9c9d2fe 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -697,7 +697,7 @@ command does not implicitly stop the units that is being disabled. If this is desired an additional -stopcommand should +stop command should be executed afterwards. This command will print the -- 1.7.10 signature.asc Description: This is a digitally signed message part ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-journald process footprint
Hi, all! I run Linux embedded system with quite tight resources. We successfully use systemd for some time, but with introduction of journald we get show-stopper problems, preventing us from upgrade to newer systemd, to get functionality we need and bugs fixed. A problem is that journald is most resource-consuming process on device, it eats most of RAM and most of CPU. For comparison if we run rsyslogd on journald's pipe, its footprint is 10 times smaller, than journald's. So, we have 2 choices - either to reduce journald's footprint (which actually just passing pipe to our custom logger, which is already frowned upon, because it is not something small), or get rid of it. So questions are: 1. is it possible to run systemd the "old way", so without journald, with all logging to normal syslog()? If it is not possible as is, how hard is to patch systemd to work like this, any pointers? 2. If 1. is too comlicated, is there any ways to make journald as tiny as possible with memory/CPU consumption? All I need from it is redirection to syslog pipe, I don't need any fancy stuff with statuses/etc. Any config options, per chance? I set values in journald.conf to minimum possible, and don't see any memory footprint changes. We do A LOT of logging. Our custom logging service serves its purpose as local and remote logger perfectly, and the information logged is critical to us. Any help is appreciated Thanks a lot, S. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [HEADSUP] fstab now parsed by generator in systemd git
On Wednesday, May 23, 2012, Lennart Poettering wrote: > On Wed, 23.05.12 12:10, Gustavo Sverzut Barbieri > (barbi...@profusion.mobi) > wrote: > > > >> One suggestion at IRC was to just keep systemd mount units. But if we > > >> should go this route, then we should call to deprecate /etc/fstab. > > >> Last time we discussed about it, people said it was not going to > > >> happen since some tools were parsing and relying on it. Whats is the > > >> way to go? > > > > > > We don't really deprecate it. But if people want to they don't have to > > > use it now, and can do this easily by dropping the file and removing > the > > > generator. > > > > > > You know, fewer PIDs are definitely a good thing, but for some things > > > doing them out-of-process is actually a good thing. Unix knows > processes > > > and process isolation for a reason. > > > > In this case I'm still more for having the fstab parser bultin, > > however I understand your point. > > > > In my usage I'll just drop fstab and see what happens. For sure simple > > "mount /mountpoint" will not work anymore, then I wonder if there is > > any plan to provide systemd-mount to be linked as /bin/mount in order > > to get the mount description (device, point, options) from systemd > > mount units instead of fstab. > > We have that already. It has a slightly different syntax though: > > systemctl start mountpoint.mount > I know this, but it's not a drop in replacement for the default "mount". Shouldn't be hard, do you think it would be accepted in systemd or better to try to patch default mount to use systemd "sd_booted() -> call it for unit" > Lennart > > -- > Lennart Poettering - Red Hat, Inc. > -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to set complex environment for apache?
Am 24.05.2012 01:56, schrieb Lennart Poettering: > On Wed, 23.05.12 16:45, Joachim Banzhaf (joachim.banz...@googlemail.com) > wrote: > >> Am 22.05.2012 22:51, schrieb Zbigniew Jędrzejewski-Szmek: >>> On 05/22/2012 10:46 PM, Joachim Banzhaf wrote: It sets and modifies environment variables. I'll have a look and try, >>> See also Environment= and EnvironmentFile= in systemd.exec(5). >>> >>> Zbyszek >> >> I tried now. Not sure if the result is optimal, but it might still help >> others with a similar problem. >> >> The DB2 provided profile script (for now) only sets and changes >> environment variables (PATH, LD_LIBRARY_PATH, CLASSPATH, DB2INSTANCE), >> with some if/else logic based on what product options are installed or not. >> >> I cannot use the script as is in ExecStartPre because this only allows >> binaries. >> I even tried /bin/bash script, but as expected the changed environment >> is not inherited by ExecStart >> >> So the only systemd options (I know of now) left are Environment and >> EnvironmentFile. >> I went with EnvironmentFile, because that is what I used before. I just >> added the variables by hand instead of by sourcing the db2profile >> script. This worked (I had to export the variables to make it backward >> compatible with SysV init though). >> >> If I'd use this approach with systemd and DB2 I'd have to manually >> analyze changes in the db2profile and try to mimic that with every >> fixpack or special build delivered by IBM. Too error prone, not acceptable. >> >> Finally I tried this, and it worked. But I am not sure about side effects: >> >> I changed >>ExecStart=/usr/sbin/start_apache2 -D SYSTEMD -k start' >> to >>ExecStart=/bin/bash -c '. /home/db2inst1/sqllib/db2profile; >> /usr/sbin/start_apache2 -D SYSTEMD -k start' >> >> Thanks for you support! > > This solution is pretty much what I'd recommend too. Would adding an "exec" allow to get rid of the bash? Will this have any advantages? ExecStart=/bin/bash -c '. /home/db2inst1/sqllib/db2profile; exec /usr/sbin/start_apache2 -D SYSTEMD -k start' For some cases it would be nice if you could run an command to set complex environments. Something like: EnvironmentExec=/home/db2inst1/sqllib/db2profile But instead of just reading the file, it's executed and the environment variables are taken. Another idea I had was to have the possibility to set single variables which can be used in the Exec command by executing external commands. But I think this would made systemd too complex... Regards Sven Anders -- Sven Anders () UTF-8 Ribbon Campaign /\ Support plain text e-mail ANDURAS intranet security AG Messestrasse 3 - 94036 Passau - Germany Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55 Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin <>___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
