> -Original Message-
> From: Lennart Poettering [mailto:lenn...@poettering.net]
> Sent: Friday, December 16, 2011 09:40
> To: Michael D. Berger
> Cc: systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] sd_listen_fds: find file descriptor
>
> On Thu, 15.12.11 13:53, Michael
Chen Jie wrote:
> Let me explain it further.
> First syslogv() in dbus may block, while rsyslog.service is starting
> and meanwhile the kernel socket buffer was full.
> Attachment syslog-test.c was a program simulates the situation.
>
> So while rsyslog.service is starting, on the systemd side:
>
On Fri, Dec 16, 2011 at 05:10:45PM +0100, Lennart Poettering wrote:
> On Fri, 16.12.11 12:41, Ran Benita (ran...@gmail.com) wrote:
>
> >
> > On Thu, Dec 15, 2011 at 04:01:05PM +0100, Lennart Poettering wrote:
> > > On Fri, 09.12.11 03:00, Ran Benita (ran...@gmail.com) wrote:
> > >
> > > > +
Am 16.12.2011 17:09, schrieb Lennart Poettering:
> On Fri, 16.12.11 13:41, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>> there must be some bug in Fedora 15 systemd
>> "systectl start/stop vmware-default.service" works perfectly
>>
>> but at shutdown systemd will not wait until it is finish
On Fri, 16.12.11 12:41, Ran Benita (ran...@gmail.com) wrote:
>
> On Thu, Dec 15, 2011 at 04:01:05PM +0100, Lennart Poettering wrote:
> > On Fri, 09.12.11 03:00, Ran Benita (ran...@gmail.com) wrote:
> >
> > > +_username = username;
> > > +r = get_user_creds(&_username, &uid, &gid,
On Fri, 16.12.11 13:41, Reindl Harald (h.rei...@thelounge.net) wrote:
> there must be some bug in Fedora 15 systemd
> "systectl start/stop vmware-default.service" works perfectly
>
> but at shutdown systemd will not wait until it is finished
> before the sysv-service "vmware-service" is terminate
On Thu, 15.12.11 13:53, Michael D. Berger (m.d.ber...@ieee.org) wrote:
>
> [...]
> >
> > Hmm? You should usually consume all fds you get passed. And
> > if you cannot handle more than one, then exit quickly with an
> > error message. And if any of the fds is invalid, then print
> > an error m
On 12/16/2011 01:41 PM, Reindl Harald wrote:
there must be some bug in Fedora 15 systemd
"systectl start/stop vmware-default.service" works perfectly
but at shutdown systemd will not wait until it is finished
before the sysv-service "vmware-service" is terminated
what results in hard-powered-off
there must be some bug in Fedora 15 systemd
"systectl start/stop vmware-default.service" works perfectly
but at shutdown systemd will not wait until it is finished
before the sysv-service "vmware-service" is terminated
what results in hard-powered-off guests and fschecks in most
guests starting th
It seems that both are defined but seen that __x86_64__ is used
in the whole systemd tree, replace to avoid confusion.
---
src/virt.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/virt.c b/src/virt.c
index 380fabd..d866d07 100644
--- a/src/virt.c
+++ b/src/virt.c
@@
On Thu, Dec 15, 2011 at 04:01:05PM +0100, Lennart Poettering wrote:
> On Fri, 09.12.11 03:00, Ran Benita (ran...@gmail.com) wrote:
>
> > +_username = username;
> > +r = get_user_creds(&_username, &uid, &gid, &home);
> > +free(username);
> > +if (r)
> > +
Currently there is no way to refer to the user's name or home directory
from within a unit file. This is mainly a problem for unit files
intended for a --user systemd instance, where you might want to set the
user's home directory in WorkingDirectory, or otherwise refer to the
user's name.
This pa
12 matches
Mail list logo
