On Sat, May 4, 2013 at 3:14 AM, Mirco Tischler wrote:
> No this won't work. Systemd is not a shell. Simply write a bash script where
> you do all your stuff and then put that as the ExecStart line.
Many shell built-ins have real execuables, too. Just run "which" on them.
--
David Strauss
| da
Hi,
Just trying to work out a few problems on our (Mageia's) NFS packages.
As with a lot of things we often take the units from Fedora (we will
soon have a nicer way to share units I hope - need to get release out
the way before I can help and put my bit of the work into this tho').
However I'm
On Fri, 03.05.13 19:55, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> On Fri, May 03, 2013 at 06:51:35PM +0200, Lennart Poettering wrote:
> > On Wed, 24.04.13 10:30, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
> > wrote:
> >
> > > [0.019862] fedora kernel: CPU0: Thermal mon
---
TODO | 3 -
man/systemd-delta.xml | 7 +++
src/delta/delta.c | 170 ++
3 files changed, 164 insertions(+), 16 deletions(-)
diff --git a/TODO b/TODO
index 84ede8c..eab5f87 100644
--- a/TODO
+++ b/TODO
@@ -74,9 +74,6 @@ Fe
On 05/06/2013 09:27 AM, Colin Guthrie wrote:
Hi,
Just trying to work out a few problems on our (Mageia's) NFS packages.
As with a lot of things we often take the units from Fedora (we will
soon have a nicer way to share units I hope - need to get release out
the way before I can help and put my
Hi,
I have masked the systemd-journal-flush.service and set the
Storage=persistent in journald.conf. Then I have removed the
/var/log/journal folder. My expectation on next boot was to see the journal
files in /var/log/journal but they have stayed in /run/log/journal.
According to man journald, i
Hi,
Would you be interested in a patch that shows "Systemd + Generators" or
maybe only "Generators"?
Sample is attached.
Thanks[image: Inline image 1]
<>___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mail
On Sat, 04.05.13 11:38, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> A new config file /etc/systemd/sleep.conf is added.
> It is parsed by systemd-sleep and logind. The strings written
> to /sys/power/disk and /sys/power/state can be configured.
> This allows people to use different mo
On Sun, 05.05.13 18:08, Umut Tezduyar (u...@tezduyar.com) wrote:
> On Fri, May 3, 2013 at 4:58 PM, Lennart Poettering
> wrote:
>
> > On Sun, 28.04.13 20:37, Umut Tezduyar (u...@tezduyar.com) wrote:
> >
> > > Hi,
> > >
> > > Should DefaultOOMScore= and DefaultLimit***= be really under [Manager]?
>
On Mon, 06.05.13 14:00, Umut Tezduyar (u...@tezduyar.com) wrote:
> Hi,
>
> Would you be interested in a patch that shows "Systemd + Generators" or
> maybe only "Generators"?
Well, I guess it makes sense to show how much time is spent in the
generators and how much time is spent in systemd's own
On Mon, May 6, 2013 at 2:51 PM, Lennart Poettering
wrote:
> On Mon, 06.05.13 14:00, Umut Tezduyar (u...@tezduyar.com) wrote:
>> Would you be interested in a patch that shows "Systemd + Generators" or
>> maybe only "Generators"?
>
> Well, I guess it makes sense to show how much time is spent in the
On 04/30/2013 06:04 PM, har...@redhat.com wrote:
> From: Harald Hoyer
>
> Do the depmod in the kernel-install hooks, so hooks can produce/install
> kernel modules and be part of the depmod.
> ---
> Makefile.am | 7 ---
> src/kernel-install/50-depmod.install | 8 +
---
man/systemd.special.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man/systemd.special.xml b/man/systemd.special.xml
index 61d45ff..7164b1e 100644
--- a/man/systemd.special.xml
+++ b/man/systemd.special.xml
@@ -784,7 +784,7 @@
To search the libgcrypt support the developer are advised
to use the automake macro AM_PATH_LIBGCRYPT. But if libgcrypt-devel
is not installed the macro does not exist yet and so
configure goes wrong. This patch test first whether the macro is defined,
and if not it set have_lgcrypt to false.
Sig
Say Lennart prepares a new upstream release and forgot to install
libgcrypt-devel, then he silently produces a dist tarball which will
be broken.
I'm not sure I like that behaviour.
Michael
2013/5/6 Elia Pinto :
> To search the libgcrypt support the developer are advised
> to use the automake mac
On Mon, May 06, 2013 at 07:35:18PM +0200, Michael Biebl wrote:
> Say Lennart prepares a new upstream release and forgot to install
> libgcrypt-devel, then he silently produces a dist tarball which will
> be broken.
> I'm not sure I like that behaviour.
It would be better to fix gcrypt to support pk
>From the man page:
> Additional units to install when this unit is installed. If the user
> requests installation of a unit with this option configured,
> systemctl enable will automatically install units listed in this
> option as well.
What also happens however is that it if systemctl disable
On Mon, 06.05.13 09:46, Elia Pinto (gitter.spi...@gmail.com) wrote:
> To search the libgcrypt support the developer are advised
> to use the automake macro AM_PATH_LIBGCRYPT. But if libgcrypt-devel
> is not installed the macro does not exist yet and so
> configure goes wrong. This patch test first
To search the libgcrypt support the developer are advised
to use the automake macro AM_PATH_LIBGCRYPT. But if libgcrypt-devel
is not installed the macro does not exist yet and so
configure goes wrong. This patch test first whether the macro is defined,
and if not it set have_lgcrypt to false.
Sig
Le 06/05/2013 11:27, Colin Guthrie a écrit :
Also, It is my understanding (and feel free to correct me here) but
nfs-idmap is often needed on client systems also? I'm sure I had to
configure a client in the past to ensure idmap was running in order to
avoid permissions problems and users getting
On Mon, 06.05.13 12:41, Umut Tezduyar (u...@tezduyar.com) wrote:
> Hi,
>
> I have masked the systemd-journal-flush.service and set the
> Storage=persistent in journald.conf. Then I have removed the
> /var/log/journal folder. My expectation on next boot was to see the journal
> files in /var/log/j
On Mon, 06.05.13 22:39, Lennart Poettering (lenn...@poettering.net) wrote:
> > According to man journald, it shouldn't be necessary to send the SIGUSR1 as
> > systemd-journal-flush.service does. It was my expectation that systemd
> > would eventually carry journal to /var/.
>
> The man page is ac
On Mon, 06.05.13 19:29, Colin Guthrie (gm...@colin.guthr.ie) wrote:
> >From the man page:
>
> > Additional units to install when this unit is installed. If the user
> > requests installation of a unit with this option configured,
> > systemctl enable will automatically install units listed in thi
On Mon, 06.05.13 15:32, Ross Lagerwall (rosslagerw...@gmail.com) wrote:
Applied! Thanks!
> ---
> man/systemd.special.xml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man/systemd.special.xml b/man/systemd.special.xml
> index 61d45ff..7164b1e 100644
> --- a/man/sys
On Sun, 05.05.13 18:09, Daniel Wallace (danielwall...@gtmanfred.com) wrote:
> Instead of completing the whole line, which doesn't work, only complete
> the pid, but still show the whole line so the user can see which command
> was which.
Thanks! Applied!
Lennart
--
Lennart Poettering - Red Hat
On Mon, 06.05.13 14:26, Lennart Poettering (lenn...@poettering.net) wrote:
> On Sat, 04.05.13 11:38, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > A new config file /etc/systemd/sleep.conf is added.
> > It is parsed by systemd-sleep and logind. The strings written
> > to /sys/power
On Tue, 23.04.13 10:35, Colin Walters (walt...@verbum.org) wrote:
> I found myself in a situation recently where I wanted to log
> a message from a shell script that included MESSAGE_ID. As
> far as I can tell there's no utility binary for this.
True.
> systemd ships systemd-cat which connects
On Tue, 23.04.13 13:34, MUNEDA Takahiro (muneda.takah...@jp.fujitsu.com) wrote:
> This patch escapes a unit name which was derived from udev.
>
> Please imagine following udev rule.
>
> ACTION=="online|offline", TAG+="systemd",
> ENV{SYSTEMD_WANTS}="muneda@%p.service"
> ACTION=="online|offl
Hey list,
Are there any plans to enable waking the system from sleep upon some timer
events defined in systemd units? By no means it should wake up on every
timer. But it should be able to wake the system for specially labelled timer
units and after finishing them put the system back to sleep (
On Mon, May 6, 2013 at 11:12 PM, Lennart Poettering
wrote:
> On Tue, 23.04.13 13:34, MUNEDA Takahiro (muneda.takah...@jp.fujitsu.com)
> wrote:
>
>> This patch escapes a unit name which was derived from udev.
>>
>> Please imagine following udev rule.
>>
>> ACTION=="online|offline", TAG+="systemd
Hey list,
I've built a server with systemd and it really worked out well. Fast booting
(that means shorter maintenance times) and most important: Reliable service
teardown and auto-restarts of crashed services. And yeah, I love the
journal. I'm logging everything there.
But now I want to (and
On 05/06/2013 09:44 PM, Kai Krakow wrote:
But now I want to (and need to) give some users cron-like abilities. I
discovered that systemd supports user instances - perfect!
Then install cronie...
JBG
___
systemd-devel mailing list
systemd-devel@lists.
On Mon, 06.05.13 23:00, Kai Krakow (hurikha...@gmail.com) wrote:
Heya,
> Are there any plans to enable waking the system from sleep upon some timer
> events defined in systemd units? By no means it should wake up on every
> timer. But it should be able to wake the system for specially labelled
Lennart Poettering schrieb:
>> Are there any plans to enable waking the system from sleep upon some
>> timer events defined in systemd units? By no means it should wake up on
>> every timer. But it should be able to wake the system for specially
>> labelled timer units and after finishing them pu
Jóhann B. Guðmundsson schrieb:
>> But now I want to (and need to) give some users cron-like abilities. I
>> discovered that systemd supports user instances - perfect!
>
> Then install cronie...
That's the obvious solution but a little bit counter-productive with respect
to my question...
Anyw
Heya,
http://www.freedesktop.org/software/systemd/systemd-203.tar.xz
This is probably a good release to synchronize a distribution on. For
example, it is our goal that this is the version we will include in
Fedora 19, more or less. d systemd git otoh will probably receive more
invasive changes ag
El 05/05/13 13:17, Sébastien Luttringer escribió:
Hello,
"journcalctl --no-pager" or" journalctl | cat" produce enless content
by looping accross journal entries. The date in lines restart from the
beginning when the end is reached.
We have reports about this behaviour in openSUSE as well, the
I don't recommend spawning user instances of systemd just for their
timer units to run. Each instance comes with a few MB of overhead, and
you'll have no fun trying to spawn sessions in a way isolated from
(but somehow integrated with) the PAM session initialization process.
On Mon, May 6, 2013 at
On Mon, May 6, 2013 at 2:44 PM, Kai Krakow wrote:
> Hey list,
>
> I've built a server with systemd and it really worked out well. Fast booting
> (that means shorter maintenance times) and most important: Reliable service
> teardown and auto-restarts of crashed services. And yeah, I love the
> jour
2013/5/7 Lennart Poettering :
> * libsystemd-logind.so gained a new call
> sd_get_machine_names() to enumerate running containers and
> VMs (currently only supported by very new libvirt and
> nspawn). sd_login_monitor can now be used to watch
> VMs/co
On Tue, May 07, 2013 at 12:10:26AM +0200, Kai Krakow wrote:
> [...]
>
> Meanwhile, where's a good place to contribute my systemd unit files I
> created for different services that not yet seem to be covered by the
> systemd distribution? They could also need some review maybe...
Upstream - su
On 05/06/2013 10:14 PM, Kai Krakow wrote:
Jóhann B. Guðmundsson schrieb:
But now I want to (and need to) give some users cron-like abilities. I
discovered that systemd supports user instances - perfect!
Then install cronie...
That's the obvious solution but a little bit counter-productive wi
42 matches
Mail list logo
