IMUNES on FreeBSD 8.0-RELEASE...

[Michael Madigan]

Hello Marko,

Thanks for the reply!!  I started from scratch and followed the directions with the new version of IMUNES.  Only difference this time was that I used tk-8.6.b.1_1 and created a symlink named wish8.4 using the following command: 

ln -s /usr/local/bin/wish8.6 /usr/local/bin/wish8.4

While IMUNES did not complain this time, it still did not work right when trying to execute an experiment (it would disable the "Execute" button and the toolbar on the right hand side, and I was not able to open a shell window to any of the nodes because that option was also disabled).  I noticed that I had been running IMUNES as a regular user and not as root.  So, I logged into KDE as root (after editing /usr/local/share/config/kdm/kdmrc and changing AllowRootLogin=false to AllowRootLogin=true), and IMUNES ran fine.  After playing around a little and looking into some of the IMUNES tcl files, I was able to get IMUNES running under a regular user by doing the following:

chmod 4755 /usr/local/bin/wish8.6
chmod 4555 /usr/sbin/vimage

I don't have the older version of IMUNES with the experimental code anymore, but I think it would run fine as a regular user after the above changes.  Thanks for your help!! 
  
Regards,
Mike
________________________________________
From: Marko Zec [zec at icir.org]
Sent: Saturday, January 09, 2010 10:22 AM
To: freebsd-virtualization at freebsd.org
Cc: Michael Madigan
Subject: Re: IMUNES on FreeBSD 8.0-RELEASE...

On Tuesday 05 January 2010 22:06:33 Michael Madigan wrote:
> Hello,
>
> Has anyone been successful in getting IMUNES to run on FreeBSD 8.0-RELEASE?
>  I have been trying and have had no luck.  I followed the directions from
> the following link exactly:
>
> http://www.mail-archive.com/freebsd-virtualization@freebsd.org/msg00156.htm
>l
>
> I have no problem starting up IMUNES or creating network topologies.
> However, when I tried  to run a network topology, I would get the following
> error:

Hi Michael,

I'm not shure why and how, but you've triggered some experimental code in the
IMUNES GUI which was not supposed to be in the tree for a while, possibly due
to some environment variable you might have set.  Nevertheless, I've removed
the offending code from the CVS - could you try refetching the GUI code from
the anoncvs and let me know whether it fixes the issue for you?

Cheers,

Marko


>
> can't use empty string as operand of "&&"
> can't use empty string as operand of "&&"
>     while executing
> "if { (![info exists mpid] || $mpid == "") && $ssh } {
>       set mpid [openFwrd [expr $rmPort + 10] $rmPort $userName@$rHost]
>     }"
>     (procedure "remoteStart" line 33)
>     invoked from within
> "remoteStart "
>     (procedure "nexec" line 7)
>     invoked from within
> "nexec id -u"
>     (procedure "setOperMode" line 11)
>     invoked from within
> "setOperMode exec"
>     invoked from within
> ".#menubar.#menubar#experiment invoke active"
>     ("uplevel" body line 1)
>     invoked from within
> "uplevel #0 [list $w invoke active]"
>     (procedure "tk::MenuInvoke" line 50)
>     invoked from within
> "tk::MenuInvoke .#menubar.#menubar#experiment 1"
>     (command bound to event)
>
>
> After searching through some of the tcl files, I tried changing the
> following lines in exec.tcl under the remoteStart procedure from
>
>
> if { (![info exists mpid] || $mpid == "") && $ssh } {
>     set mpid [openFwrd [expr $rmPort + 10] $rmPort $userName@$rHost]
> }
> if { (![info exists epid] || $epid == "") && $ssh } {
>     set epid [openFwrd [expr $rePort + 10] $rePort $userName@$rHost]
> }
>
>
> to
>
>
> if { (![info exists mpid] || $mpid == "") && ($ssh != "") } {
>     set mpid [openFwrd [expr $rmPort + 10] $rmPort $userName@$rHost]
> }
> if { (![info exists epid] || $epid == "") && ($ssh != "") } {
>     set epid [openFwrd [expr $rePort + 10] $rePort $userName@$rHost]
> }
>
>
> I now get past the previous errors, but now I get the following error:
>
> "Cannot open sockets"
>
> I have never done any tcl programming, so I don't have a clue of where to
> start debugging a program like this.  Does anyone have any ideas on how to
> resolve this?  Maybe I'm missing something?  Any help would be greatly
> appreciated!! Thanks!!
>
> Regards,
> Mike_______________________________________________
> freebsd-virtualization at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to
> "freebsd-virtualization-unsubscribe at freebsd.org"