[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[condor-users] bad glob in standard universe?


I am seeing the following in version 6.6.1. If I take this code

[skoranda@contra skoranda]$ cat globtest.c
#include <stdio.h>
#include <glob.h>
int main(void){
        char dirname[256] = "./*";
        int ret;
        glob_t globbuf;
        ret = glob(dirname, GLOB_ERR, NULL, &globbuf);
        fprintf(stdout, "Found %d paths\n", (int) globbuf.gl_pathc);

and I compile and run it I see

[skoranda@contra skoranda]$ gcc -o globtest globtest.c
[skoranda@contra skoranda]$ ./globtest
Found 170 paths

But if I condor_compile I see this:

[skoranda@contra skoranda]$ condor_compile gcc -o globtest globtest.c
LINKING FOR CONDOR : /usr/bin/ld.real -L/opt/condor/lib -Bstatic -m
elf_i386 -dynamic-linker /lib/ld-linux.so.2 -o globtest
-L/usr/lib/gcc-lib/i386-redhat-linux/2.96/../../.. /tmp/ccOf3gjJ.o
/opt/condor/lib/libcondorzsyscall.a /opt/condor/lib/libz.a -lgcc -lc
-lnss_files -lnss_dns -lresolv -lc -lnss_files -lnss_dns -lresolv -lc
-lgcc /usr/lib/gcc-lib/i386-redhat-linux/2.96/crtend.o
/opt/condor/lib/libcondorzsyscall.a(condor_file_agent.o): In function
`CondorFileAgent::open(char const *, int, int)':
/usr/condor/dir_11077/src/condor_ckpt/condor_file_agent.C:99: the use
of `tmpnam' is dangerous, better use `mkstemp'
[skoranda@contra skoranda]$ ./globtest
Condor: Notice: Will checkpoint to ./globtest.ckpt
Condor: Notice: Remote system calls disabled.
Found 0 paths

Is this a bug?

If so, might there be a workaround? Some way to escape the * in the
glob string?



Condor Support Information:
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>