Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 232684 - need initscripts for Solaris
Summary: need initscripts for Solaris
Alias: None
Product: 389
Classification: Retired
Component: Directory Server
Version: 7.1
Hardware: sparc
OS: Other
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
Depends On:
Blocks: FDS1.1.0
TreeView+ depends on / blocked
Reported: 2007-03-16 16:50 UTC by Rich Megginson
Modified: 2015-12-07 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-12-07 16:51:16 UTC

Attachments (Terms of Use)
diffs (deleted)
2007-03-16 16:52 UTC, Rich Megginson
no flags Details | Diff

Description Rich Megginson 2007-03-16 16:50:59 UTC
We need the init.d and rcX.d initscripts for Solaris.

Comment 1 Rich Megginson 2007-03-16 16:52:41 UTC
Created attachment 150248 [details]

Comment 2 Rich Megginson 2007-03-16 20:31:32 UTC
Resolves: bug 232684
Description: need initscripts for Solaris
Reviewed by: nhosoi (Thanks!)
Fix Description: I was able to mostly use the linux initscript.  The biggest
issue was that Solaris does not support bash for init scripts, so I had to
convert all of the bash-isms to just use plain old Bourne shell syntax.  I
removed the grep for the pids and just used kill -0, so I don't need the pids
list or pidof anymore.  Solaris mounts /var/run in tmpfs (i.e. memory disk)
which is removed upon reboot, so we have to create and set permission on
/var/run if it doesn't exist.  Solaris also doesn't provide a library of useful
shell functions, so I had to define success() and failure() if they don't exist.
Platforms tested: Solaris 9
Flag day: no
Doc: Yes - we will need to document the init scripts.

Checking in;
/cvs/dirsec/ldapserver/wrappers/,v  <--
new revision: 1.4; previous revision: 1.3

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