Software distribution or something like this

[Eugen Cocalea]

Hi people,

I have several HPs on my network, all of them running HP-UX 11.00. Is there a way to have a remote root depot on central machine (non-HP-UX) and register the root depot on each of the HPs and then just go to each HP and install the software from there?
Hmm, let me put it another way: I want to make something like a central site with software for HP-UX, and if I add another piece of software on the site, I wouldn't have to go to each machine to transfer the new depot, register it, install it, unregister and delete the depot (because of limited drive space).
Well, if anyone understood what I tried to say here, just point me to some information, I don't need a 'type-and-run' solution, just some directions to dig.
Thank you,

Eugen Cocalea

[Bill McNAMARA_1]

have a look as swcopy
on your patch server run swcopy and copy all the patches to a directory path.

(Use swcopy in X format for ease - but if you're looking for commandline, search here, you'll find lots)

the then on other systems, use swinstall, select network directory, select the server, and click on the depot button to see your swcopied directory. mark and install as usual.

Bill

[Santosh Nair_1]

Bill,

Don't ypu have to register the depot in order to see it over the nextwork, i.e. on the patch server run swreg -l depot

-Santosh

[Sridhar Bhaskarla]

Eugen,

Lemme see if I understood your question.

1. You cannot have a centralized depot on non-HP server because they can not recognize the swdepot format.

2. If you have a centralized depot on HP Server, yes it is possible. What I am giving is only a hint and you can probably explore.

Place a script that runs via cron on each server to do the following

- The first time you need to manually install the depots on all the servers. Once it is done, keep a log of all the depots on the centralized server on the local system. Like
swlist -l depot -s your_server > $YOUR_LOG/depots.log

- This script has to be run at regular interval. Everytime, it does an swlist -l depot -s your_server and compares it against the previous log. If there is a difference, it gets the newly added depots by doing a diff and then installs the new depots. Again, it keeps the log of currently registed depots on the centralized server to compare against that next time.

This is only an idea. Writing a script for this is cumbersome. YOu need to isolate the depots that may reboot the system etc.,

-Sri

-Sri

[Sanjay_6]

Hi Eugen,

You don't have to register the remote depot locally on the system.

First, i don't think you can have a hp depot on a non-hp server. It would be good if you can dedicate one HP server for that purpose, but that is not necessary, you can use a system not heavily loaded and easily accessible over the network.

when you create a depot on a system, it gets registered on that system. So if you have a remote depot, all you have to do when you want to install a software on the local system is to point to the remote server.

On the local system, proceed like this

swinstall --> It will open the swinstall window and prompt you saying the default source "/var/adm/sw" does not exist or is not a valid source and there are no other registered depots on this server ....---> Here the "var/adm/sw" exist but it is not a depot and hence the error --> Select OK --> Now in the specify source screen, Select Sorce Depot type as "Network Directory / CDROM"
--> Specify Source hostname as the Server name of the remote depot (if its address can be resolved / this is important ) or the ip address of the remote depot --> Press spacebar in the Souce depot path selection and it will list the depot available on the sorce host specified by you.

The next screen will display the SD software on the depot selected and you can install the software at our convenience.

You don't need to have any depot on the local system, nor do you need to register a remote depot locally on the system. Whenever you want to install a software from the remote depot, just point to the remote depot and you have the software.

Do remember your remote server should be configured as NFS Server and the local host should at least be configured as a NFS client. I think that without this you may face problems.

Hope this helps.

Thanks

P.S. : I have a remote depot and i've been using it to install new patches and softwares on the local systems. I have to just copy any new software to the remote depot once and then i can install it on local systems using that depot.

[Santosh Nair_1]

Okay, so I was wrong...don't need to explicitly register the depot. You should be able to swcopy the software into a central depot (which has to be running HPUX) and then install the software on the various other HP machines.

You do NOT have to configure the patch server as an NFS server nor the client as NFS client. The SD tools doesn't have any dependancy on NFS. It does have dependancy on RPC, so make sure rpcd is running on both the server and clients.

-Santosh