Sponsored Content
Operating Systems Solaris legato for Lotus (load_notes_api|0|0|0) Post 302387981 by eshon on Tuesday 19th of January 2010 04:44:08 AM
Old 01-19-2010
Network legato for Lotus (load_notes_api|0|0|0)

hai,
Help me please
OS SUN 5.10 Lotus 8
Legato for Lotus 3.0

when backing up gives this error
Code:
The dlopen() call for library libnotes.so failed with error:
        ld.so.1: nsrnotesv: fatal: libnotes.so: open failed: No such file or directory (load_notes_api|0|0|0)
...

nsrnml_confige.template

Code:
LOTUS {

     #
     # REQUIRED Parameter: Notes_ExecDirectory
     #
     # Default value: NONE
     #
     # Description: Full path of the Domino Server being
     #  backed up or recovered. It is a requirement that the Lotus
     #  library libnotes.so is located in this directory.
     #
     # Sample: 
     #  Notes_ExecDirectory = /opt/lotus/notes/latest/solaris
     #
 Notes_ExecDirectory = /opt/ibm/lotus/notes/85000/sunspa/85FP1

     #
     # REQUIRED Parameter: NSR_RESOURCE_DIR
     #
     # Default value: NONE
     #
     # Description: Full path of Domino Server resource files.
     #
     # Sample: 
     #  NSR_RESOURCE_DIR = /opt/lotus/notes/latest/solaris/res/C
     #
 NSR_RESOURCE_DIR = /opt/ibm/lotus/notes/latest/sunspa/res/C

     #
     # REQUIRED Parameter for Scheduled Backup: LOTUSUSER
     #
     # Default value: NONE
     #
     # Description: Name of the operating system user that runs
     #  the Domino Server being backed up.
     #
     # Sample: 
     #  LOTUSUSER = notes
     #
 LOTUSUSER = domino

     #
     # Optional Parameter: PATH
     #
     # Default value: $PATH environment variable set in the running
     #  environment.
     #
     # Description: $PATH environment variable to be set for the operation.
     #  This parameter should contain the location of notes.ini file for
     #  Domino Server being backed up, and any other path
     #  needed by the NML operation.
     #
     # Sample: 
     #  PATH = /Domino/data:/opt/lotus/bin
     #
# PATH = /local/notesdata:/opt/ibm/lotus/bin

 PATH = /local/notesdata:/opt/ibm/lotus/bin:/usr/sbin
     #
     # Optional Parameter for Scheduled Backup: PRECMD
     #
     # Default value: NONE
     #
     # Description: Full path of a command script to be run before the


Last edited by pludi; 01-19-2010 at 05:50 AM.. Reason: code tags, please...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Veritas or Legato??

Hi guys, What product would you suggest for a hot/on-line backup with an active oracle database ?? (6 Replies)
Discussion started by: guest100
6 Replies

2. UNIX for Advanced & Expert Users

Veritas or Legato?

Hi guys, What product would you suggest for a hot/on-line backup with an active oracle database ?? (3 Replies)
Discussion started by: guest100
3 Replies

3. UNIX for Dummies Questions & Answers

Legato Storage manager on Tru64

Hi, OS : Compaq Tru64 4.0D I am installing newer version of LSM which comes with Oracle Enterprise Edition. I removed the previous version of legato(Server, Node, Client and Man) using setld -d but when I try to install the new version I get this message.. ** Installation of LSM... (2 Replies)
Discussion started by: sanjay_g
2 Replies

4. UNIX for Advanced & Expert Users

Legato Networker

Has anyone ever used Networker to backups a SunSolaris 5.4 system. I have all the my other OS on the network being backup except for the 5.4 systems. It's has to do with a daemon. So help me out this doesn't make any since> (3 Replies)
Discussion started by: aojmoj
3 Replies

5. HP-UX

Legato networker on hp-ux

Hello, Firstable I am new on hp-ux (well long time ago) I am more aix admin.... Legato networker is the tool backup use on the hp-ux. I don't know this tool and would like to know where to find some docs or training. My first question will be : when a system (hp-ux B.11.0) is backuped on a... (8 Replies)
Discussion started by: touny
8 Replies

6. Filesystems, Disks and Memory

restore from Legato

Hi Fellas/Ladies I havent dont any restore unix systemsand recently issue has come up that I need to restore to fridays copy. I want to restore everything to last fridays for the directory /usr/local/projects. Anyone done legato restores? Would it keep acl/permissions, symlinks etc. ... (0 Replies)
Discussion started by: brabored
0 Replies

7. UNIX for Advanced & Expert Users

Legato Display

I am running legato 7.3.2. Here is my issue. I have taken over the backup duties from an employee who left the company. He was running Legato as the backup server/client of choice (I don't know much about Legato, but i am learning on the job). He has it setup to run the admin qui from the backup... (3 Replies)
Discussion started by: seacros
3 Replies

8. AIX

Did Sudo break my Legato

I have a system that has been runing Legato for a few years (i inherieted this system). I have now been tasked with maintaining this system. I installed sudo on it so i didnt have to give out my root password and not some of my SAP backup jobs are failing. Can anyone out there give me some help?... (2 Replies)
Discussion started by: seacros
2 Replies

9. UNIX for Dummies Questions & Answers

Legato networker 7.6

Hi ALl I have recently installed networker 7.6 on my solaris 10 host(V240). My bosses requirement was that the GUI was still availible (nwadmin). However on 7.6 there is no GUI and nwadmin does not exist. I have copied nwadmin over from the previous version of legato i had installed (6.2), and... (5 Replies)
Discussion started by: brian112
5 Replies

10. Solaris

Legato Networker

Hi , I have a lot of Tape device with backups from solaris sparc servers. This tape are in Legato Networker Format and now I need access and search an old backup. I know that Legato needed a Server , but this server is wrong , this down long time ago. I have a Legato Networker Server/Client... (10 Replies)
Discussion started by: z0rtiz
10 Replies
SYSTEMD.ENVIRONMENT-GENERATOR(7)			   systemd.environment-generator			  SYSTEMD.ENVIRONMENT-GENERATOR(7)

NAME
systemd.environment-generator - systemd environment file generators SYNOPSIS
/lib/systemd/system-environment-generators/some-generator /usr/lib/systemd/user-environment-generators/some-generator /run/systemd/system-environment-generators/* /etc/systemd/system-environment-generators/* /usr/local/lib/systemd/system-environment-generators/* /lib/systemd/system-environment-generators/* /run/systemd/user-environment-generators/* /etc/systemd/user-environment-generators/* /usr/local/lib/systemd/user-environment-generators/* /usr/lib/systemd/user-environment-generators/* DESCRIPTION
Generators are small executables that live in /lib/systemd/system-environment-generators/ and other directories listed above. systemd(1) will execute those binaries very early at the startup of each manager and at configuration reload time, before running the generators described in systemd.generator(7) and before starting any units. Environment generators can override the environment that the manager exports to services and other processes. Generators are loaded from a set of paths determined during compilation, as listed above. System and user environment generators are loaded from directories with names ending in system-environment-generators/ and user-environment-generators/, respectively. Generators found in directories listed earlier override the ones with the same name in directories lower in the list. A symlink to /dev/null or an empty file can be used to mask a generator, thereby preventing it from running. Please note that the order of the two directories with the highest priority is reversed with respect to the unit load path, and generators in /run overwrite those in /etc. After installing new generators or updating the configuration, systemctl daemon-reload may be executed. This will re-run all generators, updating environment configuration. It will be used for any services that are started subsequently. Environment file generators are executed similarly to unit file generators described in systemd.generator(7), with the following differences: o Generators are executed sequentially in the alphanumerical order of the final component of their name. The output of each generator output is immediately parsed and used to update the environment for generators that run after that. Thus, later generators can use and/or modify the output of earlier generators. o Generators are run by every manager instance, their output can be different for each user. It is recommended to use numerical prefixes for generator names to simplify ordering. EXAMPLES
Example 1. A simple generator that extends an environment variable if a directory exists in the file system # 50-xdg-data-dirs.sh #!/bin/bash # set the default value XDG_DATA_DIRS="${XDG_DATA_DIRS:-/usr/local/share/:/usr/share}" # add a directory if it exists if [[ -d /opt/foo/share ]]; then XDG_DATA_DIRS=/opt/foo/share:${XDG_DATA_DIRS} fi # write our output echo XDG_DATA_DIRS=$XDG_DATA_DIRS Example 2. A more complicated generator which reads existing configuration and mutates one variable # 90-rearrange-path.py #!/usr/bin/env python3 """ Proof-of-concept systemd environment generator that makes sure that bin dirs are always after matching sbin dirs in the path. (Changes /sbin:/bin:/foo/bar to /bin:/sbin:/foo/bar.) This generator shows how to override the configuration possibly created by earlier generators. It would be easier to write in bash, but let's have it in Python just to prove that we can, and to serve as a template for more interesting generators. """ import os import pathlib def rearrange_bin_sbin(path): """Make sure any pair of .../bin, .../sbin directories is in this order >>> rearrange_bin_sbin('/bin:/sbin:/usr/sbin:/usr/bin') '/bin:/sbin:/usr/bin:/usr/sbin' """ items = [pathlib.Path(p) for p in path.split(':')] for i in range(len(items)): if 'sbin' in items[i].parts: ind = items[i].parts.index('sbin') bin = pathlib.Path(*items[i].parts[:ind], 'bin', *items[i].parts[ind+1:]) if bin in items[i+1:]: j = i + 1 + items[i+1:].index(bin) items[i], items[j] = items[j], items[i] return ':'.join(p.as_posix() for p in items) if __name__ == '__main__': path = os.environ['PATH'] # This should be always set. # If it's not, we'll just crash, we is OK too. new = rearrange_bin_sbin(path) if new != path: print('PATH={}'.format(new)) Example 3. Debugging a generator SYSTEMD_LOG_LEVEL=debug VAR_A=something VAR_B="something else" /lib/systemd/system-environment-generators/path-to-generator SEE ALSO
systemd-environment-d-generator(8), systemd.generator(7), systemd(1), systemctl(1) systemd 237 SYSTEMD.ENVIRONMENT-GENERATOR(7)
All times are GMT -4. The time now is 11:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy