When running a perl script that has been running fine
for ages and still runs fine on other machines with the same HW(the difference being Suse and 2.6.11 vs
2.6.13 Slack 10.2 on the current machine that gives the problem) , a cp fails with return code 65535. More detailed diagnostics ($!) says 'Cannot allocate memory'
top did not complain about memory. I suspect the problem is
much more serious(after storing and deleting large
datastructures which is what the program does, I simply cannot believe it
lacks the memory for a cp!). It does not happen on other machines with less memory even(I have 2GB RAM here)
copy /home/myuser/AFILES/s7ermsc1.0.2.gz to /home/myuser/DFILES/s7ermsc1.0.2.av.gz from AFILES to DFILES failed with 65535.
Exclam point is Cannot allocate memory
child exited with value %d
not copied ( cp /home/myuser/AFILES/s7ermsc1.0.2.av.gz /home/myuser/DFILES/s7ermsc1.0.2.av.gz )
for ages and still runs fine on other machines with the same HW(the difference being Suse and 2.6.11 vs
2.6.13 Slack 10.2 on the current machine that gives the problem) , a cp fails with return code 65535. More detailed diagnostics ($!) says 'Cannot allocate memory'
top did not complain about memory. I suspect the problem is
much more serious(after storing and deleting large
datastructures which is what the program does, I simply cannot believe it
lacks the memory for a cp!). It does not happen on other machines with less memory even(I have 2GB RAM here)
copy /home/myuser/AFILES/s7ermsc1.0.2.gz to /home/myuser/DFILES/s7ermsc1.0.2.av.gz from AFILES to DFILES failed with 65535.
Exclam point is Cannot allocate memory
child exited with value %d
not copied ( cp /home/myuser/AFILES/s7ermsc1.0.2.av.gz /home/myuser/DFILES/s7ermsc1.0.2.av.gz )