Displaying 4 results from an estimated 4 matches for "removeonstop".
2015 Aug 17
2
persistent change of max_stack_depth
...f the
>> service file, when I do I don't get my error from postgresql I see this
>> in /var/log/messages
>>
>> Aug 17 08:38:47 db1 systemd: Reloading.
>> Aug 17 08:38:47 db1 systemd:
>> [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue
>> 'RemoveOnStop' in section 'Socket'
>> Aug 17 08:38:47 db1 systemd:
>> [/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue
>> 'RemoveOnStop' in section 'Socket'
>> Aug 17 08:38:49 db1 systemd: Starting PostgreSQL 9.4 database server...
>> Aug 17...
2015 Aug 17
2
persistent change of max_stack_depth
...moving the 'LimitSTACK=12288' to other sections of the
service file, when I do I don't get my error from postgresql I see this
in /var/log/messages
Aug 17 08:38:47 db1 systemd: Reloading.
Aug 17 08:38:47 db1 systemd:
[/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue
'RemoveOnStop' in section 'Socket'
Aug 17 08:38:47 db1 systemd:
[/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue
'RemoveOnStop' in section 'Socket'
Aug 17 08:38:49 db1 systemd: Starting PostgreSQL 9.4 database server...
Aug 17 08:38:49 db1 kernel: postgresql94-ch[3021]...
2015 Aug 17
0
persistent change of max_stack_depth
...288' to other sections of the
> service file, when I do I don't get my error from postgresql I see this
> in /var/log/messages
>
> Aug 17 08:38:47 db1 systemd: Reloading.
> Aug 17 08:38:47 db1 systemd:
> [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue
> 'RemoveOnStop' in section 'Socket'
> Aug 17 08:38:47 db1 systemd:
> [/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue
> 'RemoveOnStop' in section 'Socket'
> Aug 17 08:38:49 db1 systemd: Starting PostgreSQL 9.4 database server...
> Aug 17 08:38:49 db1 kernel...
2015 Aug 14
4
persistent change of max_stack_depth
Hi Thomas,
> Could anybody point me in the right direction for setting the kernel
> parameter, max_stack_depth, to 10240 for database tuning?
>
> I have currently set it by running 'ulimit -s 10240' but this does not
> survive a reboot.
>
>
Thanks for the response, I've been nosing around that file recently but
noted the first two lines;
#This file sets the