Extremely dumb question

Question

Hi,
          This is really basics, but...
          Replicated JNDI is the most obvious answer to the following questions,
          but considering that bindings are removed on a failure of the host, it
          doesn't really work for failover.
          Let say I have a stateless bean that provides a description of the
          capabilities of a service implemented by the server application.
          Doesn't really matter. Importantly, it is not related to any
          particular session. A requirement states that the bean must not be
          created till the first request to functions it provides is issued. So,
          pre-instantiating it by the start-up classes is discouraged.
          Where should I keep the reference to the stub after the bean is
          created by the front-end servlet, so that it would survive failover
          and would be available to all the servers in a cluster? Servers are
          brought into the cluster dynamically over a period of time.
          A similar question. Let say a user object is an application-wide
          resource. Where do I keep it, so that it would survive a failover?
          Thanx
          Ed Gokhman
          

Answer 1

InfernalH wrote:
Sorry for extremely dumb question, but I have the following situation after the last "sudo pacman -Syu":
Targets: abiword-2.2.7-1 acroread-7.0.0-1 codecs-20050216-1 curl-7.13.2-1
dialog-1.0-3 dosfstools-2.11-1 doxygen-1.4.2-1 ethereal-0.10.10-1
gaim-1.2.1-1 gentoo-0.11.54-1 gkrellm-2.2.5-1 gnupg-1.4.1-1
imagemagick-6.2.1-1 imlib2-1.2.0-2 lesstif-0.94.4-1 lftp-3.1.2-1
libao-0.8.6-1 libgcrypt-1.2.1-1 libgnomeprint-2.10.3-1 libxml2-2.6.19-1
libxslt-1.1.14-1 links-2.1pre17-1 m4-1.4.3-1 mozilla-firefox-1.0.2-1
mplayer-1.0pre6a-2 opera-8.00b3-1 parted-1.6.22-1 php-5.0.4-1
phpmyadmin-2.6.2.rc1-1 pkgconfig-0.16.0-1 python-2.4.1-1 rsync-2.6.4-1
sudo-1.6.8-6 tcsh-6.14.00-1 util-linux-2.12-7 whois-4.7.2-1
wvstreams-4.0.2-1 xchat-2.4.3-1 xlockmore-5.16-1 xplanet-1.1.2-1
xscreensaver-4.21-1 [b]yp-tools-2.9-1[/b]
Total Package Size: 128.3 MB
Proceed with upgrade? [Y/n]
checking package integrity... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
yp-tools: /bin/domainname: exists in filesystem
yp-tools: /bin/nisdomainname: exists in filesystem
yp-tools: /bin/ypdomainname: exists in filesystem
errors occurred, no packages were upgraded.
[vidmantas@localhost ~]$
What I have to do to make yp-tools update without any problems? Which package contains /bin/domainname and other of listed files? What to do if I have same situation with other files/programs in future?
try to use -f so it is forced