Hi Andy,

First off, you have a pretty swell name.

I don't know what to make of the bug being fixed in 4.1.1:

[root@se8 ~]# xrootd -v
v4.2.2
[root@se8 ~]# rpm -qa | grep xrootd
xrootd-libs-4.2.2-1.osg32.el6.x86_64
xrootd-selinux-4.2.2-1.osg32.el6.noarch
xrootd-server-4.2.2-1.osg32.el6.x86_64
xrootd-client-4.2.2-1.osg32.el6.x86_64
xrootd-lcmaps-0.0.7-11.osg32.el6.x86_64
xrootd-client-libs-4.2.2-1.osg32.el6.x86_64
xrootd-4.2.2-1.osg32.el6.x86_64
xrootd-server-libs-4.2.2-1.osg32.el6.x86_64
xrootd-cmstfc-1.5.1-10.osg32.el6.x86_64
cms-xrootd-1.2-9.osg32.el6.noarch

Are you and OSG somehow out of sync in the versioning? To hack things together and get something working, I started the services with (ulimit -u 1024 ; /etc/init.d/xrootd start ; /etc/init.d/cmsd start), and they worked fine. Dropping the ulimit and restarting again caused them to break. What do you think?

—
Reply to this email directly or view it on GitHub.

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1