| From: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-pkg-yum <pgsql-pkg-yum(at)postgresql(dot)org> |
| Subject: | possible init script issue |
| Date: | 2014-10-15 16:50:27 |
| Message-ID: | CABeG9Ltm5_sWfXEhqQnQMSLLvygROpo6GEFYsbx1sKiTL_Vp2w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
Hi all,
I was doing some maintenance on a server and discovered that if you
try using the SysV scripts to stop a postgres service that was started
by other means (pg_ctl the most common example) it won't stop it, but
will print a successful message.
The pg_ctl tool doesn't touch the lockfile from the sysV lock subsys,
but the SysV init script checks for the lock file first, but if it
doesn't find it it still echo_success.
Wouldn't it be wiser to echo_warning instead?
Cheers,
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Harris | 2014-10-16 07:10:15 | Centos 5 postgis2_92 packages |
| Previous Message | Adam Lanier | 2014-10-14 15:04:16 | question regarding ip4r93 for Scientific Linux 7 x86_64 |