How do I start slapd at boot time in leopard?

Greeting,
  Forgive me if this is the wrong forum/community.
  I want to start slapd at boot time on my new leopard upgrade.  On tiger, it was as simple as having an LDAPSERVER=-YES- line in /etc/hostconfig.  That does not seem to work for leopard.  I can run slapd from the command line.  I needed to make changes to the slapd.conf tiger version and reload my database, but all is working fine.  I just have not been able to get the deamon to start at boot up.  It must be simple.  Any ideas?
  Thanks,
--Linn

Texas Mac Man,
  Thanks.  Slapd is the OpenLDAP daemon (server) delivered with MacOS, even Client.  No, starting at the user level is not what I need.  I can already do that in a terminal window with /usr/libexec/slapd, after I get su'ed to root.
  Think Unix, not iApps.  When the system boots up, there should be scripts available to start specific daemons.  I am looking for hints there.
BDAqua,
  Thanks.  I had seen that first discussion before.  It deals with slapd failing when it tries to start on MacOS Server... where all these daemons indeed start at boot time.  I am just trying to figure out how to do in leopard what I successfully did in tiger, namely start /usr/libexec/slapd at boot time.
  And note, this is not an issue with slapd failing due to slapd.conf or database problems.  All works fine from the user lever start.
  Thanks,
--Linn

Similar Messages

  • How do I start service at boot?

    Hello,
      I am relatively new to arch, so I have played with it since .3 on and off but never as a server.  Right now I can start mysql, httpd and exim just fine, but they don't seem to be starting up at boot time.  How do I fix this?
    Thanks,
    mrjohnston

    Hi mrjohnston,
    You have to add an entry for each daemon in the DAEMONS array in the file /etc/rc.conf.  If you add "exim" (for example) to the DAEMONS line, the file /etc/rc.d/exim will be executed, and that should get it started at bootup.
    Cheers.

  • Strange error message when starting listener at boot time

    Hi I have SuSE 10 server and Oracle 10.2.0
    I followed the instruction on my how configure /etc/init.d/dbora to start
    the db instance and the listener at boot time
    The db instance starts fine;however, the listener doesnt start and gives the following strange message
    "cannot start using /ade/vikrkuma_new/oracle/bin/tnslnr"
    Does anyone has seen this and is there a workaround?
    It looks like to me the listener tries to locate the listener.ora but it fails
    I tried to force it by setting TNS_ADMIN in my /etc/init.d/dbora script but it still doesnt pick it up
    any clue?

    Hi,
    Check your oracle bin varible and oracle home varible. If possible can you force this?
    Cheers,
    Kamalesh JK

  • Auto starting Oracle at boot time

    I have installed Oracle 11gr2 on Oracle Enterprise Linux successfully. Now i want to make oracle available automatically at boot time. I mean whenever server is up Oracle starts automatically.

    It is not happening. I have to run dbstart script to make oracle available.
    In ubuntu, we create /etc/init.d/oracledb script file, and with the use of following commands, oracle starts at boot time
    chmod a+x /etc/init.d/oracledb
    update-rc.d oracledb defaults 99
    What i need is, its parallel for OEL.

  • How to automatically start postfix on boot?

    I often need postfix to send e-mail. To use postfix I need to start postfix everytime manually via the Terminal commandline.
    I would like to have postfix to be started automatically with booting.
    Is this possible in Mac OS X Snow Leopard? How can it be done?

    There is already an org.postfix.master.plist file in /System/Library/LaunchDaemons
    I had an old copy of Postfix Enabler from http://cutedgesystems.com/ but didn't appreciate having to buy a new program when Leopard came out, so I rolled my own. Here is my edited org.postfix.master.plist:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Label</key>
    <string>org.postfix.master</string>
    <key>OnDemand</key>
    <false/>
    <key>Program</key>
    <string>/usr/libexec/postfix/master</string>
    <key>ProgramArguments</key>
    <array>
    <string>master</string>
    </array>
    <key>QueueDirectories</key>
    <array>
    <string>/var/spool/postfix/maildrop</string>
    </array>
    </dict>
    </plist>
    This will enable you to send mail. You can setup your Mac to receive mail too, but that is a bit more involved.

  • Boot Times on Leopard

    Ever since I upgraded to Leopard a few months back, I noticed my boot times increased from about 10-20 seconds to up to what is now ranging between 45 seconds to a full 2 minutes
    Just wanted to know if anyone else was facing boot time issues on their macbook pros
    Post your boot times here if you can please

    Okay, I just ran the entire tests and fixes through both OnyX and Main Menu
    Boot times were about 45-60 seconds
    Then I tried resetting the PRAM and after I heard it reset for 3 times, the boot time got reduced to 30-35 seconds
    Although the first time, my applications seemed longer to open but at least the boot times were down
    So looks like holding down the Apple/option/p/r reset for 3 times worked for me
    Will 4 or even 5 times do any better?
    I'd like to know how resetting it over and over again helps with the boot time

  • [SOLVED] How do I start scripts at boot up?

    I've been looking around for awhile and can't find a way to auto-start scripts I've written in the console (the only ways I've found are for older systems using /etc/rc.local, but my system doesn't have this file.  The only things I've found for systemd are about starting daemons.  I'm not running a desktop environment on this system nor do I plan to (I'm using this machine as a server), so I can't put the scripts in a directory that auto-starts them like I can in KDE (and even then, I think that's only auto-starting them after login; I need these scripts to run without need of logging in).  And since my scripts aren't services I can't use "systemctl enable" to make them start at bootup.
    Does anyone know how to start scripts when the system boots?
    Last edited by Zukaro (2013-01-10 23:02:22)

    https://wiki.archlinux.org/index.php/Sy … process.3F

  • How do i start over with my time machine

    My time machine has run out of space, and i want to start backing up 3 computers (up from 2), so i think it makes to just start over. How do i do that? Will it impact my Time Capsule's ability to be the main router for my home network (will I have to set that up again too?)? With 3 machines, should I get a 1TB (I have 500 GB)?

    Are your backups on the Time Capsule?  If so, you have a couple of options:
    Erase the TC's hard drive (see To erase everything on the Time
    Capsule’s internal disk in #Q5 of  Using Time Machine with a Time Capsule), and let Time Machine start over on all 3 Macs (one at a time, connect via Ethernet if at all possible -- the first full backup will be 2-3 times faster than WIFI).
    Connect a USB drive to the Time Capsule's USB port, and back the new Mac up to it, instead of the internal HD.  See #Q2 in the same link.

  • How to auto start XAMPP at boot?

    Placing:
    /opt/lampp/lampp start
    in the session will not work because it needs sudo priviliges. But I don't how to config it to auto start at boot on Arch Linux. Thanks

    Probably /etc/rc.local would be your best bet.

  • How do I start over with the time capsule.

    ok here is it goes.  Just moved into a new house and installed a new imac with sonos (3) play fives.  The power has gone out a few times and tehn my sonos looses its connection. (frustrating) so the other day I had to reset the sonos and now it will not find the shared drive even though it is there.  The geek squad set up my timecapsule and I am frustrated trying to figure it out.  It would be easier if I redo the whole thing myself.  I do not want to lose my info (music on the HD) just tear down the network and redo it so I know how the heck to fix things when needed.

    Any info on the TC is not touched by any reset you do.. the disk will need to be erased which is only done as a deliberate action. Plug in the TC by ethernet if not already, and hold down the reset button. Wait about 10sec and it will do a reset. If you press the button for only 1sec it will reset the passwords to default for 5min, and that may give you access. But nothing you do will wipe the drive.
    Give it a go and learn.. that is the best way if you have the time and patience.

  • How to cancel filesystem check at boot time with systemd

    Hello,
    while booting, when the filesystem is checked and it takes too long, it was possible with initscripts to press ctrl^c to cancel the check and postpone it to the next boot. How this can be done with systemd?

    http://kernelnewbies.org/Ext4#head-9a25 … 1279bd2b00 would lead me to think that fsck on converted ext4 should be as fast as on a regular ext4, unless http://kernelnewbies.org/Ext4#head-e7f9 … 68c012655c you're using a compatibility mode by mounting the converted fs as ext3.
    https://wiki.archlinux.org/index.php/Ex … to_extents should take care of old, pre-migration data.
    Admittedly, I may be reading into this too much, this is mostly guesswork on my part and you seem to know much more about the filesystems than I do :-)

  • Within the TCL and NPL, how do you start a DAQ-STC timer to count the elapsed time spent in time critical code?

    Clarification: I have a 6030E DAQ board which has a built-in DAQ-STC counter chip. I've created a RTOS for my PXI8175 controller. Unfortunately, while in the TCL clock interrupts are ignored and therefore any time based operations are erroneous. Is there a way to tell the TCL to service clock interrupts? Otherwise, perhaps the following concept should be implemented: Initial Time Stamp + elapsed time spent in TCL = Final Time Stamp

    While the system clock might fall behind, there are a number of ways to measure elapsed time accurately. Here they are in ascending order of accuracy:
    1) Tick Count - Each tick is 1.000686 milliseconds.
    2) DAQ-STC counter - The base clock is 20 MHz, thus the finest period of measurement is 50 nanoseconds.
    3) NI-TIO counter - The base clock is 80 Mhz, thus the finest period of measurement is 12.5 nanoseconds.
    4) RDTSC - Read Timestamp Counter is an assembly instruction which reads timestamps right off the CPU. The period depends on CPU speed (i.e. 1 GHz yields 1 nanosecond period).
    Programming #1 requires two calls to Tick Count and a little math. There are shipping DAQ examples that demonstrate how to count events/time with counters, so that addresses #
    2 and #3. As for #4, there's an RT shipping example that demonstrates how to use RDTSC. There's also an RT template, which is identical to the RT example I mentioned.
    Let me know if you need more info.

  • How do I start IDS upon boot on OSX 10.5?

    I'm trying to start IDS CS3 upon system bootup, which worked just fine by adding a StartupItem under 10.4.
    However, under 10.5, this no longer works.
    Anyone have any suggestions whatsoever, I'm happy to try them out, as long as it doesn't involve always logging in a user...

    Interesting. We have written a script that we place in /Library/StartupItems which works just fine under 10.4, but under 10.5, we get errors indicating that it's trying to access the UI session and isn't signed.
    Have you changed your system configuration in any way to circumvent this? Or am I just missing something fundamental here? I do have lot's of sysadmin experience with SunOS and Linux, but very little when it comes to BSD and OSX, so it's plausible I'm going at this the wrong way.
    If you post your script, I'm happy to try it and see if it works for me and learn from any misstakes I've made in my setup.

  • Booting time with Leopard

    May appear simplistic.
    But it seems, eversince I had OS 10.5.6 or maybe just lately, booting seems to take a little longer.
    I timed it at 75 to 80 sec. from the push of the START button until the full appearance of the DeskTop.
    Ran a Dik Utility Verification, ALL is fine.
    Now this could be anxiety on my part, but is this OK?
    MBP 2.16 duo, 4 RAM, 30GB on internal drive.
    Thank you
    R

    Try booting it to safe mode once, then normally again. If you want to, try timing it before safe mode and after. Safe mode itself will take longer because of what is going on, but maybe it will do a bit of spring cleaning. I don't have your system configuration so I can't say if that seems a long time or not.
    [Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
    [What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
    [Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
    Safe boot mode runs a directory check command similar to that used by Disk Utility's repair. In Tiger it ignores some stored information (cache) that is normally read that speeds up the boot process, and it moves some other caches to the trash. It also uses only System fonts and disables all Startup Items, third party items, and any Login Items.

  • SMF - start at boot time, but don't restart - possible?

    I'm setting up a software package that has a number of background processes.
    I've got SMF manifests created and imported for all of them, and they're working great for starting the processes at boot time, and doing the automatic restarts when one fails.
    Here's my problem. It turns out that the users of this software want to be able to use the software's integrated process control methods to stop some of their processes. With the current configuration, they use the software's method to stop one of it's processes, and SMF promptly restarts it.
    Is there a way to set up SMF managed software so that SMF starts it at boot time, but then doesn't care if stops later?
    Richard

    I'm not sure how it would be SMF "managed" in such a case. Obviously you want the management to be elsewhere.
    You could use the "legacy" startup scripts in /etc/rcX.d. That will start a process and forget about it, just like pre-Solaris 10. You don't use manifests or have any other benefits of SMF.
    If you do want SMF, I guess the question is how you want it to act..
    When the users stop the processes, do you want SMF to say enabled or disabled? SMF does not track enabled processes by periodic polling, it does it by tracking contracts. This means that starting a process outside of SMF does not allow SMF to track it.
    Darren

Maybe you are looking for