Hello list,

I have several RedHat 9 boxes and am looking to transition to slackware. I already have one installation of slackware, but are a little unsure at to how to transition some things. For one, I have this postgresql startup script that relies on the /etc/init.d, /etc/init.d/functions, and /etc/sysconfig/network. Is there someone on this forum who would be willing to modify this script for me to work on slackware? Even some advice would be great.

Also, can anyone explain how startup scripts work in slackware? I'm used to the /etc/init.d/ directory and the /etc/rc.d/ driectories. How do you guys work around installers that are counting on these directories?

Thanks,
Meeble

Can't answer all of that, but take a look at the slackware book:

http://www.slackware.com/book/index....urce=c623.html

Go down to the section:
"The /etc/rc.d Directory"

Here is a very good FAQ about Slack:

http://wombat.san-francisco.ca.us/fa...c/cache/1.html

Here is good information regarding your question about Slackware startup scripts:

http://wombat.san-francisco.ca.us/fa.../cache/37.html

Let us know if that doesn't help you out.

A specific answer to your last question is to create the directories that something is expecting. For example, VMware wants an /etc/init.d and rcX.d directories under /etc. Just create them. Your Slackware system couldn't care less if they are there.

Also, you can read the comments in /etc/rc.d/rc.sysvinit to get more information.

hey flyfishin,

yeah, that helps me understand the BSD style startup scripts better thanks! BUT...
I still can't get my postgresql startup script to work because it references /etc/rc.d/init.d/functions
and /etc/sysconfig/network. If anyone has any ideas, I would be very thankfull. I will post
the startup script here:
http://web.absmot.com/postgresql.txt
if anyone wants to take a look at it...

thanks,
meeble

I don't have enough experience with bash scripting to quickly look at that script and modify it for Slackware. Plust I have no clue how you have Postgres installed on your box. Instead of fixing that one here is a much more maintainable one for Slackware, heck more maintainable for any platform.

#!/bin/sh

su - postgres -c "/pathtopostgresbindirectory/pg_ctl $1 -D /pathtopostgresdatadirectory -l
/pathtologfile"


This file is stored in /usr/local/sbin/lo_pg_ctl but you can put it wherever you desire and name it whatever you want. Then look at the rc.httpd that comes with Slackware. Replace the /usr/sbin/apachectl in that script with the path to the script above and save it as rc.postgresql and make it executable. Then modify rc.M and rc.6 to handle your new rc.postgresql script.