When an unit is called via udev rules like below, only first 'online'
works correctly. Even if 'offline' event has happen, device and its
relative data still exists inside systemd, then following online
events will be ignored since systemd thinks it's already done. The
device and its relatives sh
On Thu, Aug 22, 2013 at 09:00:21AM -0400, Michael Duvall wrote:
> Hello,
>
> First time to post here. I'm studying systemd.
>
> Where are the options "--switched-root" and "--deserialize 20" to
> systemd documented? If undocumented, a brief explanation of each will
> be greatly appreciated.
Hi,
Hi *
I decided to remove completely syslog daemon from my Arch based server
(my Arch is at 3.3.8 kernel level).
I manages so far all units so kicking journalctl shows output from all
units but there is no messages from kernel boot phase.
When I look on journal output in Fedora19 - kernel boot me
2013/9/6 Ross Burton :
> If the administrator disables systemd-binfmt it can't be re-enabled correctly
Not a perfect solution, but you could just mask|unmask the service.
And as already mentioned, either we remove the static symlinks (so the
service is no longer enabled by default) or keeping the
On 09/06/2013 01:53 PM, Warpme wrote:
> Hi *
> I decided to remove completely syslog daemon from my Arch based server
> (my Arch is at 3.3.8 kernel level).
> I manages so far all units so kicking journalctl shows output from all
> units but there is no messages from kernel boot phase.
> When I look
On Fri, Sep 6, 2013 at 5:32 PM, Burton, Ross wrote:
> On 6 September 2013 15:50, Zbigniew Jędrzejewski-Szmek
> wrote:
>> On Fri, Sep 06, 2013 at 03:19:47PM +0100, Ross Burton wrote:
>>> If the administrator disables systemd-binfmt it can't be re-enabled
>>> correctly
>>> because there is no [Ins
On 6 September 2013 15:50, Zbigniew Jędrzejewski-Szmek
wrote:
> On Fri, Sep 06, 2013 at 03:19:47PM +0100, Ross Burton wrote:
>> If the administrator disables systemd-binfmt it can't be re-enabled correctly
>> because there is no [Install] block, the symlinks to sysinit being created at
>> install
On Fri, Sep 06, 2013 at 04:50:49PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Sep 06, 2013 at 03:19:47PM +0100, Ross Burton wrote:
> > If the administrator disables systemd-binfmt it can't be re-enabled
> > correctly
> > because there is no [Install] block, the symlinks to sysinit being c
On Fri, Sep 06, 2013 at 03:19:47PM +0100, Ross Burton wrote:
> If the administrator disables systemd-binfmt it can't be re-enabled correctly
> because there is no [Install] block, the symlinks to sysinit being created at
> install time manually. Add an Install block so that the those symlinks can
If the administrator disables systemd-binfmt it can't be re-enabled correctly
because there is no [Install] block, the symlinks to sysinit being created at
install time manually. Add an Install block so that the those symlinks can be
re-created using systemctl, and a dependency on the automounter
In some situations it is desirable to set the fsck fix level from "-a"
to "-y". This for instance might be a reasonable decision on embedded
systems where a user dealing with emergency mode is not available and
we prefer the risk of destroying the file system by an incorrect fsck
action over the r
Hi,
I think we should remove all recommendations to use -x for bug
reports. Generic explanations are not useful one you know the bug
messages, and those addtional like make the text much harder to read.
Users may continue to use -x while reading logs, of course.
Zbyszek
_
On 09/04/2013 03:27 PM, Andrew Cook wrote:
> Make a best-effort attempt to store information about crashes during
> failure, currently if these are encountered the crash is completely
> silenced.
>
> ideally coredumpctl would show if a coredump is available.
>
> ---
> src/journal/coredump.c | 7
On 09/04/2013 03:27 PM, Andrew Cook wrote:
> Currently this check happens when the coredump has been collected in
> it's entirety and being received by journald. this is not ideal
> behaviour when the crashing process is consuming significant percentage
> of physical memory such as a large instance
On 09/04/2013 02:12 PM, George McCollister wrote:
> d_name is modified on line 227 so if the entire journal name is needed
> again p must be used. Before this change when journal_file_empty was called
> on archived journals it would always return with -2.
>
> Signed-off-by: George McCollister
> -
On 09/04/2013 02:12 PM, George McCollister wrote:
> Before my previous patch, journal_file_empty wasn't be called with the
> correct filename. Now that it's being called with the correct filename
> it leaks file descriptors. This patch closes the file descriptors before
> returning.
>
> Signed-off
16 matches
Mail list logo
