Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start-stop script for superserver on Linux does not always stop service [CORE1589] #2009

Closed
firebird-automations opened this issue Nov 13, 2007 · 11 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Emil Totev (emilt)

Attachments:
firebird

The script in /etc/init.d/firebird is not able to stop the firebird superserver service when it has been started at system startup.
This is because the name of the pidfile is generated using `basename $0`, but the script also exists with a different name in the rcn.d directories.

Also the script doesn't show any indication for failure / success. The script is supposed to support multiple firebird instances, but `service status firebird` will show the pids of all the running fbservers regardless of the service name.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Emil Totev (emilt)

This is a working start-stop script for Firebird 2 superserver on linux, supporting multiple firebird instances. It is tested on CentOS 4 based system and uses several simple RedHat specific functions.

@firebird-automations
Copy link
Collaborator Author

Modified by: Emil Totev (emilt)

Attachment: firebird [ 10660 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Emil, what were the reasons to replace:
1) daemon with runuser
2) fbmgr with fbmgr.bin
?

@firebird-automations
Copy link
Collaborator Author

Commented by: Emil Totev (emilt)

I had to use fbmgr.bin, because fbmgr is a shell script overriding $FIREBIRD with the default /opt/firebird and then starting fbmgr.bin.

Similarly, on my system 'daemon' somehow doesn't pass the environment properly, so it still looks for /opt/firebird. Apart from the numerous checks, my 'daemon' is starting the service effectively with

initlog -c "runuser -s /bin/bash - $user -c \"$*\""

I assumed that initlog is the guilty one and tried without it - and it worked.

You can also contact me directly if I can be of more help

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Patch is commited, same changes are done in start scripts (generic, slackware, gentoo) I could test myself.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 RC1 [ 10201 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 13404 ] => Firebird [ 14038 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment