Community
Participate
Working Groups
This was reported by a user without much detail. I tried unzipping a kernel build in a directory "C:\a b" and it started perfectly, so this may be a known issue of a long path. Closing as unreproducible until/unless we get more details.
This fails on Mac OS X: $ pwd /Users/glynnormington/bugs2/pathwith space/virgo-kernel-3.6.0.M03 $ bin/startup.sh -clean /Users/glynnormington/bugs2/pathwith space/virgo-kernel-3.6.0.M03/bin/dmk.sh: line 21: cd: /Users/glynnormington/bugs2/pathwith: No such file or directory /Users/glynnormington/bugs2/pathwith space/virgo-kernel-3.6.0.M03/bin/dmk.sh: line 24: /Users/glynnormington/bugs2/pathwith: No such file or directory /Users/glynnormington/bugs2/pathwith space/virgo-kernel-3.6.0.M03/bin/dmk.sh: line 27: [: /Users/glynnormington/bugs2/pathwith: binary operator expected /Users/glynnormington/bugs2/pathwith space/virgo-kernel-3.6.0.M03/bin/dmk.sh: line 34: /Users/glynnormington/bugs2/pathwith: No such file or directory chmod: /Users/glynnormington/bugs2/pathwith: No such file or directory chmod: space/virgo-kernel-3.6.0.M03/configuration/org.eclipse.virgo.kernel.jmxremote.access.properties: No such file or directory Error: Exception thrown by the agent : java.io.FileNotFoundException: /Users/glynnormington/bugs2/pathwith (Socket operation on non-socket)
I have pushed a fix to the dmk.sh script to improve the quoting. This isn't a whole fix though as further work is required to ensure arguments are passes to the executable correctly.