pathname problems?
Douglas Egan
degan at calcon.net
Thu May 3 18:09:55 GMT 2001
I generated a log file as you asked. I don't want to clog BW with a big file
so it can be found at:
http://www.calcon.net/~degan log.nsh-doug.samba.org.gz
Here is the DOS command and environment that generated the log.
Thanks,
Doug Egan
G:\FCS-apr19\target\config\m5307c3>ls
Makefile bootrom_res hello.c romInit_res.o sysLib.o
README bootrom_res.hex hello.o stderr sysSerial.c
bootConfig.o config.h m5307c3.h sysALib.o target.nr
bootInit.o configNet.h romInit.o sysALib.s version.o
bootInit_res.o depend.m5307c3 romInit.s sysLib.c
G:\FCS-apr19\target\config\m5307c3>make
cccf -c -m5200 -ansi -O2 -fvolatile -Wall -I/h -I.
-IG:\FCS-apr19\target\conf
ig\all -IG:\FCS-apr19\target/h -IG:\FCS-apr19\target/src/config
-IG:\FCS-apr19\t
arget/src/drv -DCPU=MCF5200 G:\FCS-apr19\target\config\all\usrConfig.c -o
us
rConfig.o
cccf: installation problem, cannot exec
`G:/FCS-apr19/host/x86-win32/lib/gcc-lib
/cf-wrs-vxworks/gcc-2.96/cpp.exe': No such file or directory
make: *** [usrConfig.o] Error 0x1
G:\FCS-apr19\target\config\m5307c3>set path
Path=G:\FCS-apr19\host\x86-win32\bin;D:\TOOLS\CYGWIN\BIN;C:\WINNT\SYSTEM32;C:\WI
NNT;C:\WINNT\SYSTEM32\WBEM;D:\tools\TclPro1.4\win32-ix86\bin
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
Jeremy Allison wrote:
> Douglas Egan wrote:
> >
> > Does anyone know if samba has potential problems with pathnames formed
> > like:
> >
> > s:\tornado\target\h\..\..\target\config\m5307c3\config.h
> >
> > Particularly if there are more than just a couple of ..\..
> >
> > I have run into this when using gcc 2.96 as well as another product
> > called SNiFF+. Both use pathnames formed like above, but sometimes with
> > 5 or 6 levels of backward path traversal.
> >
> > Both will run under win2k (sp1) when the filesystem is mounted using a
> > win2k NFS client or TAS (TotalNet Advanced Server smb based product
> > from www.syntax.com), but both seem to have problems when executing from
> > a win2k machine and the fs is shared with samba. Samba 2.0.7, 2.0.8 and
> > 2.2.0 all seem to have this problem (haven't tried anything earlier than
> > 2.0.7).
> >
> > Lot's of unable to find file messages.
>
> Can you give more details please ? Debug level 10 logs with
> no timestamps ?
>
> Thanks,
>
> Jeremy.
>
> --
> --------------------------------------------------------
> Buying an operating system without source is like buying
> a self-assembly Space Shuttle with no instructions.
> --------------------------------------------------------
More information about the samba-technical
mailing list