On 02/18/2016 08:28 PM, Lennart Poettering wrote:
On Wed, 17.02.16 14:35, Avi Kivity (a...@scylladb.com) wrote:
We are using systemd to supervise our NoSQL database and are generally
happy.
Thank you for the feedback! We are always interested in good feedback
like yours.
A few things will
On 02/19/2016 03:24 PM, Michal Sekletar wrote:
On Fri, Feb 19, 2016 at 1:49 PM, Zbigniew Jędrzejewski-Szmek
wrote:
I don't think there's a way around the issue short of allowing
watchdog during startup. Databases which do long recovery are a bit
special, most programs don't exhibit this kind
On 02/17/2016 07:17 PM, systemd-devel-requ...@lists.freedesktop.org wrote:
3. watchdog during startup
Sometimes we need to perform expensive operations during startup
(log replay, rebuild from network replica) before we can start
serving. Rather than configure a huge start timeout, I'd prefer
On 02/17/2016 03:56 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Feb 17, 2016 at 02:35:55PM +0200, Avi Kivity wrote:
We are using systemd to supervise our NoSQL database and are
generally happy.
A few things will help even more:
1. log core dumps immediately rather than after the dump
We are using systemd to supervise our NoSQL database and are generally
happy.
A few things will help even more:
1. log core dumps immediately rather than after the dump completes
A database will often consume all memory on the machine; dumping 120GB
can take a lot of time, especially if compr
On 06/15/2011 12:17 PM, Avi Kivity wrote:
On 06/14/2011 06:17 PM, Lennart Poettering wrote:
On Mon, 06.06.11 16:01, Avi Kivity (a...@redhat.com) wrote:
> I have a system which was upgraded to F15 and thus systemd. During
> the boot process it times out starting various .device units
On 06/14/2011 06:17 PM, Lennart Poettering wrote:
On Mon, 06.06.11 16:01, Avi Kivity (a...@redhat.com) wrote:
> I have a system which was upgraded to F15 and thus systemd. During
> the boot process it times out starting various .device units, like
> sda1.device. If I let it alon
On 06/06/2011 07:17 PM, Michal Schmidt wrote:
On 06/06/2011 03:01 PM, Avi Kivity wrote:
I have a system which was upgraded to F15 and thus systemd. During the
boot process it times out starting various .device units, like
sda1.device.
A general advice: Always use stable names (UUID, LABEL
On 06/06/2011 07:25 PM, Kay Sievers wrote:
On Mon, Jun 6, 2011 at 17:58, Avi Kivity wrote:
> On 06/06/2011 06:47 PM, Kay Sievers wrote:
>> On Mon, Jun 6, 2011 at 15:01, Avi Kivitywrote:
>> >I have a system which was upgraded to F15 and thus systemd. Duri
On 06/06/2011 06:47 PM, Kay Sievers wrote:
On Mon, Jun 6, 2011 at 15:01, Avi Kivity wrote:
> I have a system which was upgraded to F15 and thus systemd. During the boot
> process it times out starting various .device units, like sda1.device. If I
> let it alone it will boot in abo
I have a system which was upgraded to F15 and thus systemd. During the
boot process it times out starting various .device units, like
sda1.device. If I let it alone it will boot in about a week or so, but
meanwhile it is unusable. I am able to start it up using
emergency.target and various h
11 matches
Mail list logo
