Sponsored Content
Operating Systems Solaris Help - Accessing Sun Fire V120 A/LOM Post 302250004 by glieu on Wednesday 22nd of October 2008 01:57:02 PM
Old 10-22-2008
Thanks DukeNuke2,

I will give it a shot.
 

9 More Discussions You Might Find Interesting

1. Solaris

SUN LOM password

Hi friends, Please tell me how to break the LOMlite password on SUN Netra X1 system. Thanks venkat (2 Replies)
Discussion started by: rvrao77
2 Replies

2. UNIX for Dummies Questions & Answers

Sun Fire 280R

Hello all, I'm lost and can't figure this problem out. I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies

3. Solaris

Weird behavior on a Sun Fire V120 running solaris 10.

All, After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex... (2 Replies)
Discussion started by: jsandova
2 Replies

4. Solaris

LOM on SUN ultra 10

Hi experts is it possible to install lom on sun ultra 10 box? can you guys help me in undertanding lom as i tried goggling , couldn't get good stuff. Please :) (6 Replies)
Discussion started by: kumarmani
6 Replies

5. Solaris

Installing OpenSolaris on Sun v120

I have come into my possesion a v120 server at work that was decommisioned from another project. I don't have the Solaris Installation CD nor do I have root or any user credentials on this server. My goal was to install OpenSolaris on this server and use it as a playground for learning UNIX... (6 Replies)
Discussion started by: stringzz
6 Replies

6. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

7. Solaris

Sun Fire v120 memory compatibility

Hi, I recently acquired an old Sun Fire v120 from work. I plan to play around with this at home whilst I'm studying for my SCSA exams. Only problem is it currently has no memory installed. I believe the memory modules required are 168 pin PC133 DIMMs. Unfortunately, the original Sun modules are... (3 Replies)
Discussion started by: skinyana
3 Replies

8. Solaris

Clone Production Server (Sun v120)

It's a DHCP server. We want to make a clone for fail over purpose since there are some identical systems available here. We do have a secondary DHCP server. Hardware: Sun v120. OS: Solaris 9. Two disks without array, /var and /opt on the secondary disk. How can I clone the system via network... (1 Reply)
Discussion started by: aixlover
1 Replies

9. Solaris

Sun fire x2270

Hello, I have purchaced an old SUn fire x2270 server . I wanted to make ILOM upgrade to the latest version of software : ILOM 3.0.9.18.a r126592 BIOS vers. 2.09 Server 2.2.3 (10-Aug-2018) Because my version is very outdated. But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
SLURPD(8C)																SLURPD(8C)

NAME
slurpd - Standalone LDAP Update Replication Daemon SYNOPSIS
/usr/libexec/slurpd [-d debug-level] [-f slapd-config-file] [-r slapd-replog-file] [-t temp-dir] [-o] [-k srvtab-file] DESCRIPTION
Slurpd is used to propagate changes from one slapd database to another. If slapd is configured to produce a replication log, slurpd reads that replication log and sends the changes to the slave slapd instances via the LDAP protocol. slurpd is typically invoked at boot time, usually out of /etc/rc.local. Upon startup, slurpd normally forks and disassociates itself from the invoking tty, then reads the replication log (given either by the replogfile directive in the slapd config file, or by the -r command-line option). If the replication log file does not exist or is empty, slurpd goes to sleep. It periodically wakes up and checks to see if there are any changes to be propoagated. When slurpd notices that there are changes to propagate to slave slapd instances, it locks the replication log, makes its own private copy, releases the lock, and forks one copy of itself for each replica slapd to be updated. Each child process binds to the slave slapd as the DN given by the binddn option to the replica directive in the slapd config file, and sends the changes. See slapd(8) for details on the standalone LDAP daemon. Note that slurpd reads replication directive from slapd.conf(5), but uses ldap.conf(5) to obtain other configuration settings (such as TLS settings). OPTIONS
-d debug-level Turn on debugging as defined by debug-level. If this option is specified, even with a zero argument, slurpd will not fork or disas- sociate from the invoking terminal. Some general operation and status messages are printed for any value of debug-level. debug-level is taken as a bit string, with each bit corresponding to a different kind of debugging information. See <ldap.h> for details. -f slapd-config-file Specifies the slapd configuration file. The default is /etc/openldap/slapd.conf. -r slapd-replog-file Specifies the name of the slapd replication logfile. Normally, the name of the replication log file is read from the slapd configu- ration file. The file should be located in a directory with limited read/write/execute access. The -r option allows you to over- ride this. In conjunction with the -o option, you can process a replication log file in a "one-shot" mode. For example, if slurpd has encountered errors in processing a replication log, you can run it in one-shot mode and give the rejection file name as the argument to the -r option, once you've resolved the problem which caused the replication to fail. -o Run in "one-shot" mode. Normally, slurpd processes the replog file and then watches for more replication entries to be appended. In one-shot mode, slurpd processes a replication log and exits. -t temp-dir slurpd copies the replication log to a working directory before processing it. The directory permissions should limit read/write/execute access as temporary files may contain sensitive information. This option allows you to specify the location of these temporary files. The default is /var/db/openldap/openldap-slurp. -k srvtab-file Specify the location of the kerberos srvtab file which contains keys for the replica slapd instances. Overrides the srvtab argument to the replica directive in the slapd configuration file. EXAMPLES
To start slurpd and have it fork and detach from the terminal and process the replication logs generated by slapd, just type: /usr/libexec/slurpd To start slurpd with an alternate slapd configuration file, and turn on voluminous debugging which will be printed on standard error, type: /usr/libexec/slurpd -f /etc/openldap/slapd.conf -d 255 SEE ALSO
ldap(3), ldap.conf(5), slapd.conf(5), slapd.replog(5), slapd(8) "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/) ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan LDAP 3.3 Release. OpenLDAP 2.1.X RELEASEDATE SLURPD(8C)
All times are GMT -4. The time now is 06:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy