On Tue, Mar 27, 2012 at 12:01:52AM +0200, Lennart Poettering wrote:
> On Mon, 26.03.12 23:58, Lennart Poettering ([email protected]) wrote:
>
> > On Sun, 18.03.12 20:28, Dave Reisner ([email protected]) wrote:
> >
> > Heya,
> >
> > > The man page listed -f as the shortopt for both --follo
On Thu, 22.03.12 09:45, Frederic Crozat ([email protected]) wrote:
> Hi,
>
> while building systemd on ppc, I spotted a warning in src/journal/cat.c
> where a char could be used to retrieve a error code, except on ppc, char
> are unsigned. After discussing the issue with Kay on irc, it was decided
Am 26.03.2012 19:37, schrieb Lennart Poettering:
>
> I mean, allowing configuration of separate values for normal user logins
> makes sense. For system services not so much. But with these settings
> you'd configure the latter, not the former, hence I have trouble seeing
> the usefulness of allowi
On Mon, 26.03.12 23:58, Lennart Poettering ([email protected]) wrote:
> On Sun, 18.03.12 20:28, Dave Reisner ([email protected]) wrote:
>
> Heya,
>
> > The man page listed -f as the shortopt for both --follow and --force,
> > but the shortopt only applied to --force. Since --force is the
On Sun, 18.03.12 20:28, Dave Reisner ([email protected]) wrote:
Heya,
> The man page listed -f as the shortopt for both --follow and --force,
> but the shortopt only applied to --force. Since --force is the dangerous
> option, take away the shortopt and give it to --follow. Users should be
> re
On Mon, 19.03.12 13:20, Lucas De Marchi ([email protected]) wrote:
> Set a separate variable for adding warning flags. Build systems are not
> supposed to change CFLAGS and LDFLAGS, these are user variables.
As mentioned on IRC, both patches applied.
Thanks!
Lennart
--
Lennart Po
On Mon, Mar 26, 2012 at 10:43 AM, Lennart Poettering
wrote:
> On Thu, 22.03.12 10:32, Kok, Auke-jan H ([email protected]) wrote:
>
>>
>> On Wed, Mar 21, 2012 at 5:21 PM, Lennart Poettering
>> wrote:
>> >> Here is a patch integrating your header (modified as wanted by Lennart)
>> >> and the
On Mon, Mar 26, 2012 at 21:07, Lennart Poettering
wrote:
> Marti, sorry for changing my mind on this: would be great if you could
> prep a patch for this for systemd itself.
D'oh, I already prepared a patch for kexec, although I haven't sent it out yet.
> Hmm, so since this would then belong in
On Fri, 23.03.12 07:36, Simon Horman ([email protected]) wrote:
>
> On Thu, Mar 22, 2012 at 09:14:56PM +0200, Marti Raudsepp wrote:
> > Hi list,
>
> Hi Marti,
>
> > I was recently pondering how systemd could use kexec "properly", in a
> > reasonably general way, to make reboots faster. I excha
On Thu, 22.03.12 10:32, Kok, Auke-jan H ([email protected]) wrote:
>
> On Wed, Mar 21, 2012 at 5:21 PM, Lennart Poettering
> wrote:
> >> Here is a patch integrating your header (modified as wanted by Lennart)
> >> and the changes in various locations of journal to use le64_t.
> >>
> >> It
On Mon, 26.03.12 10:07, Manuel Amador ([email protected]) wrote:
> Memory limit and memory soft limit aren't rlimits, but cgroup limits?
Yes.
> Is this documented somewhere?
Yes. See systemd.exec(5):
"This controls the memory.limit_in_bytes and memory.soft_limit_in_bytes
control group attribut
On Mon, 26.03.12 19:13, Frederic Crozat ([email protected]) wrote:
> > I am mostly waiting for a usecase here. If somebody makes a good case
> > for hwo they should be useful in system services we can add support for
> > them, but otherwise I am not convinced.
> >
> > We generally only expose kern
OK, in that case it sounds like a bug in yum-updatesd, in that it is
dying without reporting an appropriate error code. This is vexing,
because when I look at the systemd logs I see no entries from yum-updatesd,
and when I start it up after boot, it runs fine (implying that the
ordering dependenci
Am 26. März 2012 16:46 schrieb Lennart Poettering :
> On Mon, 26.03.12 11:06, Albert Strasheim ([email protected]) wrote:
>
> See http://www.kernel.org/doc/Documentation/cgroups/memory.txt for more
> information how MemoryLimit= and MemorySoftLimit= work.
>
>> Is there a way for an application to d
Le lundi 26 mars 2012 à 18:51 +0200, Lennart Poettering a écrit :
> On Mon, 26.03.12 14:25, Frederic Crozat ([email protected]) wrote:
>
> Heya,
>
> > - currently, the limits are set on both rlim_cur and rlim_max (due to
> > reuse of config_parse_limit code). I'd like to extend the
> > implementat
Memory limit and memory soft limit aren't rlimits, but cgroup limits?
Is this documented somewhere?
Sorry if I spread any misinfo.
On Monday, March 26, 2012 16:47:24 Lennart Poettering wrote:
> On Mon, 26.03.12 02:44, Manuel Amador ([email protected]) wrote:
> > memorylimit and memorysoftlimit c
On Mon, 26.03.12 14:25, Frederic Crozat ([email protected]) wrote:
Heya,
> - currently, the limits are set on both rlim_cur and rlim_max (due to
> reuse of config_parse_limit code). I'd like to extend the
> implementation to support separate values for rlim_max and rlim_cur.
> But I'm not 100% sur
On Thu, 22.03.12 16:28, Jack Wu ([email protected]) wrote:
Please do not send HTML mail.
> I apologize for spamming.
>
> I have a question for systemd logging.
>
> Given the same verbosity level, less logs are shown on console when the
> logs (of a systemd service) are directed to ‘stdout’
On Sat, 24.03.12 15:24, Elan Ruusamäe ([email protected]) wrote:
> http://carme.pld-linux.org/~glen/systemd-0001-minor-typo-in-reference-to-manual-page.patch
Applied. Thanks!
Lennart
--
Lennart Poettering - Red Hat, Inc.
___
systemd-devel mailing list
sy
On Sun, 25.03.12 22:02, Sven Anders ([email protected]) wrote:
> Hello!
>
> I'm trying to switch to systemd, but I have some minor problem.
>
> "systemctl status systemd-logind.service" reports failure.
> The error message is the following:
>
> Linux/OS (d-login)[206]: Failed at step CAPABILITI
On Mon, 26.03.12 03:33, Edward Z. Yang ([email protected]) wrote:
> A few weeks ago, yum-updatesd died due to the following bug
> https://bugzilla.redhat.com/show_bug.cgi?id=709315
>
> This is exactly something that we would like systemd to report
> us. However, while interacting with servers with
On Mon, Mar 26, 2012 at 17:53, Lennart Poettering
wrote:
> On Mon, 26.03.12 17:02, Leo Baltus ([email protected]) wrote:
>> I am in the process of setting up a fairly standard busybox to act as
>> an initrd and rescue environment. The idea is to use a fedora kernel in
>> which all boot-time ne
On Mon, 26.03.12 17:02, Leo Baltus ([email protected]) wrote:
> Hi,
heya,
> I am in the process of setting up a fairly standard busybox to act as
> an initrd and rescue environment. The idea is to use a fedora kernel in
> which all boot-time needed modules are compiled in so we can boot all
Hi,
I am in the process of setting up a fairly standard busybox to act as
an initrd and rescue environment. The idea is to use a fedora kernel in
which all boot-time needed modules are compiled in so we can boot all of
our hardware from the same initrd.
The initrd is supposed to do some boot-time
On Mon, Mar 26, 2012 at 4:46 PM, Lennart Poettering
wrote:
>> Also, is there some standard way for the app[M#O7lication to determine if a
>> MemoryLimit= is configured? We might want to automatically size some
>> buffers based on this limit.
> You can read /proc/self/cgroup. Find the line with ":m
On Mon, 26.03.12 02:44, Manuel Amador ([email protected]) wrote:
>
> memorylimit and memorysoftlimit can be determined using the ulimit system
> call.
AFAICS that is simply not correct. The resource limit logic and the
cgroup memory logic are orthogonal.
Lennart
--
Lennart Poettering - Red H
On Mon, 26.03.12 11:06, Albert Strasheim ([email protected]) wrote:
> Hello all
>
> We want to limit the memory a service can use using MemoryLimit= and
> MemorySoftLimit= described in systemd.exec.
>
> As I understand it, LimitAS= and LimitRSS= aren't particularly useful.
> Linux doesn't even i
Hi all,
following one of our bug opened on systemd (
https://bugzilla.novell.com/show_bug.cgi?id=744818 ) and after discussing the
issue on irc,
I found some time to do a initial implementation of systemd wide rlimit support.
Idea is simple :
- admin can set system wide limits for all services
Am 26.03.2012 00:06, schrieb Kay Sievers:
> On Sun, Mar 25, 2012 at 22:02, Sven Anders wrote:
>> I'm trying to switch to systemd, but I have some minor problem.
>>
>> "systemctl status systemd-logind.service" reports failure.
>> The error message is the following:
>>
>> Linux/OS (d-login)[206]: Fa
Yes, getrlimit.
yes, rlimit_as
On Monday, March 26, 2012 11:50:11 Albert Strasheim wrote:
> Hello
>
> On Mon, Mar 26, 2012 at 11:44 AM, Manuel Amador wrote:
> > memorylimit and memorysoftlimit can be determined using the ulimit system
> > call.
>
> Do you mean getrlimit? man 2 ulimit on F16 s
Hello
On Mon, Mar 26, 2012 at 11:44 AM, Manuel Amador wrote:
> memorylimit and memorysoftlimit can be determined using the ulimit system
> call.
Do you mean getrlimit? man 2 ulimit on F16 says it's not implemented.
If it's getrlimit, is it RLIMIT_AS?
> you cannot detect when you've hit the soft
memorylimit and memorysoftlimit can be determined using the ulimit system
call.
you cannot detect when you've hit the soft limit other than by getting a NULL
on malloc.
On Monday, March 26, 2012 11:06:42 Albert Strasheim wrote:
> Hello all
>
> We want to limit the memory a service can use usin
On a more on-topic question:
I have two pools composed of several devices each. One of those pools is
available right after dm-crypt in the initrd, and contains the root file
system plus a bunch of other file systems. I am handling that using
generators. The other pool, well, gets no handlin
Hello all
We want to limit the memory a service can use using MemoryLimit= and
MemorySoftLimit= described in systemd.exec.
As I understand it, LimitAS= and LimitRSS= aren't particularly useful.
Linux doesn't even implement LimitRSS?
http://unix.stackexchange.com/questions/32368/how-to-limit-appl
On Mon, Mar 26, 2012 at 8:19 AM, Eduardo Tongson wrote:
> On Mon, Mar 26, 2012 at 7:33 AM, Edward Z. Yang wrote:
>> A few weeks ago, yum-updatesd died due to the following bug
>> https://bugzilla.redhat.com/show_bug.cgi?id=709315
>>
>> This is exactly something that we would like systemd to repor
On 03/26/2012 07:33 AM, Edward Z. Yang wrote:
A few weeks ago, yum-updatesd died due to the following bug
https://bugzilla.redhat.com/show_bug.cgi?id=709315
This is exactly something that we would like systemd to report
us. However, while interacting with servers with the dead
yum-updatesd, we
On Mon, Mar 26, 2012 at 7:33 AM, Edward Z. Yang wrote:
> A few weeks ago, yum-updatesd died due to the following bug
> https://bugzilla.redhat.com/show_bug.cgi?id=709315
>
> This is exactly something that we would like systemd to report
> us. However, while interacting with servers with the dead
A few weeks ago, yum-updatesd died due to the following bug
https://bugzilla.redhat.com/show_bug.cgi?id=709315
This is exactly something that we would like systemd to report
us. However, while interacting with servers with the dead
yum-updatesd, we found it didn't show up when we ran
systemctl --
38 matches
Mail list logo
