16.10.2014 01:41, Anatol Pomozov wrote:
True. module name should be enough. In this case to debug the issue user needs:
- disable failing udev rule (or blacklist module?)
- reboot, it will let the user get into shell
- modprobe the failing module
- use sysrq-trigger to get more informatio
Hi
On Fri, Oct 10, 2014 at 3:45 PM, Tom Gundersen wrote:
> On Fri, Oct 10, 2014 at 11:54 PM, Anatol Pomozov
> wrote:
>> 1) Why not to make the timeout configurable through config file? There
>> is already udev.conf you can put config option there. Thus people with
>> modprobe issues can easily "
I'm responding here only to the systemd list.
On Tue, Oct 14, 2014 at 4:35 PM, Martyn Russell wrote:
> Another option would be to use systemd. However, I am mindful that it's not
> available everywhere just yet (but soon will be I hear) I am also aware, I
> might get a biased answer here :)
syst
---
src/resolve/resolved.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/resolve/resolved.c b/src/resolve/resolved.c
index ef416e5..d612938 100644
--- a/src/resolve/resolved.c
+++ b/src/resolve/resolved.c
@@ -26,6 +26,7 @@
#include "resolved-manager.h"
#include "resolved-conf.h"
+#in
On 10/15/2014 10:46 AM, Jan Synacek wrote:
> ---
> man/systemd.service.xml | 6 +++---
> man/systemd.socket.xml | 2 +-
> man/systemd.swap.xml| 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
Applied, thanks!
>
> diff --git a/man/systemd.service.xml b/man/systemd.service.xml
> ind
Mantas Mikulėnas writes:
> On Oct 15, 2014 12:07 PM, "Jan Synacek" wrote:
>>
>> Hello,
>>
>> in the documentation for systemd.service, under Type= option, it reads:
>>
>> Behavior of oneshot is similar to simple; however, it is expected that
> the
>> process has to exit before systemd starts
On Oct 15, 2014 12:07 PM, "Jan Synacek" wrote:
>
> Hello,
>
> in the documentation for systemd.service, under Type= option, it reads:
>
> Behavior of oneshot is similar to simple; however, it is expected that
the
> process has to exit before systemd starts follow-up unit
RemainAfterExit=
> i
Hello,
in the documentation for systemd.service, under Type= option, it reads:
Behavior of oneshot is similar to simple; however, it is expected that the
process has to exit before systemd starts follow-up unit RemainAfterExit=
is particularly useful for this type of service. This is the im
I would like to discuss the state of systemd scalability on dense/large
systems.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
---
man/systemd.service.xml | 6 +++---
man/systemd.socket.xml | 2 +-
man/systemd.swap.xml| 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 50ff2f5..b9604b8 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.ser
On Mon, Oct 13, 2014 at 05:14:24PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Oct 13, 2014 at 04:57:12PM +0200, Michal Sekletar wrote:
> > Before returning from function we should reset ret to NULL, thus cleanup
> > function is nop.
> >
> > Also context_str() returns pointer to a string c
On 10/14/2014 04:13 PM, Lukasz Skalski wrote:
> ---
> src/bus-proxyd/bus-proxyd.c | 12 ++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
Applied, thanks!
> diff --git a/src/bus-proxyd/bus-proxyd.c b/src/bus-proxyd/bus-proxyd.c
> index 52498f3..6ff0e8c 100644
> --- a/src/bus-proxy
12 matches
Mail list logo
