Mark Seger wrote: > I just started an X server and exported the display to my laptop and NOW > I'm seeing something. Very cool, but I'm curious as to why I did't get > any "can't open display" errors from the script. I have perl scripts > that use TK and I thought they always gave me that error but when I went > to try and generate it so I could send a sample, it didn't! Now I'm
what about $DISPLAY? maybe it's = :0.0 and si_monitortk started in the real monitor of the machine... > confused because I know that at least under some circumstances that > occurs. btw - is it a valid assumption that everyone will always have > an X display running? Would it be a royal pain to support a non-X > mode? In any event, if someone could figure out how to tell if there is > an X server running and generate an error if one isn't, that could save > a lot of time for everyone. I suppose at the very least in the > Troubleshooting section one could enter the problem that monitortk isn't > generating output and the recommended solution is to see if X is > running. Also, is that -db switch needed? If you've not an X running you can always monitor the clients simply looking in /var/lib/systemimager/clients.xml... cat is sufficient! ;-) but I agree it's not a nice interface... maybe we could implement something using curses... at the moment I agree to add a comment in the troubleshooting section. -db is not mandatory, by default it uses /var/lib/systemimager/clients.xml. Cheers, -Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
