Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Changes to aleph_start or aleph_start.private not taking effect

    • Article Type: General
    • Product: Aleph
    • Product Version: 18 and up

    Description

    After changing ./alephe/aleph_start or aleph_start.private you find that an indexing daemon or a batch job submitted through the GUI Services is not using the changed value.

    Resolution


    In order for changes to aleph_start or aleph_start.private to take effect, you must "source aleph_start" (or exit aleph / re-log-in) and then restart the daemons and servers. {For batch jobs submitted through GUI Services this also means that the batch_que must be restarted.} See also article Additions to aleph_start not taking effect

    You can echo the parameter to verify its current value, such as:

    > echo $pw_library

    Running aleph_shutdown and aleph_startup restarts all daemons, servers, and queues. This is the surest thing.

    If the echo gives you "undefined variable", see article ALEPH table or screen change doesn't take effect.


    • Article last edited: 1-Sept-2016
    //doorbell.io feedback widged