Hi,
When uploading a profile image to ODS, the system automatically ( via
ImageMagick? ) creates a resized version. In some cases the aspect
ratio of the image is altered, which is not desirable in portrait
images.
Try uploading an image that is both smaller and thinner ( with a lower
w/h ratio )
Beside that parallel building is broken on VOS 5.0.10.
Another finding is that the 'make check' test runs 9.7% slower on VOS
5.0.10 than it did on VOS 5.0.9:
5.0.9 : 2941 seconds
5.0.10: 3227 seconds
Environment:
Mac OS X 10.5.6
Xcode 3.1.2
Code2Duo processor
Build settings:
CC=gcc-4.2
Hi Ceriel,
Building VOS 5.0.9 with 'make -j2' succeeded in december 2008.
Now trying with VOS 5.0.10.
After some failed VOS 5.0.10 build experiments, executed were:
$ make clean
$ CFLAGS="-O -m64 -mmacosx-version-min=10.5"
$ export CFLAGS
$ ./configure && make -j2 && sudo make install && make c
Steve Judkins wrote:
Running this locally downloads the data fine, but fails during the
reassemble phase with:
ERROR SR406: Running of file '/bin/sh' is not allowed in
run_executable(). (42000).
Hi,
You might want to investigate AllowOSCalls in virtuoso.ini.
HTH,
~Tim
--
Tim Haynes
Product
Ceriel Jacobs wrote:
For your information.
Building VOS 5.0.9 with 'make -j2' succeeded in december 2008.
Now trying with VOS 5.0.10.
After some failed VOS 5.0.10 build experiments, executed were:
$ make clean
$ CFLAGS="-O -m64 -mmacosx-version-min=10.5"
$ export CFLAGS
$ ./configure && make -j
For your information.
Building VOS 5.0.9 with 'make -j2' succeeded in december 2008.
Now trying with VOS 5.0.10.
After some failed VOS 5.0.10 build experiments, executed were:
$ make clean
$ CFLAGS="-O -m64 -mmacosx-version-min=10.5"
$ export CFLAGS
$ ./configure && make -j2 && sudo make install
Steve Judkins wrote:
Your solution is as follows:
1. Go to the ./backup directory that contains the backup files
2. Perform a manual restore (i.e. virtuoso -c
+restore-backup
)
This should work. It reconstitutes the db and log file but when I load
it I'm back to the pro
>
> Your solution is as follows:
>
> 1. Go to the ./backup directory that contains the backup files
> 2. Perform a manual restore (i.e. virtuoso -c +restore-backup
> )
>
>
This should work. It reconstitutes the db and log file but when I load it
I'm back to the problem where virtuoso starts up an
