Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On Thu, Nov 11, 2010 at 12:49:11PM +0100, Michael Biebl wrote: > > We can ask, but it has been that way for at least a decade so I'm > > guessing it's unlikely to be changed now. See this Debian bug from > > 2001, marked wontfix. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=117596 > I personally don't know the history of agetty resp. getty. [1] > But if we want the declare the getty implementation within util-linux as > sort-of > the default, being bold and claiming the name "getty" might actually be a > good idea. After a bit more digging: back in the distant past, there was an agetty package in Debian. Rather than hijacking the name, we renamed agetty in util-linux. Given that the package was removed from Debian sometime before 2001, I have no issue with delivering agetty as a hardlink to getty (and therefore vice-versa). That will remain so for the next eternity. That is, I have no intention of removing the copy called 'getty', for reasons of not wanting to have to kill myself after the installed base screams. I'll add it now and it should land post-squeeze. lamont ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-remount-api-vfs fails for me
On Thu, 11.11.10 11:01, Kay Sievers (kay.siev...@vrfy.org) wrote: > > What's wrong? > > It's a bug in the systemd filter list. systemd has a list of stuff to > ignore, along with the API filesystems it uses itself. The > remount-api-vfs tool uses the entire list, so this goes wrong with > /proc/bus/usb. I'll look into it. Just a small update on this: Kay has now fixed this issue in systemd git. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On Thu, 11.11.10 14:06, Andreas Jaeger (a...@novell.com) wrote: > > On Thursday 11 November 2010 12:50:44 Kay Sievers wrote: > > [...] > > > Anyway, the point of this was only to have getty start late(ish) in > > > the boot process, after most of the other services that are pulled in > > > by multi-user.target. Maybe there is a better way to specify this, if > > > not everyone has rc.local? > > > > Yeah, others asked for that too. So far, we don't really have a > > concept of 'late' or 'last' in systemd. > > Yes, we had this in openSUSE as well the $ALL target to have the firewall > called at the end so that it could handle services with dynamic ports. > For details see https://bugzilla.novell.com/show_bug.cgi?id=652608 Can't say I like this approach to firewalls. Matching against ports is a thing of the past. They firewall people should match against processes, that's the only remotely sensible thing and then all of this would not be necessary. I am really not a big fan of Suse's $ALL extension. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On Thu, 11.11.10 12:50, Kay Sievers (kay.siev...@vrfy.org) wrote: > > Anyway, the point of this was only to have getty start late(ish) in > > the boot process, after most of the other services that are pulled in > > by multi-user.target. Maybe there is a better way to specify this, if > > not everyone has rc.local? > > Yeah, others asked for that too. So far, we don't really have a > concept of 'late' or 'last' in systemd. I don't think such a concept would even make sense. If you order more than once service as "last", then how would they ordered against each other? We already have something remotely similar: if you want stuff to be run after multi-user.target is reached (instead of 'before') then you can just add an After=multi-user.target into the unit files. By default all services pulled in from multi-user.target via Wants= or .wants/ will implicitly gain a Before=multi-user.target, which however is disabled if you by hand add After=multi-user.target instead. That said, I do believe that using this is really a bad idea and people should instead really sort their stuff after the services they really mean. Placeholders for "everything" is just a dead-end. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On Thu, 11.11.10 21:39, Andrew Edmunds (andrew.edmu...@yahoo.com.au) wrote: > Kay, Lennart, > > Kay Sievers wrote: > > Michael, any chance to check if it's possible to avoid the mangling of > > common util-linux tool names, and get a symlink in Debian package? > > After that we can drop the ifdef stuff here. > > We can ask, but it has been that way for at least a decade so I'm > guessing it's unlikely to be changed now. See this Debian bug from > 2001, marked wontfix. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=117596 > > The Debian position actually seems quite logical to me. Why do Fedora > (and SUSE?) need to ship two different versions of getty and hence > call one of them "alternate getty"? Other people seem to manage quite > well with only one. On Fedora and Suse there is no getty, only an agetty (and mingetty, but we are phasing that one out too). Upstream and almost all distros call the binary agetty. Only Debian renames it to getty. Due to that I think it is smarter and easier to have Debian change back to the upstream name then have everybody else follow Debians deviation from upstream. But then again I must admit that the name "getty" is nicer and more appropriate than "agetty", but that doesn't really matter does it? > > Hmm, I'd very much prefer if those distros would upgrade their u-l-ng > > patches instead. > > I'm sure they will, and I was only suggesting this as a temporary fix > to be removed again later. Without "-s", you may need to press Break > to get the correct baud rate but at least a serial console is usable. > With the "-s", getty just gives a "Usage:" error and respawns > continuously so the serial console is completely non-functional as > things stand. Maybe as long as the u-l-ng version in Debian/Ubuntu isn't updated it might make sense to include a patch to this in the package? I really would like to gently pressure downstream to upgrade u-l-ng, so that we don't have to carry around compat kludges upstream all the time. > >> Is there a reason why this applies only to Fedora and Arch? It seems > >> > appropriate for all users as far as I can see. > > > > Only Fedora and Arch have rc.local. If you ask me rc.local is something > > that should just die, hence I am very reluctant to support it on any > > more distros than we currently support it on. > > Not so. Here are the contents of /etc/rc.local on an Ubuntu system. > I believe this file comes straight from Debian. Hmm, if that's the case, then the units/debian subdir should probably have a service file for this, and we can include this extra ifdef. > Anyway, the point of this was only to have getty start late(ish) in > the boot process, after most of the other services that are pulled in > by multi-user.target. Maybe there is a better way to specify this, if > not everyone has rc.local? Well, since we start everything in parallel and without waiting there isn't really a point in time where we know we finished start-up. Such a point simply does not exist. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] man: Fix various typos
On Thu, Nov 11, 2010 at 13:30, Andrew Edmunds wrote: > man/systemd.exec.xml | 19 ++- > man/systemd.service.xml | 6 +++--- > man/systemd.unit.xml | 2 +- > man/systemd.xml | 12 ++-- > 4 files changed, 20 insertions(+), 19 deletions(-) Applied. Thanks. Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On 11.11.2010 12:39, Andrew Edmunds wrote: > Kay, Lennart, > > Kay Sievers wrote: >> Michael, any chance to check if it's possible to avoid the mangling of >> common util-linux tool names, and get a symlink in Debian package? >> After that we can drop the ifdef stuff here. > > We can ask, but it has been that way for at least a decade so I'm > guessing it's unlikely to be changed now. See this Debian bug from > 2001, marked wontfix. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=117596 > > The Debian position actually seems quite logical to me. Why do Fedora > (and SUSE?) need to ship two different versions of getty and hence > call one of them "alternate getty"? Other people seem to manage quite > well with only one. I personally don't know the history of agetty resp. getty. [1] But if we want the declare the getty implementation within util-linux as sort-of the default, being bold and claiming the name "getty" might actually be a good idea. Regards, Michael [1] e.g. I didn't know that a stands for alternate -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On Thursday 11 November 2010 12:50:44 Kay Sievers wrote:
> [...]
> > Anyway, the point of this was only to have getty start late(ish) in
> > the boot process, after most of the other services that are pulled in
> > by multi-user.target. Maybe there is a better way to specify this, if
> > not everyone has rc.local?
>
> Yeah, others asked for that too. So far, we don't really have a
> concept of 'late' or 'last' in systemd.
Yes, we had this in openSUSE as well the $ALL target to have the firewall
called at the end so that it could handle services with dynamic ports.
For details see https://bugzilla.novell.com/show_bug.cgi?id=652608
Andreas
--
Andreas Jaeger, Program Manager openSUSE, a...@{novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Trying systemd in Fedora 14
On 11/11/2010 12:03 AM, Lennart Poettering wrote: On Wed, 03.11.10 11:03, Felix Braun (felix.br...@mail.mcgill.ca) wrote: Hi there, heya, while systemd wasn't chosen as a default init system for F14, it is included in the repositories. That way, it was argued, more people could give it a try and potentially discover shortcomings before it would be made the default. I would like to give systemd a spin and have installed it in my fresh Fedora system. However, bootup is still seems to be handled by upstart after installation. I have not been able to find installation information in the man pages or on systemd's web presence. How do I transfer control to systemd? Changing init=xxx in grub.conf? Do I need to pass any other arguments on the kernel command line? At this point we only really maintain systemd for F15. It's too much work for us to maintain it for two distributions at the same time, especially since systemd requires deep integration into the system. Also, bug reports against the old systemd version in F14 are only of limited use to us. My recommendation to test systemd is to upgrade to F15. I have been running it for a while now, and while it is a bumpy ride it generally works. Sorry if this is disappointing, Lennart I had success with: # yum --enablerepo=rawhide update udev systemd initscripts ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] man: Fix various typos
man/systemd.exec.xml| 19 ++- man/systemd.service.xml |6 +++--- man/systemd.unit.xml|2 +- man/systemd.xml | 12 ++-- 4 files changed, 20 insertions(+), 19 deletions(-) diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 51dcdcd..7c8005c 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -127,7 +127,7 @@ be specified more than once in which case all listed groups are set as supplementary groups. This option does -not override but extend the list of +not override but extends the list of supplementary groups configured in the system group database for the user. @@ -301,10 +301,11 @@ below) and the executed process becomes the controlling process of the terminal. If the terminal is already -being controlled by another process it -is waited until that process releases -the -terminal. tty-force +being controlled by another process the +executed process waits until the current +controlling process releases the +terminal. +tty-force is similar to tty, but the executed process is forcefully and immediately made the controlling @@ -500,15 +501,15 @@ TimerSlackNSec= Sets the timer slack in nanoseconds for the executed -processes The timer slack controls the +processes. The timer slack controls the accuracy of wake-ups triggered by timers. See prctl2 for more information. Note that in contrast to most other time span -definitions this value is takes a -nano-seconds integer and does not -understand any other +definitions this parameter takes an +integer value in nano-seconds and does +not understand any other units. diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 2db146b..c77992d 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -427,7 +427,7 @@ Restart= Configures whether the main service process shall be -restarted when it exists. Takes one of +restarted when it exits. Takes one of no, on-success, on-failure, @@ -557,7 +557,7 @@ group and the control group continues to exist after stop unless it is empty. Defaults to -control-croup. +control-group. Processes will first be terminated via SIGTERM. If then after @@ -597,7 +597,7 @@ main or all. If none no daemon status -updates are accepted by the service +updates are accepted from the service processes, all status update messages are ignored. If main only service updates sent from the diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 4e1d9f3..34f4bab 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -602,7 +602,7 @@ must either be a single word, or an assignment (i.e. two words, seperated by the equality sign). In the former -case the kernel command line is search +case the kernel command line is searched
Re: [systemd-devel] systemd-remount-api-vfs fails for me
On Thursday 11 November 2010 11:01:21 Kay Sievers wrote:
> On Thu, Nov 11, 2010 at 10:34, Andreas Jaeger wrote:
> > I noticed for some time that systemd-remount-api-vfs is in the failed
> > state and found now the following in the log files
> >
> > <4>[3.063357] systemd[1]: systemd 11 running in system mode. (+PAM
> > +LIBWRAP +AUDIT +SELINUX +SYSVINIT; suse) <4>[3.142518] systemd[1]:
> > Set hostname to .
> > <4>[4.598928] systemd-remount-api-vfs[467]: /bin/mount for
> > /proc/bus/usb exited with exit status 32. <4>[4.603561]
> > systemd-remount-api-vfs[467]: mount: /proc/bus/usb not mounted already,
> > or bad option <4>[4.620621] systemd[1]:
> > systemd-remount-api-vfs.service: main process exited, code=exited,
> > status=1 <4>[4.634045] systemd[1]: Unit
> > systemd-remount-api-vfs.service entered failed state.
> >
> > My fstab contains:
> > usbfs/proc/bus/usbusbfs noauto
> > 0 0
> >
> > What's wrong?
>
> It's a bug in the systemd filter list. systemd has a list of stuff to
> ignore, along with the API filesystems it uses itself. The
> remount-api-vfs tool uses the entire list, so this goes wrong with
> /proc/bus/usb. I'll look into it.
>
> Unrelated to that, usbfs is deprecated since long, we even disabled it
> in the SUSE kernel, in think. You still need that for something?
I don't need it - and it's noauto, so it should not get mounted at all ;)
Andreas
--
Andreas Jaeger, Program Manager openSUSE, a...@{novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On Thu, Nov 11, 2010 at 12:39, Andrew Edmunds wrote: > Kay Sievers wrote: >> Michael, any chance to check if it's possible to avoid the mangling of >> common util-linux tool names, and get a symlink in Debian package? >> After that we can drop the ifdef stuff here. > > We can ask, but it has been that way for at least a decade so I'm > guessing it's unlikely to be changed now. See this Debian bug from > 2001, marked wontfix. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=117596 > > The Debian position actually seems quite logical to me. Why do Fedora > (and SUSE?) need to ship two different versions of getty and hence > call one of them "alternate getty"? Other people seem to manage quite > well with only one. We have only agetty from util-linux, there is no getty here. >>> Is there a reason why this applies only to Fedora and Arch? It seems >>> > appropriate for all users as far as I can see. >> >> Only Fedora and Arch have rc.local. If you ask me rc.local is something >> that should just die, hence I am very reluctant to support it on any >> more distros than we currently support it on. /etc/rc.local should not be in the default setup, it's legacy only some distros did, and it does not make much sense in the systemd context, especially not to run an empty shell script. :) > Anyway, the point of this was only to have getty start late(ish) in > the boot process, after most of the other services that are pulled in > by multi-user.target. Maybe there is a better way to specify this, if > not everyone has rc.local? Yeah, others asked for that too. So far, we don't really have a concept of 'late' or 'last' in systemd. Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
Kay, Lennart, Kay Sievers wrote: > Michael, any chance to check if it's possible to avoid the mangling of > common util-linux tool names, and get a symlink in Debian package? > After that we can drop the ifdef stuff here. We can ask, but it has been that way for at least a decade so I'm guessing it's unlikely to be changed now. See this Debian bug from 2001, marked wontfix. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=117596 The Debian position actually seems quite logical to me. Why do Fedora (and SUSE?) need to ship two different versions of getty and hence call one of them "alternate getty"? Other people seem to manage quite well with only one. Lennart Poettering wrote > 2. serial-ge...@.service.m4 invokes agetty with option "-s", which >> seems to have been recently added to agetty at Lennart's request. >> getty on Debian/Ubuntu doesn't have that option yet and I would >> guess that other distros may be in the same position. Since ifdefs >> are needed here anyway, it would be nice to apply that option only >> to the distros where it currently works. > > Hmm, I'd very much prefer if those distros would upgrade their u-l-ng > patches instead. I'm sure they will, and I was only suggesting this as a temporary fix to be removed again later. Without "-s", you may need to press Break to get the correct baud rate but at least a serial console is usable. With the "-s", getty just gives a "Usage:" error and respawns continuously so the serial console is completely non-functional as things stand. >> Is there a reason why this applies only to Fedora and Arch? It seems >> > appropriate for all users as far as I can see. > > Only Fedora and Arch have rc.local. If you ask me rc.local is something > that should just die, hence I am very reluctant to support it on any > more distros than we currently support it on. Not so. Here are the contents of /etc/rc.local on an Ubuntu system. I believe this file comes straight from Debian. $ cat /etc/rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. exit 0 Anyway, the point of this was only to have getty start late(ish) in the boot process, after most of the other services that are pulled in by multi-user.target. Maybe there is a better way to specify this, if not everyone has rc.local? Regards, -- Andrew Edmunds andrew.edmu...@yahoo.com.au ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] ge...@.service.m4 and serial-ge...@.service.m4
On Thu, Nov 11, 2010 at 00:37, Lennart Poettering wrote: > On Wed, 03.11.10 22:49, Andrew Edmunds (andrew.edmu...@yahoo.com.au) wrote: >> A few points about these two source files. >> >> 1. ge...@.service.m4 has: >> > m4_ifdef(`TARGET_FEDORA', `m4_define(`GETTY', `/sbin/agetty 38400')')m4_dnl >> > m4_ifdef(`TARGET_SUSE', `m4_define(`GETTY', `/sbin/agetty 38400')')m4_dnl >> > m4_ifdef(`TARGET_DEBIAN', `m4_define(`GETTY', `/sbin/getty 38400')')m4_dnl >> > m4_ifdef(`TARGET_UBUNTU', `m4_define(`GETTY', `/sbin/getty 38400')')m4_dnl >> > m4_ifdef(`TARGET_GENTOO', `m4_define(`GETTY', `/sbin/agetty 38400')')m4_dnl >> > m4_ifdef(`TARGET_ARCH', `m4_define(`GETTY', `/sbin/agetty -8 >> > 38400')')m4_dnl >> >> This code should be duplicated into serial-ge...@.service.m4, or >> pulled out into configure.ac so that it can be used by both units. >> Currently serial-ge...@.service tries to invoke /sbin/agetty on >> Debian/Ubuntu, which doesn't exist. > > Fixed this now. Ideally Debian/Ubuntu would stop renaming agetty like > this, or at least do it via symlink only. I'd love to get rid of the > differences between the distros here. Michael, any chance to check if it's possible to avoid the mangling of common util-linux tool names, and get a symlink in Debian package? After that we can drop the ifdef stuff here. Thanks, Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-remount-api-vfs fails for me
On Thu, Nov 11, 2010 at 10:34, Andreas Jaeger wrote: > > I noticed for some time that systemd-remount-api-vfs is in the failed state > and found now the following in the log files > > <4>[ 3.063357] systemd[1]: systemd 11 running in system mode. (+PAM > +LIBWRAP +AUDIT +SELINUX +SYSVINIT; suse) > <4>[ 3.142518] systemd[1]: Set hostname to . > <4>[ 4.598928] systemd-remount-api-vfs[467]: /bin/mount for /proc/bus/usb > exited with exit status 32. > <4>[ 4.603561] systemd-remount-api-vfs[467]: mount: /proc/bus/usb not > mounted already, or bad option > <4>[ 4.620621] systemd[1]: systemd-remount-api-vfs.service: main process > exited, code=exited, status=1 > <4>[ 4.634045] systemd[1]: Unit systemd-remount-api-vfs.service entered > failed state. > > My fstab contains: > usbfs /proc/bus/usb usbfs noauto 0 0 > > What's wrong? It's a bug in the systemd filter list. systemd has a list of stuff to ignore, along with the API filesystems it uses itself. The remount-api-vfs tool uses the entire list, so this goes wrong with /proc/bus/usb. I'll look into it. Unrelated to that, usbfs is deprecated since long, we even disabled it in the SUSE kernel, in think. You still need that for something? Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-remount-api-vfs fails for me
I noticed for some time that systemd-remount-api-vfs is in the failed state and
found now the following in the log files
<4>[3.063357] systemd[1]: systemd 11 running in system mode. (+PAM +LIBWRAP
+AUDIT +SELINUX +SYSVINIT; suse)
<4>[3.142518] systemd[1]: Set hostname to .
<4>[4.598928] systemd-remount-api-vfs[467]: /bin/mount for /proc/bus/usb
exited with exit status 32.
<4>[4.603561] systemd-remount-api-vfs[467]: mount: /proc/bus/usb not
mounted already, or bad option
<4>[4.620621] systemd[1]: systemd-remount-api-vfs.service: main process
exited, code=exited, status=1
<4>[4.634045] systemd[1]: Unit systemd-remount-api-vfs.service entered
failed state.
My fstab contains:
usbfs/proc/bus/usbusbfs noauto0 0
What's wrong?
Andreas
--
Andreas Jaeger, Program Manager openSUSE, a...@{novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] Explain structure of tmpfiles.d
On Wednesday 10 November 2010 23:59:26 Lennart Poettering wrote:
> On Thu, 04.11.10 11:30, Andreas Jaeger (a...@novell.com) wrote:
> > IMO we should add an easy reference of the structure of tmpfiles.d files.
> > Here's a patch,
>
> I'd prefer not to maintain duplicates of the documentation at different
> places at the same time. Since we now have Brandon's man page I think it
> is nicer to simply include a reference to the man page in the .conf
> files. Which I now added in git.
>
> Hope that's acceptable to you.
Yes, perfectly fine for me - my goal is reached to have a reference and the
man page is the better solution.
Andreas
--
Andreas Jaeger, Program Manager openSUSE, a...@{novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] BTRFS bug with parallel mounts?
On Thursday, November 11, 2010, Mike Kazantsev wrote: > On Wed, 10 Nov 2010 15:52:51 -0200 > Gustavo Sverzut Barbieri wrote: > >> On Wed, Nov 10, 2010 at 2:11 PM, Greg KH wrote: >> > On Wed, Nov 10, 2010 at 01:02:51PM -0200, Gustavo Sverzut Barbieri wrote: >> >> On Wed, Nov 10, 2010 at 9:33 AM, Gustavo Sverzut Barbieri >> >> >> >> Part of the log (sorry, I had no way but to type it all): >> >> >> >> BUG: unable to handle kernel NULL pointer dereference at 0128 >> >> IP: [] btrfs_test_super+0xb/0x30 >> >> PGD: 26b5b1067 PUD 26a465067 PMD 0 >> >> last sysfs file: /sys/devices/virtual/bdi/btrfs-2/uevent >> >> CPU 0 >> >> Modules linked in: nvidia(P) lib80211_crypt_tkip wl(P) >> >> Pid: 434, comm: mount Tainted: P 2.6.36 #3 Mac-F22586C8/MacBookPro6,2 >> >> RIP: ... btrfs_test_super+0xb/0x30 >> > >> > Sounds like a btrfs issue, have you contacted those developers? >> >> No, I just mailed systemd as people (kay?) seems to be using it, at >> least I saw people here advertising its usage, even the readahead have >> specific code, so maybe people had (or not) issues with it. >> >> Let's face that mounting multiple points simultaneously is not what >> one would expect. >> >> >> > Also, you really are going to have to be able to reproduce this without >> > the closed source kernel modules linked in (broadcom and nvidia) for >> > anyone to even be able to help you out. >> >> yeah, I'm pretty sure about that ;-) >> > > I can reliably reproduce the issue on my hardware and similar vm setup > with several btrfs mounts, activated during boot. > Kernel spits some backtrace into terminal, then, after a few seconds it > enters some kind of crazy endless error-loop, flooding terminal with > more backtraces. > Vanilla 2.6.36 kernel, no proprietary code. > > Since none of these mounts are critical to boot (I didn't trust btrfs > much at the time), I've worked around the issue by > comment=systemd.automount, so they got mounted after boot with systemd. > > I thought about reporting the issue when I've encountered it, but been > a bit busy adapting the system for systemd, so it kina slipped off my > mind. > Guess I'll get all these traces, clean my vm from possible private > stuff (I rsync it from a real machine) and report the setup to btrfs > maintainers in a few days. > Thanks for reminder! ;) I'd appreciate it as I'm going into a business trip without much spare time do do dev/testing. If possible, add me as mail/bugzilla CC -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
