[osol-discuss] network monitoring software on osol/belenix/linux
Dear all, Primarily my servers would be either Linux or Opensolaris. I'm evaluating to implement network monitoring infrastructure for various heterogeneous systems like windows,linux, mac os x and solaris etc. to be monitored centrally. while researching for oss based network monitoring softwares, there are couple of options that are popular and commonly used, such as: nagios zenoss cacti zabbix functionality : 1. monitor heterogeneous network. 2. popup or mail alerts. 3. mail the alerts and create a task to helpdesk/ticketing systems(like otrs still evaluating). 4. monitor and alert specific services. 5. reports on various statistics being collected and graphs. 6. bandwidth usage and monitor. wishlist: an integrated solution with the following functionality also. 1. inventory management. 2. helpdesk/ticketing system. I would like the opinion of the group, as to what you guys use in such cases. feel free to suggest even if the software is not mentioned above. Regds, Arun. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [storage-discuss] Comstart - relationship between luns and targets
Peter Cudhea said the following, on 10/13/2009 09:41 PM: Sorry for the slow reply. In COMSTAR, the View is what *defines* the target <-> volume relation. Until there is a View, the LUN is not visible to initiators via any target at all, period. In other words, our sentence that "I have 3 target created from different volumes" doesn't make sense in COMSTAR. Remember, the basic comstar iSCSI model would be that all the LUNs visible through a single target, using LUN Mapping (i.e. views) to determine which LUNs are visible to each initiator. When you add multiple targets into the mix, nothing really changes.You as the storage administrator are in charge of whether the initiators see the same LUNs through all 3 targets or a different set of LUNs through each target. When you as the storage administrator create multiple targets for some reason, you must be the one to remember what is different between each target and the other ones. Peter Hi Peter, I've already discovered that creating a target doesn't make relation to LUN till a view is created. Anyway thanks for follow-up, Peter. -- Roman Naumenko ro...@frontline.ca ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] psycopg2 not installing on osol0906
Hi! I"m on osol0906, with python2.6 on a virtualenv. I want to install psycopg2 (postgres driver), but i'm not able to. I"ve tried both the methods, easy_install and python setup.py build both of them throws error. (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ python Python 2.6.1 (r261:67515, Mar 10 2009, 14:11:34) [C] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> ^D (venv)a...@opensolaris:/tmp$ cd psycopg2-2.0.13/ (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ ls AUTHORSdebian examples lib MANIFEST PKG-INFO psycopg2da scriptssetup.py ZPsycopgDA ChangeLog doc INSTALL LICENSE MANIFEST.in psycopg README setup.cfg tests (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ python setup.py build running build running build_py creating build creating build/lib.solaris-2.11-i86pc-2.6 creating build/lib.solaris-2.11-i86pc-2.6/psycopg2 copying lib/tz.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 copying lib/extensions.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 copying lib/pool.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 copying lib/__init__.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 copying lib/psycopg1.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 copying lib/extras.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 copying lib/errorcodes.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 running build_ext error: No such file or directory (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ easy_install psycopg2 Searching for psycopg2 Reading http://pypi.python.org/simple/psycopg2/ Reading http://initd.org/projects/psycopg2 Reading http://initd.org/pub/software/psycopg/ Best match: psycopg2 2.0.13 Downloading http://initd.org/pub/software/psycopg/psycopg2-2.0.13.tar.gz Processing psycopg2-2.0.13.tar.gz Running psycopg2-2.0.13/setup.py -q bdist_egg --dist-dir /tmp/easy_install-KfvzTB/psycopg2-2.0.13/egg-dist-tmp-cKek3m error: Setup script exited with error: No such file or directory also attaching the reply from federico, the developer and maintainer of the postgres driver. From: Federico Di Gregorio To: Arun Tomar Subject: Re: psycopg2 not installing on opensolaris Date: Tue, 18 Aug 2009 13:42:00 +0200 (17:12 IST) Il giorno dom, 16/08/2009 alle 18.26 +0530, Arun Tomar ha scritto: > i would like to report an issue about installation of psycopg2 driver > on opensolaris. > I'm using opensolaris 0906, build 111, using python 2.6. when i try to > install the postgres driver it gives the following error. is there any > way i can resolve this issue. This can be two different problem: a build problem on Solaris or an easy_install incompatibility. Plase build the standard way (python setup.py build) and report any error before going on with easy_install. federico kindly suggest a solution. regds, Arun Tomar. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] psycopg2 not installing on osol0906
Il giorno mer, 14/10/2009 alle 10.39 +0530, Arun Tomar ha scritto: > I"m on osol0906, with python2.6 on a virtualenv. I want to install > psycopg2 (postgres driver), but i'm not able to. > > I"ve tried both the methods, easy_install and python setup.py build > both > of them throws error. > > (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ python > Python 2.6.1 (r261:67515, Mar 10 2009, 14:11:34) [C] on sunos5 > Type "help", "copyright", "credits" or "license" for more information. > >>> ^D > > (venv)a...@opensolaris:/tmp$ cd psycopg2-2.0.13/ > (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ ls > AUTHORSdebian examples lib MANIFEST PKG-INFO > psycopg2da > scriptssetup.py ZPsycopgDA > ChangeLog doc INSTALL LICENSE MANIFEST.in psycopg README > setup.cfg tests > > (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ python setup.py build > running build > running build_py > creating build > creating build/lib.solaris-2.11-i86pc-2.6 > creating build/lib.solaris-2.11-i86pc-2.6/psycopg2 > copying lib/tz.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 > copying lib/extensions.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 > copying lib/pool.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 > copying lib/__init__.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 > copying lib/psycopg1.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 > copying lib/extras.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 > copying lib/errorcodes.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2 > running build_ext > error: No such file or directory setup.py does not find pg_config. Install the development packages for PostgreSQL. Hope this helps, federico -- Federico Di Gregorio http://people.initd.org/fog Debian GNU/Linux Developerf...@debian.org INIT.D Developer f...@initd.org Degli altri, della gente senza domande, si puo' fare a meno. -- macchinavapore signature.asc Description: Questa è una parte del messaggio firmata digitalmente ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] psycopg2 not installing on osol0906
On Wed, 2009-10-14 at 09:44 +0200, Federico Di Gregorio wrote:
> Il giorno mer, 14/10/2009 alle 10.39 +0530, Arun Tomar ha scritto:
> > I"m on osol0906, with python2.6 on a virtualenv. I want to install
> > psycopg2 (postgres driver), but i'm not able to.
> >
> > I"ve tried both the methods, easy_install and python setup.py build
> > both
> > of them throws error.
> >
> > (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ python
> > Python 2.6.1 (r261:67515, Mar 10 2009, 14:11:34) [C] on sunos5
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> ^D
> >
> > (venv)a...@opensolaris:/tmp$ cd psycopg2-2.0.13/
> > (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ ls
> > AUTHORSdebian examples lib MANIFEST PKG-INFO
> > psycopg2da
> > scriptssetup.py ZPsycopgDA
> > ChangeLog doc INSTALL LICENSE MANIFEST.in psycopg README
> > setup.cfg tests
> >
> > (venv)a...@opensolaris:/tmp/psycopg2-2.0.13$ python setup.py build
> > running build
> > running build_py
> > creating build
> > creating build/lib.solaris-2.11-i86pc-2.6
> > creating build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > copying lib/tz.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > copying lib/extensions.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > copying lib/pool.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > copying lib/__init__.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > copying lib/psycopg1.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > copying lib/extras.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > copying lib/errorcodes.py -> build/lib.solaris-2.11-i86pc-2.6/psycopg2
> > running build_ext
> > error: No such file or directory
>
> setup.py does not find pg_config. Install the development packages for
> PostgreSQL.
>
> Hope this helps,
> federico
>
Hi!
finally psycopg2 got installed, although it threw some warnings,
something related to static and non static declarations, but for now you
can ignore them.
here are the steps:
make sure these packages are intalled.
a...@opensolaris:~# pkg list|grep postgr
SUNWpostgr-83-client 8.3.7-0.111 installed
SUNWpostgr-83-devel 8.3.7-0.111 installed
SUNWpostgr-83-libs8.3.7-0.111 installed
SUNWpostgr-83-server 8.3.7-0.111 installed
#add postgres to the system path
a...@opensolaris:~# cat ~/.bashrc
#
# Define default prompt to @:<"($|#) ">
# and print '#' for user "root" and '$' for normal users.
#
export
PATH=/usr/gnu/bin:/usr/bin:/usr/X11/bin:/usr/sbin:/sbin:/opt/csw/bin:/opt/csw/sbin:/opt/sfw/bin:/usr/postgres/8.3/bin/64
export
MANPATH=/usr/gnu/share/man:/usr/share/man:/usr/X11/share/man:/opt/csw/share/man
#export the postgres library
export LD_LIBRARY_PATH=/usr/postgres/8.3/lib
PS1='${logna...@$(/usr/bin/hostname):$(
[[ "${LOGNAME}" == "root" ]] && printf "%s" "${PWD/${HOME}/~}# " ||
printf "%s" "${PWD/${HOME}/~}\$ ")'
#added by arun
export TERM=xterm-color
alias l='ls -l'
a...@opensolaris:~# svcs -a|grep postgres
disabled Oct_11
svc:/application/database/postgresql_83:default_32bit
online 13:47:49
svc:/application/database/postgresql_83:default_64bit
(venv)a...@opensolaris:~$ python
Python 2.6.1 (r261:67515, Mar 10 2009, 14:11:34) [C] on sunos5
Type "help", "copyright", "credits" or "license" for more information.
>>> import psycopg2
regds,
Arun.
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] swap purge
looking for some kind of tool that will let me release the swap space consumed by a process that was swapped out and its parent died. There is no way for this process to get back on the stack and its carcass consumes unrecoverable swap space. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
kill doesn't work? max Mike DeMarco wrote: looking for some kind of tool that will let me release the swap space consumed by a process that was swapped out and its parent died. There is no way for this process to get back on the stack and its carcass consumes unrecoverable swap space. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
> kill doesn't work? > > max Nothing to kill, the process was swapped out and the parent crashed out so there is no longer a owner of the swapped out process. It remains in swap until the next reboot at which time the kernel no longer has any idea about it so the swap space is free. I am looking for a tool that would let me examine the swap space allocations that the kernel must know about and send out a reaper to reclaim the space and tell the kernel to mark it as free. Tools to examine swapped out processes seem to be lacking. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
What state is the process in? How do you know it is swapped out? What problem is this causing? If the parent crashed, then init should inherit the child as its own, and it AFAIK does reap dead children periodically. If the process shows up as because the parent is not reaping it, then there should be no memory associated with it any longer (actually, there is enough to give the hint a process is still there, but the address space should have already been reclaimed, and what's left of the process now uses the kernel's address space until the parent can be notified). If you really want to force it into memory, then temporarily removing your swap device and re-adding it is one way of trying this, but may fail if you actually need the swap space. It's also a very heavy handed way of doing it ;-) Regards, Brian Mike DeMarco wrote: kill doesn't work? max Nothing to kill, the process was swapped out and the parent crashed out so there is no longer a owner of the swapped out process. It remains in swap until the next reboot at which time the kernel no longer has any idea about it so the swap space is free. I am looking for a tool that would let me examine the swap space allocations that the kernel must know about and send out a reaper to reclaim the space and tell the kernel to mark it as free. Tools to examine swapped out processes seem to be lacking. -- Brian Ruthven Solaris Revenue Product Engineering Sun Microsystems UK Sparc House, Guillemont Park, Camberley, GU17 9QG ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
From: Brian Ruthven - Sun UK To: Mike DeMarco Cc: opensolaris-discuss@opensolaris.org Sent: Wed, October 14, 2009 10:58:06 AM Subject: Re: [osol-discuss] swap purge What state is the process in? How do you know it is swapped out? What problem is this causing? If the parent crashed, then init should inherit the child as its own, and it AFAIK does reap dead children periodically. If the process shows up as because the parent is not reaping it, then there should be no memory associated with it any longer (actually, there is enough to give the hint a process is still there, but the address space should have already been reclaimed, and what's left of the process now uses the kernel's address space until the parent can be notified). If you really want to force it into memory, then temporarily removing your swap device and re-adding it is one way of trying this, but may fail if you actually need the swap space. It's also a very heavy handed way of doing it ;-) Regards, Brian Whenever we have had systems go deep into swap some software will fail and the processes that were swapped out will die. When this happens the swapped out process will remain in swap space, there is no pid to get back on the stack to pull the process back out of the swap abyss. So the swap space remains consumed until the next reboot. The kernel must know that the process is in swap since it swapped it out and is keeping track of it as shown by the w column of vmstat. There has to be a way to message this iformation in the kernel and tell the kernel to forget about that swapped out process it is never coming back. This would help my by allowing me to cleanup the disk space that is being consumed by swap instead of allocating more disk spaceto swap that is of no use. I have also found that unless the pid can pull back the swap space when swap -d is called the swap -d will fail since the kernel can not clear the swap file out fully to delete it. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] mail list added to Nabble
Hi folks, I happy to announce that I just added this mail-list on nabble. Mail list will be archived and accessed for posting/reading from: http://n2.nabble.com/Opensolaris-General-discuss-mail-list-f3823541.html Cheers! -- () ASCII Ribbon Campaign | Against HTML e-mail /\ www.asciiribbon.org | Against proprietary extensions -- () ASCII Ribbon Campaign | Against HTML e-mail /\ www.asciiribbon.org | Against proprietary extensions ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
How do you know that the processes represented in the 'w' column are in fact dead processes? This bring me back to my original question: What state is the process in? (i.e. how does it show up in a "ps -f" listing?) Do you have a reproducible test case to demonstrate this? Regards, Brian Mike DeMarco wrote: From: Brian Ruthven - Sun UK To: Mike DeMarco Cc: opensolaris-discuss@opensolaris.org Sent: Wed, October 14, 2009 10:58:06 AM Subject: Re: [osol-discuss] swap purge What state is the process in? How do you know it is swapped out? What problem is this causing? If the parent crashed, then init should inherit the child as its own, and it AFAIK does reap dead children periodically. If the process shows up as because the parent is not reaping it, then there should be no memory associated with it any longer (actually, there is enough to give the hint a process is still there, but the address space should have already been reclaimed, and what's left of the process now uses the kernel's address space until the parent can be notified). If you really want to force it into memory, then temporarily removing your swap device and re-adding it is one way of trying this, but may fail if you actually need the swap space. It's also a very heavy handed way of doing it ;-) Regards, Brian Whenever we have had systems go deep into swap some software will fail and the processes that were swapped out will die. When this happens the swapped out process will remain in swap space, there is no pid to get back on the stack to pull the process back out of the swap abyss. So the swap space remains consumed until the next reboot. The kernel must know that the process is in swap since it swapped it out and is keeping track of it as shown by the w column of vmstat. There has to be a way to message this iformation in the kernel and tell the kernel to forget about that swapped out process it is never coming back. This would help my by allowing me to cleanup the disk space that is being consumed by swap instead of allocating more disk spaceto swap that is of no use. I have also found that unless the pid can pull back the swap space when swap -d is called the swap -d will fail since the kernel can not clear the swap file out fully to delete it. -- Brian Ruthven Solaris Revenue Product Engineering Sun Microsystems UK Sparc House, Guillemont Park, Camberley, GU17 9QG ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
How do I know that the process is swapped out. Best answer I can give for this is that I don't. I have no tools that can tell me what processes are represented by the number that is in the "w" column in vmstat. I do know that once swap is hit this number will grow and stay > zero until the kernel is rebooted. I am looking for tools/methods to analyze the processes in swap determine if indeed they are unneeded and remove them since they will never be called out of swap and are consuming disk space. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] practical zfs implementation problem
> This card is great if you have PCI-X. I could not get > it to work using standard PCI slot. > > Wonder why MoBo manufacturers do not put PCI-X on > most motherboards? PCI-X cards will work in PCI motherboards. Just slower. There are also PCIe options if you have slots available. I have 2 Supermicro USAS-L8i PCIe cards in my server machine, each card can support 8 SATA or SAS drives directly and SAS expanders can allow more at the expense of bandwidth. Note that PCI maxes out at 133MB/sec. A single hard drive approaches that these days. If you don't mind that, PCI works great. The PCI-X card recommended is well known to work well. I would avoid the cheaper SATA controllers if you care about reliability. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
Hi Mike, Mike DeMarco wrote: How do I know that the process is swapped out. Best answer I can give for this is that I don't. I have no tools that can tell me what processes are represented by the number that is in the "w" column in vmstat. I do know that once swap is hit this number will grow and stay > zero until the kernel is rebooted. I am looking for tools/methods to analyze the processes in swap determine if indeed they are unneeded and remove them since they will never be called out of swap and are consuming disk space. The "w" column in vmstat is a count of the number of threads swapped out. A swapped out thread will not have 0x1 set in t_schedflag. You can find the process(es) the threads belong to by: # mdb -k > ::walk thread t | ::print kthread_t t_schedflag | ::grep "(.&1)==0" | ::eval (Starting at ::walk thread t is all one line.) max ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
Mike DeMarco wrote: How do I know that the process is swapped out. Best answer I can give for this is that I don't. I have no tools that can tell me what processes are represented by the number that is in the "w" column in vmstat. I do know that once swap is hit this number will grow and stay > zero until the kernel is rebooted. I am looking for tools/methods to analyze the processes in swap determine if indeed they are unneeded and remove them since they will never be called out of swap and are consuming disk space. A little follow up from my box. # vmstat 2 kthr memorypagedisk faults cpu r b w swap free re mf pi po fr de sr cd s0 s1 -- in sy cs us sy id 1 0 1 1551744 875932 51 488 6 285 349 0 17112 25 -0 11 0 935 160430 1503 11 9 80 0 0 11 1693076 1221836 0 117 213 0 0 0 0 74 0 0 0 540 433 498 0 1 99 0 0 11 1692408 1220544 0 89 307 0 0 0 0 89 0 0 0 586 314 555 1 0 99 So, 11 threads swapped out. Here is a list. # mdb -k Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs usba sockfs ip hook neti sctp arp uhci sd fctl lofs audiosup fcip random cpc crypto logindmux ptm ufs sppp ipc ] > ::walk thread t | ::print kthread_t t_schedflag | ::grep "(.&1)==0" | ::eval p_user.u_psargs = [ "/usr/lib/inet/in.ndpd" ] p_user.u_psargs = [ "/usr/sbin/avahi-daemon-bridge-dsd -D" ] p_user.u_psargs = [ "/usr/openwin/bin/fbconsole -n -d :0" ] p_user.u_psargs = [ "/usr/lib/thunderbird/thunderbird-bin" ] p_user.u_psargs = [ "/usr/lib/thunderbird/thunderbird-bin" ] p_user.u_psargs = [ "/usr/lib/thunderbird/thunderbird-bin" ] p_user.u_psargs = [ "/usr/lib/thunderbird/thunderbird-bin" ] p_user.u_psargs = [ "gnome-terminal" ] p_user.u_psargs = [ "gnome-terminal" ] p_user.u_psargs = [ "/usr/sbin/gdm-binary" ] p_user.u_psargs = [ "/usr/lib/rmvolmgr -s" ] > max ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
mdb -k Loading modules: [ unix genunix specfs dtrace ufs sd mpt px md ip hook neti sctp arp nca fcp fctl emlxs cpc random crypto zfs wrsmd fcip ssd logindmux ptm sppp nfs lofs ipc ] > ::walk thread t| ::print kthread_t t_schedflag | ::grep "(.&1)==0" | ::eval Usage: eval command > ::walk thread t| ::print kthread_t t_schedflag | ::grep "(.&1)==0" 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
> ::walk thread t | ::print kthread_t t_schedflag | ::grep "(.&1)==0" | ::eval < t=K | ::print kthread_t t_procp | ::print proc_t p_user.u_psargs p_user.u_psargs = [ "/lib/svc/bin/svc.configd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/sbin/nscd" ] p_user.u_psargs = [ "/usr/lib/crypto/kcfd" ] p_user.u_psargs = [ "/usr/platform/SUNW,SPARC-Enterprise/lib/sparcv9/oplhpd" ] p_user.u_psargs = [ "/usr/platform/SUNW,SPARC-Enterprise/lib/sparcv9/oplhpd" ] p_user.u_psargs = [ "/usr/lib/picl/picld" ] p_user.u_psargs = [ "/usr/lib/picl/picld" ] p_user.u_psargs = [ "/usr/sbin/rpcbind" ] p_user.u_psargs = [ "/usr/lib/nfs/statd" ] p_user.u_psargs = [ "/usr/lib/nfs/statd" ] p_user.u_psargs = [ "/usr/lib/nfs/nfsmapid" ] p_user.u_psargs = [ "/usr/openwin/bin/rpc.ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-cmsd" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/lib/dcs -l" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.configd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/usr/lib/crypto/kcfd" ] p_user.u_psargs = [ "/usr/sbin/rpcbind" ] p_user.u_psargs = [ "/usr/lib/nfs/statd" ] p_user.u_psargs = [ "/usr/lib/nfs/lockd" ] p_user.u_psargs = [ "/usr/lib/nfs/nfs4cbd" ] p_user.u_psargs = [ "/usr/lib/nfs/nfsmapid" ] p_user.u_psargs = [ "/usr/openwin/bin/rpc.ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-cmsd" ] p_user.u_psargs = [ "/usr/sbin/nscd" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/dt/bin/dtlogin -daemon" ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/lib/saf/ttymon -g -d /dev/console -l console -T vt100 -m ldterm,ttcompat - " ] p_user.u_psargs = [ "/usr/lib/dmi/dmispd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/usr/bin/pfksh" ] p_user.u_psargs = [ "/usr/bin/pfksh" ] p_user.u_psargs = [ " /usr/lib/saf/ttymon -g -d /dev/console -l console -m ldterm,ttcompat -h -p seie " ] p_user.u_psargs = [ "/usr/lib/sendmail -bd -q15m" ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] So is this telling me that a thread of rpcbind is still swapped out? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
Mike DeMarco wrote: mdb -k Loading modules: [ unix genunix specfs dtrace ufs sd mpt px md ip hook neti sctp arp nca fcp fctl emlxs cpc random crypto zfs wrsmd fcip ssd logindmux ptm sppp nfs lofs ipc ] ::walk thread t| ::print kthread_t t_schedflag | ::grep "(.&1)==0" | ::eval After ::eval, on the same line, you need: t_procp | ::print proc_t p_user.u_psargs Usage: eval command ::walk thread t| ::print kthread_t t_schedflag | ::grep "(.&1)==0" 4000 4000 4000 And 0x4000 is, according to /usr/include/sys/thread.h: #defineTS_RUNQMATCH0x4000/* exact run queue balancing by setbackdq() */ In particular, the TS_LOAD flag (0x1) is not set, indicating the thread is not in memory (ie., swapped out). If you want pid instead of arguments, you can use "p_pidp | ::print struct pid pid_id" instead of "p_user.u_psargs". max ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] update manager unresponsive
Glenn Holmer wrote: On Fri, 2009-10-02 at 12:16 -0500, Shawn Walker wrote: Glenn Holmer wrote: I've got several OpenSolaris machines that were installed with 2009.06. I updated to snv_123 (which was my first dev build), and would now like to update to snv_124. But when I start the Update Manager, it hangs at "Checking for new software". The status bar does not move. Is there something else I'm supposed to do to go from snv_123 to 124? Have you checked to see if there is any network activity? The update manager has to do quite a bit of work (including file retrieval) to check for updates at the moment. Eventually it became ready, but when I started the update, it went through a long "Preparing..." phase, then promptly timed out on the download. In that case, I have to start all over again (i.e. go through the preparation phase again)? Yes. But it won't have to download anything it has already downloaded. -- Shawn Walker ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] practical zfs implementation problem
1. Get LSI SAS hba, such as 3042(8 port) or 3041(4port), these are cheap and work better than marvel based. You may want to get hotswapable SAS mobile rack that can host 5 SAS/SATA disks so with LSI 3042, you can connect 10 disks from it, plus 4 onboard SATA, that gives you 14 disks. I suggest you use ECC RAM, and the more RAM the better. I believe AMD supports ECC. 2G ram is not enough to get good performance. I'm not sure if you are able to afford SLC SSD as zil, but it will help a lot. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
Mike DeMarco wrote: ::walk thread t | ::print kthread_t t_schedflag | ::grep "(.&1)==0" | ::eval < t=K | ::print kthread_t t_procp | ::print proc_t p_user.u_psargs p_user.u_psargs = [ "/lib/svc/bin/svc.configd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "devfsadmd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/lib/sysevent/syseventd" ] p_user.u_psargs = [ "/usr/sbin/nscd" ] p_user.u_psargs = [ "/usr/lib/crypto/kcfd" ] p_user.u_psargs = [ "/usr/platform/SUNW,SPARC-Enterprise/lib/sparcv9/oplhpd" ] p_user.u_psargs = [ "/usr/platform/SUNW,SPARC-Enterprise/lib/sparcv9/oplhpd" ] p_user.u_psargs = [ "/usr/lib/picl/picld" ] p_user.u_psargs = [ "/usr/lib/picl/picld" ] p_user.u_psargs = [ "/usr/sbin/rpcbind" ] p_user.u_psargs = [ "/usr/lib/nfs/statd" ] p_user.u_psargs = [ "/usr/lib/nfs/statd" ] p_user.u_psargs = [ "/usr/lib/nfs/nfsmapid" ] p_user.u_psargs = [ "/usr/openwin/bin/rpc.ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-cmsd" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/lib/dcs -l" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/usr/lib/fm/fmd/fmd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.configd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/usr/lib/crypto/kcfd" ] p_user.u_psargs = [ "/usr/sbin/rpcbind" ] p_user.u_psargs = [ "/usr/lib/nfs/statd" ] p_user.u_psargs = [ "/usr/lib/nfs/lockd" ] p_user.u_psargs = [ "/usr/lib/nfs/nfs4cbd" ] p_user.u_psargs = [ "/usr/lib/nfs/nfsmapid" ] p_user.u_psargs = [ "/usr/openwin/bin/rpc.ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-ttdbserverd" ] p_user.u_psargs = [ "/bin/sh /lib/svc/method/rpc-cmsd" ] p_user.u_psargs = [ "/usr/sbin/nscd" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/sadm/lib/smc/bin/smcboot" ] p_user.u_psargs = [ "/usr/dt/bin/dtlogin -daemon" ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/lib/saf/ttymon -g -d /dev/console -l console -T vt100 -m ldterm,ttcompat - " ] p_user.u_psargs = [ "/usr/lib/dmi/dmispd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/usr/bin/pfksh" ] p_user.u_psargs = [ "/usr/bin/pfksh" ] p_user.u_psargs = [ " /usr/lib/saf/ttymon -g -d /dev/console -l console -m ldterm,ttcompat -h -p seie " ] p_user.u_psargs = [ "/usr/lib/sendmail -bd -q15m" ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ " /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4 " ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] p_user.u_psargs = [ "/lib/svc/bin/svc.startd" ] So is this telling me that a thread of rpcbind is still swapped out? Correct. As well as thread(s) from svc.configd, svc.startd, devfsadmd, syseventd, etc. max ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
Thanks Max: This helps. Can you recommend good documentation/books for mdb? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] swap purge
Hi Mike, The only book I can recommend is Solaris Modular Debugger Guide, at http://docs.sun.com/app/docs/doc/816-5041?l=en If you look around a little, you'll probably find some good blog entries. Eric Schrock wrote a nice little puzzle a while ago (see http://blogs.sun.com/eschrock/entry/mdb_puzzle). I have also done a little with mdb, and blogged a bit about it at mbruning.blogspot.com. The best way to learn it is by experience. I recommend learning the data structures (header files work well for this), and trying to "see" the data structures via mdb. Of course, I think a very good way to come up to speed with it is to take a course. I would start with a Solaris Internals course, then take a course on kernel crash analysis and debugging. (But then, I _would_ recommend this, as I teach both.) max Mike DeMarco wrote: Thanks Max: This helps. Can you recommend good documentation/books for mdb? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] System svn b122 seriously jacked up during run
I've managed to do something serious to my system... build 122.. It took a hard reboot after showing signs of resource usage maxed out. Now on reboot I get hundreds maybe thousands of lines from system logger that look like this: Oct 14 13:57:29 svs.stated [828]: Could not commit state change for svc:/system/fcoe_initiator: default to reposititory: Not owner One thing I did... not sure if its relevant. I replaced the file /etc/users_attr with a symlink to a file elsewhere on the fs. Its a buffer I use as a mirror of a module checked out of cvs that contains many system related files. If that sounds confusing... it would look like: /etc/users_attr -> /cvsb/zfs/etc/users_attr The file at /cvsb/zfs/etc/users_attr is not directly under cvs control. So any kind of permission problems that might occur under cvs does not apply here. However if the OS demands a real copy of /etc/users_attr rather than a symlink then it might be relevant or even the source of the problem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] System svn b122 seriously jacked up during run
Harry Putnam writes: > One thing I did... not sure if its relevant. I replaced the file > /etc/users_attr with a symlink to a file elsewhere on the fs. Its a > buffer I use as a mirror of a module checked out of cvs that contains > many system related files. err yup that was it... after tediously replacing that file with no network ... no way to ssh scp etc... it boots right up. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] KeePassX under Opensolaris 2009.06
Has anymone manage to build KeePassX under Opensolaris 2009.06. I have sucsessful build Qt 4.52 and using gcc-432 from the package. As I have read on this post, it should be possible. http://de.opensolaris.org/jive/thread.jspa?messageID=366614 Can someone please explain to me how to tweak the compile flags like shown in the above post? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] emacs mappings on opensolaris
When I first started using opensolaris about a yr ago... some kind soul here told me how to set things up so that emacs works like it does on linux. Not having to use Esc-x instead of M-x for example.. and so that backspc does delete to the left... I don't recall if there was more but I've lost my notes about this... and my old .emacs file that contained it. I wonder if someone can coach me a bit before I commit suicide, or take an axe to RMS. (That may not be a smart thing to say on a solaris OS hehe). ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ssh root logins have quit working
I've enabled remote root logins long ago.. and have had no problems with it... but today... I started getting this message: Received disconnect from 192.168.0.29: 2: Too many authentication failures for root Even when it is the absolute first attempt. I was't able to discern where this message comes from. I guess from one of the ssh configs... but darned if I see it there. grep -rl 'Too many authentication' /etc didn't find it either. Looking at man sshd and man sshd_config... it appears my settings should be working. Somehow the OS thinks there have been multiple attempts at root login that failed... My logs show no such thing. At least `grep ssh /var/adm/messages' gets no hits... would that sort of stuff be somewhere else? Anyone have a guess what might be the problem. I think if it were a bum setting in sshd_config the message, if any at all, would not be what I am seeing. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] emacs mappings on opensolaris
Harry Putnam wrote: When I first started using opensolaris about a yr ago... some kind soul here told me how to set things up so that emacs works like it does on linux. Not having to use Esc-x instead of M-x for example.. and so that backspc does delete to the left... I don't recall if there was more but I've lost my notes about this... and my old .emacs file that contained it. I wonder if someone can coach me a bit before I commit suicide, or take an axe to RMS. (That may not be a smart thing to say on a solaris OS hehe). ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Is this it? http://www.mail-archive.com/opensolaris-discuss@opensolaris.org/msg38090.html It was the first thing google brought up when I entered "Harry Putnam emacs solaris". - Ali ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] log message repeating every second involving smb
Looks like today is my turn to have all sorts of troubles I don't know how to handle. I'm getting these log message once per second: Oct 14 16:48:53 zfs smbd[6138]: [ID 653746 daemon.notice] SmbLogon[corp\reader]: WRONG_PASSWORD Oct 14 16:48:54 zfs smbd[6138]: [ID 775558 daemon.debug] smb_door_srv_func: execute server routine(opcode=0) zfs is my hosts name. Is this a windows machine stuck on attempting to connect or the other way round? Ahhh I guess its coming from remote or some internal problem since shutting down the smb server stops the message. But of course, I need the server running... how can I tell what is going on? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] emacs mappings on opensolaris
Ali Bahrami writes: > Harry Putnam wrote: >> When I first started using opensolaris about a yr ago... some kind >> soul here told me how to set things up so that emacs works like it >> does on linux. >> >> Not having to use Esc-x instead of M-x for example.. and so that >> backspc does delete to the left... I don't recall if there was more >> but I've lost my notes about this... and my old .emacs file that >> contained it. >> >> I wonder if someone can coach me a bit before I commit suicide, or >> take an axe to RMS. (That may not be a smart thing to say on a solaris >> OS hehe). >> >> ___ >> opensolaris-discuss mailing list >> opensolaris-discuss@opensolaris.org > > Is this it? > > > http://www.mail-archive.com/opensolaris-discuss@opensolaris.org/msg38090.html > > It was the first thing google brought up when I entered "Harry >Putnam emacs solaris". How embarrassing... but yup ... In case you are a gmane user..(A maillist to NNTP gateway at news.gmane.org. You may like to know that the gmane conversion also mungs anthing that might look like an email address. Like the `disc...@opensolaris.org' part of the url you posted. But I just followed your lead and googled it myself... thanks. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GTK+ development packages?
Thanks for all the great information. It is very useful. My inclination is to use the Sun compiler since that would expose my code to the eyes of a different compiler (I find that to be a good thing in general). I have a feeling that, considering the various pressures on my time, I may just wait until the fixes you talked about have been integrated. Or maybe I won't wait. In any case, no matter what I end up doing your information has been quite helpful. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ssh root logins have quit working
I believe that you can no longer log in as root - you can use privilege escalation through pfexec for that or su once you login. Root logins are too insecure. On Wed, Oct 14, 2009 at 16:33, Harry Putnam wrote: > I've enabled remote root logins long ago.. and have had no problems > with it... but today... I started getting this message: > > Received disconnect from 192.168.0.29: 2: Too many authentication > failures for root > > Even when it is the absolute first attempt. > > I was't able to discern where this message comes from. I guess from > one of the ssh configs... but darned if I see it there. > > grep -rl 'Too many authentication' /etc didn't find it either. > > Looking at man sshd and man sshd_config... it appears my settings > should be working. > > Somehow the OS thinks there have been multiple attempts at root login > that failed... > > My logs show no such thing. At least `grep ssh /var/adm/messages' > gets no hits... would that sort of stuff be somewhere else? > > Anyone have a guess what might be the problem. > > I think if it were a bum setting in sshd_config the message, if any at > all, would not be what I am seeing. > > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > -- " ' With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' Those words were uttered by Judge Aaron Satie as wisdom and warning... The first time any man's freedom is trodden on we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron Satie, Star Trek: TNG episode "The Drumhead" - Alex Smith (K4RNT) - Murfreesboro/Nashville, Tennessee USA ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] bizarre X windows behavior on snv_124
I booted the most recent live CD image ( which is a DVD actually ) and the first two times my machine completely rebooted/crashed just after the desktop appears. I admit this is a strange machine ... it is a VIA C7 based embedded motherboard thing with 1GB of memory. I'll try to capture the output from SDDT. [1] I did manage to boot with the kmdb option enabled from GRUB and for whatever reasons the machine has been running for nearly 2 hours this time. However ... when I started firefox I seemed to have lost control of the mouse. I tried to resize a window and poof ... the window slammed to the left and Firefox became a tall thin line with just the slightest visible graphics in it. When I tried to move my mouse to resize that window my mouse would suddenly jump back to the upper left corner. I then tried to click on a window title and select "resize". It took a while but I was able .. and then I used the keyboard right arrow button to resize Firefox. However .. now the process won't stop and the window keeps getting wider and wider until it has left the current desktop window and seems to have expanded into the next desktop to the right. Iam not touching the keyboard and the window keeps growing. It took me about an hour of carefully moving the mouse in hopes that I got lucky and it would land in the right place to allow me to double click on the SDDT icon ... and then later I opened a terminal and tried to resize it. What you see is the best I could do : [1] http://www.blastwave.org/dclarke/OpenSolaris/snv_124/via_c7_000.png [2] http://www.blastwave.org/dclarke/OpenSolaris/snv_124/via_c7_001.png I have given up on trying to resize Firefox. I'm waiting for the enevitable panic with some data on the screen from kmdb ... but it has not happened yet. Is there any info worth gathering from this ... since its currently alive ? -- Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] bizarre X windows behavior on snv_124
Dennis Clarke wrote: > However ... when I started firefox I seemed to have lost control of > the mouse. I tried to resize a window and poof ... the window slammed > to the left and Firefox became a tall thin line with just the slightest > visible graphics in it. When I tried to move my mouse to resize that > window my mouse would suddenly jump back to the upper left corner. That's a well known bug on x86 CPU's with SSE support. Fortunately, Jürgen has provided a workaround: http://defect.opensolaris.org/bz/show_bug.cgi?id=9862#c10 I putback a change to the X gate for build 126 that disables use of the SIGIO signal handlers altogether until the kernel guys can fix the underlying register bug. -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] bizarre X windows behavior on snv_124
> Dennis Clarke wrote: >> However ... when I started firefox I seemed to have lost control of >> the mouse. I tried to resize a window and poof ... the window slammed >> to the left and Firefox became a tall thin line with just the slightest >> visible graphics in it. When I tried to move my mouse to resize that >> window my mouse would suddenly jump back to the upper left corner. > > That's a well known bug on x86 CPU's with SSE support. Fortunately, > Jürgen has provided a workaround: > > http://defect.opensolaris.org/bz/show_bug.cgi?id=9862#c10 > > I putback a change to the X gate for build 126 that disables use of the > SIGIO signal handlers altogether until the kernel guys can fix the > underlying register bug. > > -- > -Alan Coopersmith- alan.coopersm...@sun.com >Sun Microsystems, Inc. - X Window System Engineering thank you very much ! That has to be the fastest and most awesome support response I have ever seen here! hence : http://www.blastwave.org/dclarke/OpenSolaris/index.html -- Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
