similar to: systemd

> On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: >> I am trying to understand what After= means in a unit file. Does it >> mean after the specified target is up and operational or only that >> the target has been started? >> >> I have something that needs postgres but postgres needs to be >> operational not just started. Sometimes it can take a

On 01/09/2019 11:36 AM, Jonathan Billings wrote: > On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: >> I am trying to understand what After= means in a unit file. Does it >> mean after the specified target is up and operational or only that >> the target has been started? >> >> I have something that needs postgres but postgres needs to be >>

On 02/17/2016 08:10 AM, Michael H wrote: >> The easy answer is yes .. glibc requires so many things to be restarted, >> that is the best bet. Or certainly the easiest. >> >> Note: in CentOS 7, there is also a kernel update which is rated as >> Important .. so you should boot to that anyway: >>

On 02/17/2016 07:08 AM, Michael H wrote: > On 17/02/16 13:01, Johnny Hughes wrote: >> I normally just let the daily announce post to this list show what >> is available for updates, but there is a CVE (CVE-2015-7547) that >> needs a bit more attention which will be on today's announce list >> of updates. >> >> We released a new glibc yesterday for

> The easy answer is yes .. glibc requires so many things to be restarted, > that is the best bet. Or certainly the easiest. > > Note: in CentOS 7, there is also a kernel update which is rated as > Important .. so you should boot to that anyway: > https://lists.centos.org/pipermail/centos-announce/2016-February/021705.html > > Here is a good link to figure out what to

When I run the rake db:migrate command, I get this: C:\testror\depot>rake db:migrate --trace (in C:/testror/depot) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate rake aborted! 182: Le systÞme d''exploitation ne peut pas exÚcuter %1. - c:/ruby/ lib/ruby/gem

On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: > I am trying to understand what After= means in a unit file. Does it > mean after the specified target is up and operational or only that > the target has been started? > > I have something that needs postgres but postgres needs to be > operational not just started. Sometimes it can take a bit for > postgres to

Hi Jason, On 14/08/15 16:45, Jason Warr wrote: > On Fri, 2015-08-14 at 16:31 +0100, Michael H wrote: >> 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

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

I tried moving a PosgreSQL database to an external harddisk due to lack of space on the main harddisks. Not the ideal solution of course but it should work. However, on CentOS 7 the external harddisk is mounted under /run/media and the user. I copied the postgresql database directory and made sure it is owned recursively by postgres, changed the necessary settings in both the systemd unit and the

Hello Everybody, I am trying to configure Asterisk to listen into a database which is created in PostgreSQL. Whenever asterisk starts up, it is unable to connect to the pg database and gives the following error: [cdr_pgsql.so] => (PostgreSQL CDR Backend) == Parsing '/etc/asterisk/cdr_pgsql.conf': Found Jun 24 21:20:53 DEBUG[1074494336]: cdr_pgsql.c:284 my_load_module: cdr_pgsql:

On Oct 8, 2020, at 15:22, H <agents at meddatainc.com> wrote: > > ?I tried moving a PosgreSQL database to an external harddisk due to lack of space on the main harddisks. Not the ideal solution of course but it should work. However, on CentOS 7 the external harddisk is mounted under /run/media and the user. I copied the postgresql database directory and made sure it is owned

On 15 Apr 2015 13:22, "Dennis Jacobfeuerborn" <dennisml at conversis.de> wrote: > > On 15.04.2015 12:41, Alessandro Baggi wrote: > > Hi there, > > Yesterday I've updated from 7 to 7.1 and today I've noticed on 2 server > > that postgresql systemd file was replaced with default values. This make > > postgres to no start and webserver give me

Hello, I've been struggling with a problem for the past several weeks, trying to get PL/R (R procedural language handler for PostgreSQL, http://www.joeconway.com/plr/) to work on Red Hat 9. In brief, R dumps core during the embedded library initialization, while in Rf_regcomp(), working on on Rprofile. Below I've included the important parts of a backtrace: Program received signal

Me again! I have a recipe that looks like: class postgresql { file { pg_hba_conf: name => "/var/lib/pgsql/data/pg_hba.conf", source => "puppet://puppetmaster/files/workstations/common/var/lib/pgsql/data/pg_hba.conf", owner => postgres, group => postgres, mode => 600, subscribe => [ Package[postgresql] ],

Hello people... In the rails2.pdf Dave T says: Rails works with the DB2, MySQL, Oracle, Postgres,... The database drivers are all written in C and are primarily distributed in source form. Then he lists this site: http://ruby.scripting.ca/postgres/ Then he says, There is a pure-Ruby version of the Postgres adapter available. Download postgres-pr from the Ruby-DBI page at

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

Hi there, I''ve been trying for a few hours now to get RoR and postgresql talking - but I''m very confused about what''s going on (I''m running windows btw). I haven''t created a database in postgresql (I''m assuming that RoR will do that?) my database.yml looks like this: production: adapter: ruby-postgres database: rails_production

Signed-off-by: Joey Boggs <jboggs at redhat.com> --- installer/modules/ovirt/manifests/freeipa.pp | 8 ++++---- installer/modules/ovirt/manifests/postgres.pp | 12 ++++++------ 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/installer/modules/ovirt/manifests/freeipa.pp b/installer/modules/ovirt/manifests/freeipa.pp index e5de852..f91cd43 100644 ---

Hi there, Yesterday I've updated from 7 to 7.1 and today I've noticed on 2 server that postgresql systemd file was replaced with default values. This make postgres to no start and webserver give me problem. This problem was fixed and now all works good. It's normal that on major update I can get this problem? If so, I've ridden release change but I have not ridden about