Hello,
I've been wanting to discuss the default behaviour of systemctl, which I began
doing on fedora-devel (see [1] for start of thread) before it was pointed out
that systemd-devel is probably a more appropriate place for discussion.
For those who can't be bothered reading through the original
Hi,
I'm trying to build systemd on a shiny new LFS system. I roughly followed the
instructions here:
http://www.linuxfromscratch.org/lfs/view/development/index.html
Since this is a very minimal system, you have to add extra software:
gperf
libcap
attr
expat
libxml2
dbus
No PAM, no gtk, no tcpw
---
src/main.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/main.c b/src/main.c
index 68328b7..11379f6 100644
--- a/src/main.c
+++ b/src/main.c
@@ -169,7 +169,7 @@ _noreturn_ static void crash(int sig) {
_exit(1);
}
-
Thanks a lot,
And how do I select the services to be started at boot time??
I've seen lots of documentation, and possibly I did not read good enough.
Stef
2011/6/20 Maarten Lankhorst :
> Hey Stef,
> sysv init is only used as compatibility. If you have no sysv init scripts,
> nothing will be us
2011/6/20 Christian Hesse :
> Stef Bon on Mon, 20 Jun 2011 15:15:57 +0200:
>> Thanks a lot,
>>
>>
>> And how do I select the services to be started at boot time??
>>
>> I've seen lots of documentation, and possibly I did not read good
>> enough.
>
> Just add "init=/bin/systemd" to you boot options
Stef Bon on Mon, 20 Jun 2011 15:15:57 +0200:
> Thanks a lot,
>
>
> And how do I select the services to be started at boot time??
>
> I've seen lots of documentation, and possibly I did not read good
> enough.
Just add "init=/bin/systemd" to you boot options.
--
Schoene Gruesse
Chris
_
On Mon, Jun 20, 2011 at 12:09 AM, Aaron Sowry wrote:
> Hello,
>
> I've been wanting to discuss the default behaviour of systemctl, which I began
> doing on fedora-devel (see [1] for start of thread) before it was pointed out
> that systemd-devel is probably a more appropriate place for discussion.
On Mon, 20.06.11 15:15, Stef Bon (stef...@gmail.com) wrote:
Heya,
> And how do I select the services to be started at boot time??
Use "systemctl enable" and "systemctl disable" to enable or disable a
service in systemd.
http://0pointer.de/blog/projects/three-levels-of-off
Note that a number of
On Mon, 20.06.11 10:59, Michal Vyskocil (mvysko...@suse.cz) wrote:
Thanks! Applied.
> ---
> src/main.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/src/main.c b/src/main.c
> index 68328b7..11379f6 100644
> --- a/src/main.c
> +++ b/src/main.c
> @@ -169,7 +169,7
On Mon, 20.06.11 09:09, Aaron Sowry (aaron...@aeneby.se) wrote:
> Hello,
Heya,
> I've been wanting to discuss the default behaviour of systemctl, which I began
> doing on fedora-devel (see [1] for start of thread) before it was pointed out
> that systemd-devel is probably a more appropriate plac
On Thu, 16.06.11 14:21, William Douglas (william.r.doug...@gmail.com) wrote:
>
> William Douglas writes:
> > Awww I suck.
> >
>
> Oops was rushing yesterday and didn't notice a compiler warning of great
> interest.
>
> Needed to && the !S_ISCHR !S_ISREG not || them X(.
>
> >From af09c54ac6ce
On Sat, 18.06.11 13:56, Ville Skyttä (ville.sky...@iki.fi) wrote:
> ---
> src/systemctl-bash-completion.sh |8
> 1 files changed, 4 insertions(+), 4 deletions(-)
Thanks a lot!
Applied.
Lennart
--
Lennart Poettering - Red Hat, Inc.
___
On Sat, 18.06.11 16:40, Ville Skyttä (ville.sky...@iki.fi) wrote:
> ---
> man/daemon.xml |2 +-
> man/pam_systemd.xml |4 ++--
> man/systemctl.xml|4 ++--
> man/systemd-ask-password.xml |2 +-
> man/systemd-nspawn.xml |4 ++--
> man/sys
On 06/20/2011 06:58 PM, Lennart Poettering wrote:
> BTW, the subject of this mail suggests you had 3 patches originally. I
> just saw (and commited 2 of them), what happened to patch 2/3? (just
> making sure we are not missing that one)
2/3 was https://bugs.freedesktop.org/show_bug.cgi?id=38439 b
Hello..
Today we hit a bug where incorrect guessing of the MAINPID in a
Type=forking service always killed the service somehow..
The service in question was ypbind from the ypbind-mt package from
kernel.org/utils/NIS..
It forks two times to detach and provides the mainpid in
/var/run/ypbind.pid
Hi there..
we are also using a self-maintained LFS based gnu/linux here.
we switched to systemd in Nov 2010 and it worked fine from the start..
since we started a new LFS we decided not to integrate any support for
sysv anymore by compiling systemd with
--with-distro=other
--wit
On Mon, Jun 20, 2011 at 05:52:22PM +0200, Lennart Poettering wrote:
> > I've been wanting to discuss the default behaviour of systemctl, which I
> > began
> > doing on fedora-devel (see [1] for start of thread) before it was pointed
> > out
> > that systemd-devel is probably a more appropriate pl
2011/6/20 Marius Tolzmann :
> Hi there..
>
> we are also using a self-maintained LFS based gnu/linux here.
>
> we switched to systemd in Nov 2010 and it worked fine from the start..
>
> since we started a new LFS we decided not to integrate any support for
> sysv anymore by compiling systemd with
>
On Fri, 17.06.11 14:53, Bill Nottingham (nott...@redhat.com) wrote:
>
> William Douglas (william.r.doug...@gmail.com) said:
> > For minimal distributions it is useful for systemd to have a
> > syslogd as this avoids the need for extra packages
> > (cron, rsyslog, syslog-ng, logrotate).
>
> My c
I'm trying to set up a new service under Fedora 15. I've created the
following service unit file in /usr/local/etc/svscan.service:
[Unit]
Description=Daemontools svscan
[Service]
ExecStart=/usr/local/bin/svscanboot
Restart=on-abort
[Install]
WantedBy=multi-user.target
Basically, I jus
On Thu, 16.06.11 22:35, William Douglas (william.r.doug...@gmail.com) wrote:
(Read my reply to Bill's mail first)
> - units/syslog-bridge.target
> + units/syslog-bridge.target \
We probably indeed should rename the two logging related services in
systemd. Right now "systemd-logger" conne
On Mon, 20.06.11 14:16, Dave Sill (de5-dated-1309025818.073...@sws5.ornl.gov)
wrote:
> Unit name /usr/local/etc/svscan.service is not a valid unit name.
> Cannot install unit /usr/local/etc/svscan.service: Invalid argument
>
> Obviously it's not expecting a pathname on the command line, so h
On Mon, 20.06.11 19:34, Marius Tolzmann (tolzm...@molgen.mpg.de) wrote:
>
> We fixed this issue by patching ypbind-mt to run in foreground an let
> systemd do the forking - as intended 8)
>
> But it still seems to be some kind of bug in setting the correct MAINPID
> in Type=forking service files
Lennart Poettering wrote:
>
> >
> > And try to start it:
> >
> > systemctl start svscan.service
> >
> > Which results in:
> >
> > Failed to issue method call: Unit svscan.service failed to load: No
> > such file or directory. See system logs and 'systemctl status' for
> > details.
>
Hi,
On Mon, 2011-06-20 at 15:45 -0400, Dave Sill wrote:
> > > Which results in:
> > >
> > > Failed to issue method call: Unit svscan.service failed to load:
> No
> > > such file or directory. See system logs and 'systemctl status'
> for
> > > details.
> >
> > I have now modified this messa
On Mon, 20.06.11 23:15, Sérgio Basto (ser...@serjux.com) wrote:
> Hi,
> On Mon, 2011-06-20 at 15:45 -0400, Dave Sill wrote:
> > > > Which results in:
> > > >
> > > > Failed to issue method call: Unit svscan.service failed to load:
> > No
> > > > such file or directory. See system logs and 's
Hello,
On Tue, 2011-06-21 at 00:43 +0200, Lennart Poettering wrote:
> On Mon, 20.06.11 23:15, Sérgio Basto (ser...@serjux.com) wrote:
>
> > Hi,
> > On Mon, 2011-06-20 at 15:45 -0400, Dave Sill wrote:
> > > > > Which results in:
> > > > >
> > > > > Failed to issue method call: Unit svscan.ser
On Mon, Jun 20, 2011 at 11:56 AM, Lennart Poettering
wrote:
> On Fri, 17.06.11 14:53, Bill Nottingham (nott...@redhat.com) wrote:
>
>>
>> William Douglas (william.r.doug...@gmail.com) said:
>> > For minimal distributions it is useful for systemd to have a
>> > syslogd as this avoids the need for e
Lennart Poettering writes:
> In general I must say that I actually like the code (and the coding
> style) very much, so it's hard for me to say no to this.
>
> KUTGW,
>
> Lennart
I understand your reasoning and, though I'm disappointed it doesn't look like
this syslogd can make it into systemd,
2011/6/20 Marius Tolzmann :
> Hi there..
>
> we are also using a self-maintained LFS based gnu/linux here.
>
> we switched to systemd in Nov 2010 and it worked fine from the start..
What version are you using?
And what version of kernel? Did you have to tune your kernel?? (for
example devfs..)
S
30 matches
Mail list logo
