[cod] World At War 1.6 Error libdl.so.2

stp at shooter-szene.de stp at shooter-szene.de
Mon Sep 21 07:03:39 EDT 2009


no, cod5 is not the user, i tried also as root and the rights of lnxded´s 
are ok

thats wierd, it never happend before

i think its nothing with the permissions

hrm



----- Original Message ----- 
From: "escapedturkey" <escapedturkey at escapedturkey.com>
To: "Call of Duty server admin list." <cod at icculus.org>
Sent: Monday, September 21, 2009 12:52 PM
Subject: Re: [cod] World At War 1.6 Error libdl.so.2


> The username's is cod5?
>
> So when you su - cod5 it logins as a user?
>
> Please type 'whoami' after you su - cod5
>
> Then you may want to chmod 755 codwaw_lnxded-bin
>
> :)
>
> Please try this script as root:
>
> permissions-fix.sh
>
> #!/bin/bash
> chmod 711 /home
> rm -f /home/users
> cd /home
> ls -1p|grep /|grep -v install|cut -d "/" -f1 > users
> for user in `cat users`
> do
> /bin/chmod 700 /home/$user
> chown -R $user.$user /home/$user
> done
> rm -f /home/users
> exit $?
>
> stp at shooter-szene.de wrote:
>> just another problem i never had before
>>
>> USER:/home/cod5# ./codwaw_lnxded +set net_port 28960 +set sv_punkbuster 1 
>> +set sv_pure 1 +exec server.cfg +set fs_homepath /home/cod5/ +map_rotate
>> ./codwaw_lnxded: line 46: /home/cod5/codwaw_lnxded-bin: cannot execute 
>> binary file
>> ./codwaw_lnxded: line 46: /home/cod5/codwaw_lnxded-bin: Success
>>
>> i tried with another user, all rights seems to be ok, libs are ok and 
>> located in the right folders, i dont have any clue what going on
>>
>>
>> ----- Original Message ----- From: "Ryan C. Gordon" <icculus at icculus.org>
>> To: "Call of Duty server admin list." <cod at icculus.org>
>> Sent: Monday, September 21, 2009 9:32 AM
>> Subject: Re: [cod] World At War 1.6 Error libdl.so.2
>>
>>
>>> Brandon Clinger wrote:
>>>> I receiving this error. Any ideas where to start with this one?
>>>>
>>>> *./codwaw_lnxded-bin: error while loading shared libraries: libdl.so.2: 
>>>> cannot create shared object descriptor: Cannot allocate memory*
>>>
>>> I have no idea why that would happen, but did this work in 1.5? I added 
>>> an explicit RPATH to the binary so it knows to load libgcc/libstd from 
>>> the same directory as the game without the LD_LIBRARY_PATH hack that 
>>> used to be in the shell script. It's possible this is causing some funky 
>>> bad reaction from your dynamic loader?
>>>
>>> If this wasn't tested with 1.5: you have a broken system.  :)
>>>
>>> --ryan.
>>>
>>>
>>> _______________________________________________
>>> cod mailing list
>>> cod at icculus.org
>>> http://icculus.org/mailman/listinfo/cod
>>>
>>
>> _______________________________________________
>> cod mailing list
>> cod at icculus.org
>> http://icculus.org/mailman/listinfo/cod
>>
> _______________________________________________
> cod mailing list
> cod at icculus.org
> http://icculus.org/mailman/listinfo/cod
> 



More information about the cod mailing list