Mirco,
On Mon, Apr 18, 2011 at 11:57:46PM +0200, Mirco Tischler wrote:
> How about pointing the default.target symlink at your custom unit that
> pulls in only a very basic system and executes your custom setup
> script.
That sounds pretty good, we'll try that!
rsc
--
Pengutronix e.K.
Hello all
I've been experimenting with
http://0pointer.de/public/systemd-units/sshd@.service
It works well, but I've noticed that each client connection adds a
line to the output in
systemctl --system --full
e.g.,
sshd@127.0.0.1:2-127.0.0.1:35006.service error failed failed
sshd@127.0.0.
On 04/19/2011 09:15 AM, Albert Strasheim wrote:
> Hello all
>
> I've been experimenting with
>
> http://0pointer.de/public/systemd-units/sshd@.service
>
> It works well, but I've noticed that each client connection adds a
> line to the output in
>
> systemctl --system --full
>
> e.g.,
>
> ssh
Hi,
On Tue, Apr 19, 2011 at 09:02:47AM +0200, Robert Schwebel wrote:
> On Mon, Apr 18, 2011 at 11:57:46PM +0200, Mirco Tischler wrote:
> > How about pointing the default.target symlink at your custom unit that
> > pulls in only a very basic system and executes your custom setup
> > script.
>
> Th
On 04/18/2011 11:04 PM, Stef Bon wrote:
2011/1/17 Lennart Poettering:
possible is via xattr support in procfs and cgroupfs.
Anyway, as mentioned, I am not really ready to discuss this now. Sorry
of that might sound disappointing.
Why do think anyone is disappointed, by you not reacting? Do y
2011/4/19 Michael Olbrich :
> Hi,
>
> On Tue, Apr 19, 2011 at 09:02:47AM +0200, Robert Schwebel wrote:
>> On Mon, Apr 18, 2011 at 11:57:46PM +0200, Mirco Tischler wrote:
>> > How about pointing the default.target symlink at your custom unit that
>> > pulls in only a very basic system and executes y
Well, your email suprises me, really.
Yes I read some sort of apologies, but he is expecting someone is
dissapointed he's not reacting. If that's not arrogant, I'm a marsian.
I will raise a fund to support all of those who are dissapointed by
him not reacting... Yek
Much better would be just: I c
On Tue, Apr 19, 2011 at 12:15:01PM +0200, Mirco Tischler wrote:
> 2011/4/19 Michael Olbrich :
> > Hi,
> >
> > On Tue, Apr 19, 2011 at 09:02:47AM +0200, Robert Schwebel wrote:
> >> On Mon, Apr 18, 2011 at 11:57:46PM +0200, Mirco Tischler wrote:
> >> > How about pointing the default.target symlink at
Dnia wtorek, 19 kwietnia 2011 o 13:22:06 Stef Bon napisał(a):
> Well, your email suprises me, really.
> Yes I read some sort of apologies, but he is expecting someone is
> dissapointed he's not reacting. If that's not arrogant, I'm a marsian.
There is a difference between ‘it might sound disappoin
Hello again
I had the same problem again today trying to start a service.
The last few system calls made by systemd-tty-ask-password-agent are:
19048 mkdir("/run", 0755) = -1 EEXIST (File exists)
19048 mkdir("/run/systemd", 0755) = -1 EEXIST (File exists)
19048 mkdir("/run/sy
During this time, systemd does the following:
epoll_wait(4, {{EPOLLIN, {u32=25559008, u64=25559008}}}, 1, 4294967295) = 1
accept4(8, {sa_family=AF_FILE, NULL}, [2], SOCK_CLOEXEC) = 15
fcntl(15, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(15, F_SETFL, O_RDWR|O_NONBLOCK) = 0
getsockna
Hello
Finally, a clue.
It seems after a really long time, or maybe sometimes, systemctl will print:
A dependency job failed. See system logs for details.
and sometimes (but not always), syslog will contain:
systemd[1]: Job dev-dm-0.device/start timed out.
This is caused by an
After=dev-%i.de
Hello again
My previous problem with an After= referring to a device seems to have
been caused by a device with a dash in the name.
I had a service called mounter@dm-0.service with
BindTo=dev-%i.device
After=dev-%i.device
which fails to find dev-dm-0.device because systemd seems to be calling i
On Tue, Apr 19, 2011 at 12:28 PM, Albert Strasheim wrote:
>
> Hello again
>
> My previous problem with an After= referring to a device seems to have
> been caused by a device with a dash in the name.
>
> I had a service called mounter@dm-0.service with
>
> BindTo=dev-%i.device
> After=dev-%i.devic
2011/4/18 Lennart Poettering :
> /lib/systemd/system. I'd be willing to merge a patch to make these
> things configurable at compile time via ./configure switches. In general
One big configure switch or a configure switch per feature?
Michael
--
Why is it that all of the instruments seeking int
On Tue, 19.04.11 21:53, Michael Biebl (mbi...@gmail.com) wrote:
>
> 2011/4/18 Lennart Poettering :
> > /lib/systemd/system. I'd be willing to merge a patch to make these
> > things configurable at compile time via ./configure switches. In general
>
> One big configure switch or a configure switc
On Tue, 19.04.11 13:57, Chris Ferron (chris.e.fer...@linux.intel.com) wrote:
Heya,
Please send patches to the systemd-devel mailing list, as
systemd-commits is only for notifications of actual upstream commits.
Minor nitpicks: we don't do S-o-b in systemd, we aren't the
kernel. Please send white
On Tue, 19.04.11 17:28, Albert Strasheim (full...@gmail.com) wrote:
> Hello again
>
> My previous problem with an After= referring to a device seems to have
> been caused by a device with a dash in the name.
>
> I had a service called mounter@dm-0.service with
>
> BindTo=dev-%i.device
> After=d
On Mon, 18.04.11 23:57, Mirco Tischler (mt...@gmx.de) wrote:
> > I'm trying to migrate some stuff to systemd, but I have some problems
> > getting it right.
> > The scenario:
> > I'm cross-building root file systems. I try to do as much as possible
> > on the host system, but there is some stuff t
On Sun, 17.04.11 10:33, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> Hi,
>
> I'm trying to migrate some stuff to systemd, but I have some problems
> getting it right.
> The scenario:
> I'm cross-building root file systems. I try to do as much as possible
> on the host system, but there is
On Tue, 19.04.11 13:52, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
>
> On Tue, Apr 19, 2011 at 12:15:01PM +0200, Mirco Tischler wrote:
> > 2011/4/19 Michael Olbrich :
> > > Hi,
> > >
> > > On Tue, Apr 19, 2011 at 09:02:47AM +0200, Robert Schwebel wrote:
> > >> On Mon, Apr 18, 2011 at 11:57
On Thu, 14.04.11 17:34, fykc...@gmail.com (fykc...@gmail.com) wrote:
> diff --git a/src/missing.h b/src/missing.h
> index 35e209f..b367831 100644
> --- a/src/missing.h
> +++ b/src/missing.h
> @@ -125,7 +125,12 @@ static inline int fanotify_init(unsigned int flags,
> unsigned int event_f_flags)
>
On Thu, 14.04.11 17:35, fykc...@gmail.com (fykc...@gmail.com) wrote:
> Hi all,
>
> /.readahead exists means activated readahead-replay will run. Meanwhile if
> readahead-collect runs, all replayed blocks will be collected -- size of
> /.readahead will increase(e.g. in case of services update).
W
On Wed, 13.04.11 12:11, Tomasz Torcz (to...@pipebreaker.pl) wrote:
> Hi,
>
> Typing "sessionctl status …" is easier than "systemctl --sesion status …".
There is no --session anymore. It's --user since quite some time. I
don't think we should introduce an extra binary name for this. After all
On Tue, 12.04.11 16:15, Albert Strasheim (full...@gmail.com) wrote:
Heya,
> I had the following in my syslog today while my service was running:
>
> systemd[1]: Got invalid poll event on socket.
> systemd[1]: foo.service: main process exited, code=exited, status=1
>
> What causes invalid poll e
On Thu, 07.04.11 14:55, Marius Tolzmann (tolzm...@molgen.mpg.de) wrote:
Heya,
> we have a setup where every user can start its own services
> (e.g. a webserver, database server, whatever).
>
> if the user wants this service to be started after a reboot he just
> tells us the name of its startup
On Fri, 15.04.11 17:42, Marius Tolzmann (tolzm...@molgen.mpg.de) wrote:
>
> Hi..
>
> is there a simple or documented way to start a user systemd at boot
> time?
Nope, no docs yet. All still in flux.
> when i create a unit for systemd --user including the PAM setup a
> user-systemd gets started
On Tue, 05.04.11 08:23, Albert Strasheim (full...@gmail.com) wrote:
> Hello all
>
> I have the following socket unit:
>
> [Unit]
> Description=unix sock
>
> [Socket]
> ListenStream=@foo/%i
> Backlog=128
> Service=foo@%i.service
>
> [Install]
> Alias=foo@dev1.socket
> Alias=sockets.target.wants
On Tue, 05.04.11 10:06, Albert Strasheim (full...@gmail.com) wrote:
> Hello all
>
> Sometimes (not sure when), when I run
>
> systemctl stop foo.service
>
> where foo.service is in this state:
>
> foo.service loaded failed failed stop Foo
Would be good to get my hands on an output of "systemc
On Tue, 19.04.11 17:02, Albert Strasheim (full...@gmail.com) wrote:
>
> Hello again
>
> I had the same problem again today trying to start a service.
>
> The last few system calls made by systemd-tty-ask-password-agent are:
>
> 19048 mkdir("/run", 0755) = -1 EEXIST (File exists)
On Tue, 19.04.11 17:06, Albert Strasheim (full...@gmail.com) wrote:
> and then hangs in an epoll_wait.
This looks pretty much correct too. We are just waiting for a response
from systemd.
Lennart
--
Lennart Poettering - Red Hat, Inc.
___
systemd-deve
On Tue, 19.04.11 17:18, Albert Strasheim (full...@gmail.com) wrote:
>
> Hello
>
> Finally, a clue.
>
> It seems after a really long time, or maybe sometimes, systemctl will print:
>
> A dependency job failed. See system logs for details.
>
> and sometimes (but not always), syslog will contain
On Thu, 31.03.11 09:59, Sedat Dilek (sedat.di...@googlemail.com) wrote:
> Hi,
>
> I am here on v20 of systemd and wanted to setup a local
> fetchmail/postfix solution by following the hints in [1].
>
> As my system changes daily (I am on linux-next), it took some time to
> understand what piece
On Wed, 30.03.11 18:06, Ian Pilcher (arequip...@gmail.com) wrote:
> Hi -
>
> I am trying to figure out why systemd is getting hung up trying to
> start one of my filesystems.
>
> (Details at https://bugzilla.redhat.com/show_bug.cgi?id=692248 for
> the masochists out there.)
>
> I've reached th
On Sat, 02.04.11 01:11, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
> Hello. I have a daemon, that runs before init system, it do some things
> and must sleep before system go to 3 or 5 runlevel.
> That is the best way to waiting ? I'm not only using systemd, but other
> init systems too...
> V
On Fri, 18.03.11 07:42, Michael Biebl (mbi...@gmail.com) wrote:
>
> 2011/3/18 Mike Kazantsev :
> > On Fri, 18 Mar 2011 07:03:01 +0100
> > Michael Biebl wrote:
> >
> >> Hi,
> >>
> >> when booting with systemd.log_level=debug, I get
> >>
> >> Mar 18 06:39:26 pluto rsyslogd-2177: imuxsock begins to
On Fri, 18.03.11 09:35, fykc...@gmail.com (fykc...@gmail.com) wrote:
> Hi all,
>
> We did a series boot-time tests of systemd, and found some interesting things:
> (Note the tests were performed on a laptop with a 4-core mips cpu, AMD
> RS780 chipset, 2GB Memory, rotate harddisk with ext4 filesys
On Fri, 18.03.11 13:52, Andrey Borzenkov (arvidj...@mail.ru) wrote:
> > I tried to create a hotplug.target(which is activated after
> > default.target), and made udev-settle reside at it, this rendered a
> > unbootable system. systemd depends on udev at early time.
> > Thoughts: devtmpfs is mounte
On Fri, 18.03.11 13:40, Gustavo Sverzut Barbieri (barbi...@profusion.mobi)
wrote:
>
> On Fri, Mar 18, 2011 at 10:52 AM, Andrey Borzenkov wrote:
> > On Fri, Mar 18, 2011 at 12:35 PM, fykc...@gmail.com
> > wrote:
> >> Hi all,
> >>
> >> We did a series boot-time tests of systemd, and found some
On Wed, 30.03.11 02:28, fykc...@gmail.com (fykc...@gmail.com) wrote:
>
> 2011/3/29 Lennart Poettering :
> > On Tue, 29.03.11 03:36, fykc...@gmail.com (fykc...@gmail.com) wrote:
> >> To make boot fast, it seems udev's coldplug do too much jobs -- what I
> >> expect is only coldplug local block dev
2011/4/20 Lennart Poettering
>
> On Thu, 14.04.11 17:34, fykc...@gmail.com (fykc...@gmail.com) wrote:
>
> > diff --git a/src/missing.h b/src/missing.h
> > index 35e209f..b367831 100644
> > --- a/src/missing.h
> > +++ b/src/missing.h
> > @@ -125,7 +125,12 @@ static inline int fanotify_init(unsigned
On Wed, 20.04.11 09:15, fykc...@gmail.com (fykc...@gmail.com) wrote:
>
> 2011/4/20 Lennart Poettering
> >
> > On Thu, 14.04.11 17:34, fykc...@gmail.com (fykc...@gmail.com) wrote:
> >
> > > diff --git a/src/missing.h b/src/missing.h
> > > index 35e209f..b367831 100644
> > > --- a/src/missing.h
>
2011/4/20 Lennart Poettering :
> On Wed, 20.04.11 09:15, fykc...@gmail.com (fykc...@gmail.com) wrote:
>
>>
>> 2011/4/20 Lennart Poettering
>> >
>> > On Thu, 14.04.11 17:34, fykc...@gmail.com (fykc...@gmail.com) wrote:
>> >
>> > > diff --git a/src/missing.h b/src/missing.h
>> > > index 35e209f..b36
> -Original Message-
> From: Lennart Poettering [mailto:lenn...@poettering.net]
> Sent: Wednesday, April 20, 2011 2:33 AM
> To: Michael Biebl
> Cc: Mike Kazantsev; systemd-devel@lists.freedesktop.org; Rainer
> Gerhards
> Subject: Re: [systemd-devel] rsyslog drops messages in debug mode
>
>
Hello.
After upgrade to systemd-24 my sshd.socket after some time die.
netstat -nal | grep 22 says nothing.
systemctl status sshd.socket says:
Active: failed
Accepted: 2652 Connected:1
In mesages:
getty@tty1.service holdoff timer over, scheduling restart.
sshd@188.127.24148:22-85.142.60.148:33
I'm use cloudfuse module to access remote storage.
If i mount -a after system booted in multi-user.target all work's fine
But automount in boot process not work:
[5.629611] <27>systemd[1]: Failed to initialize automounter: No such
file or directory
/etc/fstab:
cloudfuse /mn
46 matches
Mail list logo
