Bug 75791 - error messages running postgresql SysV init script
error messages running postgresql SysV init script
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: postgresql (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Lane
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-12 10:25 EDT by Chris Ricker
Modified: 2013-07-02 22:59 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-14 15:10:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2002-10-12 10:25:16 EDT
When I start postgresql the first time, I get the error message "stdin:  is not
a tty"

	
[root@peppy data]# /etc/init.d/postgresql start
Initializing database: stdin: is not a tty

                                                           [  OK  ]
Starting postgresql service: stdin: is not a tty

                                                           [  OK  ]
[root@peppy data]#
Comment 1 Chris Ricker 2002-10-12 10:31:01 EDT
Actually, it does this on all postgresql start / stops, not just the first

[root@peppy data]# /etc/init.d/postgresql start
Starting postgresql service: stdin: is not a tty
                                                           [  OK  ]
[root@peppy data]# 

I'm ssh'ed into peppy as a normal user, then su - to root
Comment 2 Andrew Overholt 2003-03-04 12:36:17 EST
Assigning to me.
Comment 3 Andrew Overholt 2003-03-12 17:56:35 EST
Reassigning.
Comment 4 Tom Lane 2005-01-14 15:10:55 EST
I've never seen this happen, so I'm going to close it as WORKSFORME.
Feel free to reopen if you can provide info on how to reproduce it.

Note You need to log in before you can comment on or make changes to this bug.