zappy1 and zappy2 are a hangover from a time when we were running two zappy
instances on a single server (long story...), just use zappy1 for
everything.
Yes there are hard coded paths, the whole thing needs packaging properly.
You may find it easier to work with these paths rather than trying to edit
everything.
80n
On Fri, Jun 19, 2009 at 1:41 PM, Christian Lange <cla...@nw7.de> wrote:
> Hi,
>
> what is the different between zappy1 zappy2 zappy4?
>
> there are many hardcoded path's in the source like "/home/etienne/...".
>
>
> regards christian
>
> 80n schrieb:
> > Christian
> > These are compilation errors, but actually for modules that only apply to
> > other platforms so they can be safely ignored.
> >
> > If you re-run the process (zappy1_up I assume) you shouldn't see these
> > errors again.
> >
> > 80n
> >
> > On Fri, Jun 19, 2009 at 9:47 AM, Christian Lange <cla...@nw7.de> wrote:
> >
> >
> >> Next problem is:
> >> o socket:(:port:"PSTA"):10 e d logMessage("Cannot open
> >> socket",0,port) s stop=1 q
> >> ^-----
> >> At column 12, line 53, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >> . u socket:"PSTA"
> >> ^-----
> >> At column 13, line 57, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >> . j
> >> sub01^serverLink(port,logLevel):(:4:socket:socket):10 e d
> >> logMessage("Cannot spawn sub-process",1,port) q
> >> ^-----
> >> At column 39, line 60, source module serverLink.m
> >> %GTM-E-JOBPARUNK, Job parameter unknown
> >> o device:("TCP":"":port):10 e d logMessage("Cannot open
> >> socket",0,port) s stop=1 q
> >> ^-----
> >> At column 12, line 73, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >> . s socket=$zsocket(device)
> >> ^-----
> >> At column 14, line 80, source module serverLink.m
> >> %GTM-E-INVFCN, Invalid function name
> >> . u device:(::::::socket) ; Detach socket
> >> ^-----
> >> At column 14, line 82, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >> . c device:socket
> >> ^-----
> >> At column 19, line 84, source module serverLink.m
> >> %GTM-E-DEVPARVALREQ, A value is required for this device parameter
> >> s $et="i $estack=0 znspace """_$znspace_""" g
> >> error^serverLink"
> >> ^-----
> >> At column 34, line 182, source module serverLink.m
> >> %GTM-E-INVSVN, Invalid special variable name
> >> u socket:(::"STP")
> >> ^-----
> >> At column 12, line 188, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >> . u socket:(::"STP")
> >> ^-----
> >> At column 14, line 198, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >> s ucivol=$zu(0)
> >> ^-----
> >> At column 12, line 228, source module serverLink.m
> >> %GTM-E-INVFCN, Invalid function name
> >> s ucivolno=$zu(uci,vol)
> >> ^-----
> >> At column 14, line 231, source module serverLink.m
> >> %GTM-E-INVFCN, Invalid function name
> >> o device:("TCP":""::::socket) ; Attach socket
> >> ^-----
> >> At column 12, line 239, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >> u device:(:::$c(10))
> >> ^-----
> >> At column 12, line 285, source module serverLink.m
> >> %GTM-E-DEVPARUNK, Deviceparameter unknown
> >>
> >>
> >> regards christian
> >>
> >> 80n schrieb:
> >>
> >>> Christian
> >>> This can occur if you are running SELinux. In that case try it with
> >>>
> >> SELinux
> >>
> >>> disabled, or follow the suggestions from this post:
> >>>
> >>>
> >>
> http://www.mail-archive.com/hardhats-memb...@lists.sourceforge.net/msg16471.html
> >>
> >>> A second possibility is if you are using an AMD processor then you need
> >>>
> >> to
> >>
> >>> add noexec32=off to your kernel boot command line.
> >>>
> >>> 80n
> >>>
> >>> On Thu, Jun 18, 2009 at 11:12 AM, Christian Lange <cla...@nw7.de>
> wrote:
> >>>
> >>>
> >>>
> >>>> Hi,
> >>>> i will be setup a xapi server.
> >>>>
> >>>> i have looked in http://xapi.openstreetmap.org/ and
> >>>> http://xapi.openstreetmap.org/scripts <scripts> .
> >>>>
> >>>> but i do nothing know about GT.M
> >>>>
> >>>> i have try to start zappy:
> >>>>
> >>>> %GTM-F-KILLBYSIGSINFO1, GT.M process 20929 has been killed by a signal
> >>>> 11 at address 0xF7CFBF83 (vaddr 0x00000000)
> >>>> %GTM-F-SIGMAPERR, Signal was caused by an address not mapped to an
> >>>>
> >> object
> >>
> >>>> can anybody help me plz?
> >>>>
> >>>>
> >>>>
> >>>> sorry for my english ;)
> >>>>
> >>>>
> >>>> regards Christian
> >>>>
> >>>> _______________________________________________
> >>>> dev mailing list
> >>>> dev@openstreetmap.org
> >>>> http://lists.openstreetmap.org/listinfo/dev
> >>>>
> >>>>
> >>>>
> >>>
> >> _______________________________________________
> >> dev mailing list
> >> dev@openstreetmap.org
> >> http://lists.openstreetmap.org/listinfo/dev
> >>
> >>
> >
> >
>
>
_______________________________________________
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
