On Sunday, November 27, 2011 05:13:09 PM Sebastian Hilbert wrote:
> On Sunday, November 27, 2011 05:10:43 PM Sebastian Hilbert wrote:
> > More info
> >
> > running bootstrap-latest.sh in /usr/lib/gnumed-server/bootstrap leads
> > to:;
> >
> > >linux:/usr/lib/gnumed-server/bootstrap # ./bootstrap-latest.sh
> > >===========================================================
> > >Bootstrapping latest GNUmed database.
> > >
> > >This will set up a GNUmed database of version v16
> > >with the name "gnumed_v16".
> > >Creating module import symlink ...
> > >real dir: /usr/lib/client
> > >
> > >     link: /usr/lib/Gnumed
> > >
> > >Traceback (most recent call last):
> > >  File "./bootstrap_gm_db_system.py", line 63, in <module>
> > >  
> > >    os.symlink(real_dir, link_name)
> > >
> > >OSError: [Errno 17] File exists
> > >Bootstrapping "gnumed_v16" did not finish successfully. Aborting.
> >
> > Seems not log file is created.
> >
> > Removing the faulty symlink actually starts the boostrap process.
>
It cannot create and therefore write to /var/log/gnumed/server

When manually creating that directory it works

Sebastian

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@gnu....
https://lists.gnu.org/mailman/listinfo/gnumed-devel