 |
 |
Hi Christian, Yeah, this is irritating. I'm afraid the answer is that we don't build these rpms, so we can't change the versioning without producing LCG/EGEE variants of the packages (which we really want to avoid). Oliver. Oliver Keeble Information Technology Department [log in to unmask] CERN +41 22 76 72360 CH-1211 Geneva 23 Christian Peter wrote: > hi oliver, > > during our LCG 2.6.0 update i just noticed that the old rfiod start > problem was still present on a SE machine. > > analysis: > > in the LCG 2.6 repository, there *is* an updated version of the > necessary RPM: > CASTOR-client-1.7.1.5-1.longname.i386.rpm, 24-Jun-2005 12:54, > 5986136 bytes > > but unfortunately, it has the same version and revision number as the > old buggy variant so it has never been (automatically) installed on our > machine. > > obvious solution: > > #rpm -e --nodeps CASTOR-client > #apt-get install CASTOR-client > > could you please increase the revision number of that RPM package? > > regards, > christian > > > Oliver Keeble wrote: > >> Hi Chris, >> >> This looks like a bug in the >> CASTOR-client-1.7.1.5-1.longname.i386.rpm package distributed with the >> middleware - I'll make sure it gets updated. FYI, I notice that the >> CASTOR-client rpm distributed with SLC3 (rather than the middleware) does >> not suffer from this. Thanks, >> >> -Oliver >> >> -------------------------------------------------------------------- >> Oliver Keeble Information Technology Department >> [log in to unmask] CERN >> +41 22 76 74929 CH-1211 Geneva 23 >> >> On Mon, 24 Jan 2005, Brew, CAJ (Chris) wrote: >> >>> Hi, >>> >>> I had a problem with rfiod not starting on my YAIM installed SL303 SE >>> box. >>> >>> When you try to start the daeomn you get: >>> >>> [root@heplnx202 root]# /etc/init.d/rfiod start >>> Starting rfiod: execvp: No such file or directory >>> rfiod not started: >>> >>> I've eventually isolated the cause of the problem to /etc/init.d/rfiod >>> >>> In there the path to the rfiod executable is explicitly specified as >>> /usr/local/bin/rfiod in actual fact rfiod is at /usr/bin/rfiod on these >>> nodes. >>> >>> Changing the entry in the init.d script seems to have solved the >>> problem. >>> >>> Yours, >>> Chris. >>> >>> -- >>> Chris Brew ([log in to unmask]) +44 1235 446326 >>> Particle Physics Department >>> Rutherford Appleton Laboratory >>> Chilton, Didcot. Oxfordshire. >>> OX11 0QX. United Kingdom. >>> >> >