Re: [osol-discuss] b134 freezes
More info, sorry for spamming ... > 1. The kernel freezes for a few hundred ms in b134 > (does not happen in b133). More specifically when the kernel "freezes" nothing else works, mouse stops, real time priority class processes stop, keyboard input stops, etc. Not sure about network (wireless) or other I/O. Actually according to vmstat the kernel does not "freeze" but suddenly gets many threads running making the system completely unresponsive to the user. I wonder what it is doing and why. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b134 freezes
There are two problems now ... I bet I was a bit confusing, sorry. 1. The kernel freezes for a few hundred ms in b134 (does not happen in b133). Number of running kernel threads jumps up suddenly - see the vmstat output. No clue why. 2. Firefox dies/freezes and cannot be killed (kill -9 has no effect) - this happens on both b133 and b134. This also prevents (clean) reboot, must force poweroff (by hw). At the moment I think this might be due to swap on zfs on (external) sd. But I do not have enough evidence yet. Maybe compression=on is not a good idea for swap (it does have a bad feeling)? I wonder why I left it on ... -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with creating logical using in OpenSolaris 2009.06
Thank you so much for responding :-) I just read that you need to reboot! -Original Message- From: Ignacio Marambio Catán [mailto:darkjo...@gmail.com] Sent: Thursday, March 18, 2010 5:08 PM To: Jeff Freeman Cc: opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] Problem with creating logical using in OpenSolaris 2009.06 you probably need to restart the server after installing the storage-server package in order for some of the relevant kernel modules to load. have you done that? nacho On Thu, Mar 18, 2010 at 6:03 PM, Jeff Freeman wrote: > I've just finished installing storage-server and so now I am at the step to 'Create a ligical unit using the volume' command: sbdadm create-lu /dev/zvol/rdsk/pool_1/vol_1 > > I keep getting "Unable to open device. Is the driver attached?" I've never see this message before. > -- > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b134 freezes
Jouko Holopainen wrote: > The firefox freezes completely (unkillble process, must force shutdown) in > b134. > > Now I'm investigating if swap (on zfs on sd disk) might be part of problem. I've seen this behavior on snv_132 using an sd disk as well (running nightly builds, nothing interactive). Unfortunately the machine is locked tight; I am unable to even break into kmdb through serial (dual-core machine). Steve ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] MythTV
Yes please! There are some simple use-cases that would be extremely helpful, long before worrying about device driver support for tuner cards: 1 packaging convenience for various ancilliary but vital components that can run away from the main myth box (e.g. mythweb server) 2 a supplementary backend, running local to the storage which is of course already in ZFS (e.g. for commflag and transcode jobs). This leaves room for a smaller or less-loaded primary, still on linux. It would also reduce network traffic and (by avoiding NFS) reduce sync-write load from transcodes. 3 a backend using external network tuners that don't need special driver support (e.g. HDHomeRun). 4 basic frontend / player support, perhaps first as a secondary frontend before solving all the issues with being a primary. For example, I'd love to be able to use my laptop to edit recordings (add cutpoints and trim ads), preview recordings (enough to see and kill duplicates) or even watch the odd recording even if it doesn't have the greatest sound or perfectly smooth 1080p HD playback). I can already get most of the way to point 3 using xvm and a linux (gentoo in my case) domU, though I still need NFS. Even when it comes to tuner support, some tuner devices may be much easier to support than others; we don't necessarily need support for every one. I'd happily replace some tuners (probably with hdhomeruns) if it also allowed me to replace linux. Regardless, the point of this post is to show that this is the last problem to worry about, not the first. -- Dan. pgpaqy4eyK18e.pgp Description: PGP signature ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problems with adding package to the local repo
This log /var/svc/log/application-pkg-server:default.log exists but the last information it has is the pkg server restart that I did last time. The pkg/log_errors property wasn't changed when I set this up and is set to 'stderr' svccfg -s pkg/server listprop pkg/log_errors pkg/log_errors astring stderr Which I assume goes to the default log. I'll to turn off the service and do mess with it manually, although I am not sure what I'd be doing. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problems with adding package to the local repo
On 03/18/10 05:29 PM, melbogia wrote: I just tried that and got the same error. Where would the logs be for the depot server? Is it the same as pkg/server logs at the following location? /var/svc/log/application-pkg-server:default.log I looked at that but the last thing it has is when I restarted the pkg/server service. This should have it: /var/svc/log/application-pkg-server:default.log ..unless you've set the pkg/log_errors property, in which case, they'll go to wherever that indicates. It's hard to help debug further. The best suggestion I could give would be to disable the SMF service temporarily, and run the pkg.depotd from the command line manually in another window: /usr/lib/pkg.depotd -d /path/to/repo -p Cheers, -- Shawn Walker ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] opensolaris updates...
On Thu, Mar 18, 2010 at 3:35 PM, Alexander wrote:
> I know, it was discussed many times. I know, that it is maybe the wrong
> place to ask :). But anyway...
> For now Solaris security updates are non-free. OpenSolaris /dev is not a
> good choice for a server. OpenSolaris support repository is closed... Is
> there any way to receive secure (Open)Solaris system for free (or at least
> for small price...) or we are forced to migrate our SRSS server to CentOS?
> I wouldn't like to port our hal patches there and don't like to use system
> without ZFS, but are there any alternatives?
>
AFAIK, no.
Threatening to migrate to another OS is totally unnecessary to the
discussion but I'm assuming you want to get Oracle management's attention,
right ? I'm not sure if they are reading this mailing list. Otherwise you're
not helping yourself get an answer.
I've been to the Oracle Sun Welcome Event just today all I can say is that
they spent no more than 15 seconds talking about OpenSolaris ("it's a
distribution for experimenting with new features") and a good half hour
about Solaris premium support plans. But it was a marketing event so I did
not expect any real content besides PR bullshit.
You mentioned "or at least a small price". Perhaps you can talk to a Oracle
rep and check what the real costs are and see if they are within your
budget.
I do hope Oracle embraces total open development and remove these and other
barriers to adoption. But OpenSolaris is not a grass root project like Linux
or some of the BSD flavors that started from zero as open projects. You've
got a product that was developed for years as closed source. Changing
processes and creating a community takes time. The upstream vendor
exercicing "selective open development" doesn't help either. But I'm
optimistic.
--
Giovanni
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problems with adding package to the local repo
I just tried that and got the same error. Where would the logs be for the depot server? Is it the same as pkg/server logs at the following location? /var/svc/log/application-pkg-server:default.log I looked at that but the last thing it has is when I restarted the pkg/server service. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Three heads on GeForce 8600 Video Card
On 03/18/10 05:17 PM, robs wrote: I've got two monitors hooked-up to the DVI ports of a GeForce 8600 video card. Recently moved the computer into the living-room, and want to run my TV off of the s-video port. I've tried numerous different settings, but can only get two heads to work at the same time. Not possible. Only two outputs per GPU can be active at the same time. You need to add a second card. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b134 freezes
On Thu, Mar 18, 2010 at 4:14 PM, Jouko Holopainen wrote: > The firefox freezes completely (unkillble process, must force shutdown) in > b134. > > Now I'm investigating if swap (on zfs on sd disk) might be part of problem. > In your first email you said that the kernel freezes, right? Is the system totally unresponsive or just Firefox ? Try using pkill/preap to kill Firefox. -- Giovanni ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problems with adding package to the local repo
On 03/18/10 04:57 PM, melbogia wrote: Hello, I downloaded a package using pkgrecv and now I am trying to add it to the local repository. I keep getting this error that I don't know how to fix or what the problem is eval `pkgsend -s http://localhost:80/ open fac...@1.5.7%2c5.11-0.1%3a20091019t112931z` Did you try fac...@1.5.7,5.11-0.1:20091019T112931Z ? You should check the server logs for your depot server, as the '500' error indicates that the server didn't like something you tried to do. Cheers, -- Shawn Walker ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] problems with adding package to the local repo
Hello, I downloaded a package using pkgrecv and now I am trying to add it to the local repository. I keep getting this error that I don't know how to fix or what the problem is eval `pkgsend -s http://localhost:80/ open fac...@1.5.7%2c5.11-0.1%3a20091019t112931z` pkgsend: 'open' failed for transaction ID 'None'; status '500': http://localhost:80/ doesn't speak a known version of open operation I have the local repository running on localhost at port 80. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] MythTV
On Fri, 19 Mar 2010 06:24:29, James Lever wrote: > On 19/03/2010, at 12:20 AM, homerun wrote: > >> Just asking , is there interest to port MythTV to OpenSolaris. >> http://www.mythtv.org/ > > There is definite interest. > > Ken Mays reported building it from source on desktop-discuss quite some time > ago and when I queried him about it late last year he responded saying, > > ??" > You need a few dependencies which are now a part of OSOL. > > Use this web page as a guide to what you need: > http://www.mythtv.org/wiki/Dependencies_(Building_from_source) > ??? > > I would be interested in having a regular binary build in that I can pull > from a repository mostly because I?ve still not found time to build from > source. > > I think the main benefit of MythTV on OSOL at the moment is either as a > frontend or as a slave backend or backend with network tuners due to capture > card support in the operating system. > > Me?. I would be using it as a primary dedicated backend with a pair of > HDHomeRun DVB-T tuners :) I would be very interested in MythTV on Opensolaris. I run an Opensolaris server in my basement, but also a Mythdora (MythTV on Fedora Linux) system which I have turn itself on and off based upon recording schedules. It would be very desirable to put the Myth backend on the Opensolaris system, powered on all the time, and just use the Mythdora machine as a front-end. Where I live, we get good over the air reception, so I primarily use OTA for recording. I think the biggest stumbling block to supporting MythTV on Opensolaris will be the wide variety of tuners out there. There are a lot of them, and keeping up with all the drivers folks may want to use is daunting. Jon - _/ _/ / - Jonathan Loran - - -/ / /IT Manager - - _ / _ / / Space Sciences Laboratory, UC Berkeley -/ / / (510) 643-5146 jlo...@ssl.berkeley.edu - __/__/__/ AST:7731^29u18e3 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Three heads on GeForce 8600 Video Card
I've got two monitors hooked-up to the DVI ports of a GeForce 8600 video card. Recently moved the computer into the living-room, and want to run my TV off of the s-video port. I've tried numerous different settings, but can only get two heads to work at the same time. Has anyone done this? If so, do you have an xorg.conf file that you can share? Thanks, --Robs ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with creating logical using in OpenSolaris 2009.06
you probably need to restart the server after installing the storage-server package in order for some of the relevant kernel modules to load. have you done that? nacho On Thu, Mar 18, 2010 at 6:03 PM, Jeff Freeman wrote: > I've just finished installing storage-server and so now I am at the step to > 'Create a ligical unit using the volume' command: sbdadm create-lu > /dev/zvol/rdsk/pool_1/vol_1 > > I keep getting "Unable to open device. Is the driver attached?" I've never > see this message before. > -- > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Problem with creating logical using in OpenSolaris 2009.06
I've just finished installing storage-server and so now I am at the step to 'Create a ligical unit using the volume' command: sbdadm create-lu /dev/zvol/rdsk/pool_1/vol_1 I keep getting "Unable to open device. Is the driver attached?" I've never see this message before. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Heap corruption, possibly hotswap related (snv_134 with imr_sas, nvdisk drivers)
2010/3/18 Kaya Bekiroğlu : > I first noticed this panic when conducting hot-swap tests. However, > now I see it every hour or so, even when all drives are attached and > no ZFS resilvering is in progress. It appears that these panics recur on my system when the zfs-auto-snapshot service runs. Disabling the hourly zfs-auto-snapshot service prevents the panic. The panic appears to be load-related, which explains why it can also occur around hot swap, but perhaps drivers are not to blame. > Repro: > - Pull a drive > - Wait for drive absence to be acknowledged by fm > - Physically re-add the drive > > This machine contains two LSI 9240-8i SAS controllers running imr_sas > (the driver from LSI's website) and a umem NVRAM card running the > nvdisk driver. It also contains an SSD L2ARC. > > Mar 17 16:00:10 storage genunix: [ID 478202 kern.notice] kernel memory > allocator: > Mar 17 16:00:10 storage genunix: [ID 432124 kern.notice] buffer freed > to wrong cache > Mar 17 16:00:10 storage genunix: [ID 815666 kern.notice] buffer was > allocated from kmem_alloc_160, > Mar 17 16:00:10 storage genunix: [ID 530907 kern.notice] caller > attempting free to kmem_alloc_48. > Mar 17 16:00:10 storage genunix: [ID 563406 kern.notice] > buffer=ff0715c74510 bufctl=0 cache: kmem_alloc_48 > Mar 17 16:00:10 storage unix: [ID 836849 kern.notice] > Mar 17 16:00:10 storage ^Mpanic[cpu7]/thread=ff002de17c60: > Mar 17 16:00:10 storage genunix: [ID 812275 kern.notice] kernel heap > corruption detected > Mar 17 16:00:10 storage unix: [ID 10 kern.notice] > Mar 17 16:00:10 storage genunix: [ID 655072 kern.notice] > ff002de17a70 genunix:kmem_error+501 () > Mar 17 16:00:10 storage genunix: [ID 655072 kern.notice] > ff002de17ac0 genunix:kmem_slab_free+2d5 () > Mar 17 16:00:10 storage genunix: [ID 655072 kern.notice] > ff002de17b20 genunix:kmem_magazine_destroy+fe () > Mar 17 16:00:10 storage genunix: [ID 655072 kern.notice] > ff002de17b70 genunix:kmem_cache_magazine_purge+a0 () > Mar 17 16:00:10 storage genunix: [ID 655072 kern.notice] > ff002de17ba0 genunix:kmem_cache_magazine_resize+32 () > Mar 17 16:00:10 storage genunix: [ID 655072 kern.notice] > ff002de17c40 genunix:taskq_thread+248 () > Mar 17 16:00:10 storage genunix: [ID 655072 kern.notice] > ff002de17c50 unix:thread_start+8 () > Mar 17 16:00:10 storage unix: [ID 10 kern.notice] > Mar 17 16:00:10 storage genunix: [ID 672855 kern.notice] syncing file > systems... > Mar 17 16:00:10 storage genunix: [ID 904073 kern.notice] done > Mar 17 16:00:11 storage genunix: [ID 111219 kern.notice] dumping to > /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel > Mar 17 16:00:11 storage ahci: [ID 405573 kern.info] NOTICE: ahci0: > ahci_tran_reset_dport port 0 reset port > > I'd file this directly to the bug database but I'm waiting for my > account to be reactivated. > > zpool status: > pool: tank > state: ONLINE > scrub: resilver completed after 0h0m with 0 errors on Thu Mar 18 10:07:12 > 2010 > config: > > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > c6t15d1 ONLINE 0 0 0 > c6t14d1 ONLINE 0 0 0 > c6t13d1 ONLINE 0 0 0 > raidz1-1 ONLINE 0 0 0 > c6t12d1 ONLINE 0 0 0 > c6t11d1 ONLINE 0 0 0 > c6t10d1 ONLINE 0 0 0 > raidz1-2 ONLINE 0 0 0 > c6t9d1 ONLINE 0 0 0 > c6t8d1 ONLINE 0 0 0 > c5t9d1 ONLINE 0 0 0 > logs > c7d1p0 ONLINE 0 0 0 > cache > c4t0d0p2 ONLINE 0 0 0 > spares > c5t8d1 AVAIL > > -- > Kaya > -- Kaya ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] MythTV
On 19/03/2010, at 12:20 AM, homerun wrote: > Just asking , is there interest to port MythTV to OpenSolaris. > http://www.mythtv.org/ There is definite interest. Ken Mays reported building it from source on desktop-discuss quite some time ago and when I queried him about it late last year he responded saying, “”" You need a few dependencies which are now a part of OSOL. Use this web page as a guide to what you need: http://www.mythtv.org/wiki/Dependencies_(Building_from_source) “”” I would be interested in having a regular binary build in that I can pull from a repository mostly because I’ve still not found time to build from source. I think the main benefit of MythTV on OSOL at the moment is either as a frontend or as a slave backend or backend with network tuners due to capture card support in the operating system. Me…. I would be using it as a primary dedicated backend with a pair of HDHomeRun DVB-T tuners :) cheers, James ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b134 freezes
The firefox freezes completely (unkillble process, must force shutdown) in b134. Now I'm investigating if swap (on zfs on sd disk) might be part of problem. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] opensolaris updates...
I know, it was discussed many times. I know, that it is maybe the wrong place to ask :). But anyway... For now Solaris security updates are non-free. OpenSolaris /dev is not a good choice for a server. OpenSolaris support repository is closed... Is there any way to receive secure (Open)Solaris system for free (or at least for small price...) or we are forced to migrate our SRSS server to CentOS? I wouldn't like to port our hal patches there and don't like to use system without ZFS, but are there any alternatives? //The only question my chief is thinking about is why we have bought SunRay terminals but not some multi-protocol terminal devices from Fujitsu or HP... :) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Trying to Install storage-server package - unsuccessful on 2009.06
Can anyone help me with the following problem? I just completed a clean install of opensolaris 2009.06 and wanted to install ComStar - I'm getting the following error when attempting to install: jfree...@pular:/dev/zvol/rdsk# pfexec pkg install storage-server Creating Plan | [b]pkg: Could not retrieve manifest 'storage-ser...@0.1%2c5.11-0.111%3a20090508t165041z' from 'http://pkg.opensolaris.org/release' URLError, reason: (8, 'node name or service name not known')[/b] jfree...@pular:/dev/zvol/rdsk# -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b134 freezes
Hi Jouko sorry I haven't tried b134 I will try this weekend on my eee 701. and let me check about firefox problem as you say. -masafumi On 2010/03/19, at 1:12, Jouko Holopainen wrote: > My EeePC701 works quite nicely with b133 (from Masafumi Ohta), except some > reliability problems with Firefox (resulting in unkillable firefox process). > > But after upgrade to 134 the kernel freezes about every ten seconds for very > long time (maybe 200-500ms?): > $ vmstat 1 > kthr memorypagedisk faults cpu > r b w swap free re mf pi po fr de sr cd s0 -- -- in sy cs us sy id > 3 0 0 1174864 447184 127 826 9 0 0 0 332 32 4 0 0 471 5983 2075 17 30 53 > 0 0 0 1240148 320888 17 39 0 0 0 0 0 0 0 0 0 417 497 243 3 2 95 > 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 441 400 256 2 1 97 > 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 440 408 251 3 1 96 > 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 0 0 0 433 347 282 2 2 96 > 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 12 0 0 466 377 382 3 1 96 > 19 0 0 1240148 320924 0 0 0 0 0 0 0 0 25 0 0 363 128 53 1 91 8 > 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 3 0 0 428 394 317 3 2 95 > 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 8 0 0 434 373 312 3 1 96 > 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 14 0 0 453 406 340 2 2 96 > 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 431 365 242 3 1 96 > 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 423 361 236 2 1 97 > 0 0 0 1240148 320940 0 0 0 0 0 0 0 0 0 0 0 417 346 230 3 2 95 > 0 0 0 1240148 320940 0 0 0 0 0 0 0 0 0 0 0 429 357 251 2 1 97 > 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 455 726 413 3 1 96 > 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 424 363 238 3 2 95 > 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 435 348 246 3 1 96 > 10 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 357 155 49 1 88 11 > 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 416 395 246 2 1 97 > > Even real time priority class processes stop for that time. Note that b133 > does not have this problem. > > What could be the cause? How can I try to find out the problem? > -- > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org Masafumi Ohta a Leader of Tokyo OpenSolaris User Group mailto:masafumi.o...@gmail.com http://www.twitter.com/masafumi_ohta ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] b134 freezes
My EeePC701 works quite nicely with b133 (from Masafumi Ohta), except some reliability problems with Firefox (resulting in unkillable firefox process). But after upgrade to 134 the kernel freezes about every ten seconds for very long time (maybe 200-500ms?): $ vmstat 1 kthr memorypagedisk faults cpu r b w swap free re mf pi po fr de sr cd s0 -- -- in sy cs us sy id 3 0 0 1174864 447184 127 826 9 0 0 0 332 32 4 0 0 471 5983 2075 17 30 53 0 0 0 1240148 320888 17 39 0 0 0 0 0 0 0 0 0 417 497 243 3 2 95 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 441 400 256 2 1 97 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 440 408 251 3 1 96 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 0 0 0 433 347 282 2 2 96 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 12 0 0 466 377 382 3 1 96 19 0 0 1240148 320924 0 0 0 0 0 0 0 0 25 0 0 363 128 53 1 91 8 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 3 0 0 428 394 317 3 2 95 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 8 0 0 434 373 312 3 1 96 0 0 0 1240140 320916 0 0 0 0 0 0 0 0 14 0 0 453 406 340 2 2 96 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 431 365 242 3 1 96 0 0 0 1240148 320924 0 0 0 0 0 0 0 0 0 0 0 423 361 236 2 1 97 0 0 0 1240148 320940 0 0 0 0 0 0 0 0 0 0 0 417 346 230 3 2 95 0 0 0 1240148 320940 0 0 0 0 0 0 0 0 0 0 0 429 357 251 2 1 97 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 455 726 413 3 1 96 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 424 363 238 3 2 95 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 435 348 246 3 1 96 10 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 357 155 49 1 88 11 0 0 0 1240148 320944 0 0 0 0 0 0 0 0 0 0 0 416 395 246 2 1 97 Even real time priority class processes stop for that time. Note that b133 does not have this problem. What could be the cause? How can I try to find out the problem? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] MythTV
On 03/18/10 10:20 AM, homerun wrote: Greetings Just asking , is there interest to port MythTV to OpenSolaris. http://www.mythtv.org/ How long will the supported list of video capture cards be useful? The notices I've been receiving from Comcast sound like they are moving to most programming being delivered as encrypted digital. If this an indication of where the industry is moving, how useful will the boards be that only support over the air (ATSC) or unencrypted cable (clear QAM)? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] MythTV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.03.2010 15:20, homerun wrote: > Greetings > > Just asking , is there interest to port MythTV to OpenSolaris. > http://www.mythtv.org/ Actuall, I'd have a personal interest (as an end user) for this. A mini-itx box running OpenSolaris would make for a _PERFECT_ "personal DVR" ;) //Svein - -- - +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE - +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - Picture Gallery: https://gallery.stillbilde.net/v/svein/ - -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuiQ7sACgkQSBMQn1jNM7asbwCeMYhH+fpu9gE7bujI8vTSIOie Gs8AoOQZB+c1v4J6rVWmjnaaVhIVWfkI =fPIN -END PGP SIGNATURE- ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Asterisk
I don't believe you HAVE to run zap; you can run a timer module if i remember right. I haven't done a lot with Asterisk in a few years beyond "usage".. We were a very early adopter of it and liked it a lot. The zaptel drivers were used early on for several timing functions, especially related to conference calls / meetme. Our Asterisk runs inside an OpenVZ container on Linux and I don't see any zap modules loaded at the host nor container levels. We don't use a lot of the functions any more, generally speaking we've migrated more to skype / IM for most things we initially used Asterisk for - once we have an established relationship with a customer many of them are preferring other solutions than a traditional phone... -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] MythTV
Greetings Just asking , is there interest to port MythTV to OpenSolaris. http://www.mythtv.org/ -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 2010.03 OSOL improvements regarding 3G USB HSDPA modems? Android+OSOL?
Thanks Ken! I will do that and see if somebody can help me. I'm at work at the moment, but will post the output of "mdb -k ::prtusb -i e -v" command once I get home to my personal computer. Can't wait to get Open Solaris to work on my computer. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 2010.03 OSOL improvements regarding 3G USB HSDPA modems? Android+OSOL?
Thanks Matthias for your comments! Wireless router that supports my 3G is actually a very good idea (these are pretty cheap today I suppose) and the possible solution I will use if I will not get this 3G USB modem to work with the configuration tips I might get from other users. Thanks for your thoughts! -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] setting date to iso 8601 (YYYY-MM-DD)
Thanks! So, I wrote a quick script to look through the options available to me with locale -a, and then run the date command. Output is attached. The closest thing to what I was after was zh_CN.UTF-8, which I now set via this line in .bashrc export LC_TIME=zh_CN.UTF-8 (I work in Beijing, so it is appropriate anyway.) I did find iso_8859_1 in the list, which gives this output: iso_8859_1 Thu Mar 18 08:16:39 CST 2010 I'll file a CR to get 8601 added. Regards, --Robs On 2010年03月17日 14:17, Hemantha Holla wrote: On 16/03/10 13:10, robs wrote: Hi. Although as a PROUD American, I PROUDLY use en_US.UTF-8, I'd really like to go the -MM-DD route for displaying time. Not only as returned by date, but displayed by %s in thunderbird in the mailnews.reply_header_authorwrote preference. I'm thinking this would be done using LC_TIME, but cannot come-up with anything after a bit of searching. Pointers would be appreciated. Have a look at http://kb.mozillazine.org/Date_display_format. But I couldn't find en_DK locale definitions in any of the system/locale/* packages on build 134 though. HTH Hemantha ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org C Thu Mar 18 08:16:38 CST 2010 POSIX Thu Mar 18 08:16:38 CST 2010 ar_AE.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_BH.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_DZ.UTF-8 اÙخ٠ÙØ³Ø 18 Ù Ø§Ø±Ø³Ø 2010 CST 08:16:38 ص ar_EG.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_IQ.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_JO.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ø¢Ø°Ø§Ø±Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_KW.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_LY.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_MA.UTF-8 اÙخ٠ÙØ³Ø 18 Ù Ø§Ø±Ø³Ø 2010 CST 08:16:38 ص ar_OM.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_QA.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_SA.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص ar_TN.UTF-8 اÙخ٠ÙØ³Ø 18 Ù Ø§Ø±Ø³Ø 2010 CST 08:16:38 ص ar_YE.UTF-8 اÙخ٠ÙØ³Ø Ù¡Ù¨ Ù Ø§Ø±Ø³Ø Ù¡Ù CST Ù¨:١٦:٣٨ ص be_BY.UTF-8 ÑаÑвеÑ, 18 ÑакавÑк 2010 08.16.38 CST bg_BG.UTF-8 18 маÑÑ 2010, ÑеÑвÑÑÑÑк 08:16:38 CST ca_ES.UTF-8 dijous 18 de març de 2010 08:16:38 CST cs_CZ.UTF-8 Ätvrtek, 18. bÅezna 2010 08:16:38 CST da_DK.UTF-8 torsdag den 18. marts 2010 08.16.38 CST de.UTF-8 Donnerstag, 18. März 2010, 08:16:38 Uhr CST de_AT.UTF-8 Donnerstag, 18. März 2010, 08:16:38 Uhr CST de_BE.UTF-8 Donnerstag 18 März 2010, 08 h 16 min 38 s CST de_CH.UTF-8 Donnerstag, 18. März 2010, 08:16:38 Uhr CST de_DE.UTF-8 Donnerstag, 18. März 2010, 08:16:38 Uhr CST de_LI.UTF-8 Donnerstag, 18. März 2010, 08:16:38 Uhr CST de_LU.UTF-8 Donnerstag, 18. März 2010, 08:16:38 Uhr CST el.UTF-8 Î ÎμÏÏη, 18 ÎαÏÏÎ¯Î¿Ï 2010 08:16:38 Ï.μ. CST el_CY.UTF-8 Î ÎμÏÏη, 18 ÎαÏÏÎ¯Î¿Ï 2010 08:16:38 Ï.μ. CST el_GR.UTF-8 Î ÎμÏÏη, 18 ÎαÏÏÎ¯Î¿Ï 2010 08:16:38 Ï.μ. CST en_AU.UTF-8 Thursday, 18 March 2010 08:16:38 AM CST en_BW.UTF-8 Thursday 18 March 2010 08:16:38 AM CST en_CA.UTF-8 Thursday, March 18, 2010 08:16:38 AM CST en_GB.UTF-8 Thursday, 18 March 2010 08:16:38 CST en_HK.UTF-8 Thursday, March 18, 2010 08:16:38 AM CST en_IE.UTF-8 Thursday 18 March 2010 08:16:38 CST en_IN.UTF-8 Thursday 18 March 2010 08:16:38 AM CST en_MT.UTF-8 Thursday, 18 March 2010 08:16:38 CST en_NZ.UTF-8 Thursday, 18 March 2010 08:16:38 AM CST en_PH.UTF-8 Thursday, March 18, 2010 08:16:38 AM CST en_SG.UTF-8 Thursday, March 18, 2010 08:16:38 AM CST en_US.UTF-8 Thursday, March 18, 2010 08:16:38 AM CST en_ZW.UTF-8 Thursday 18 March 2010 08:16:38 AM CST es.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_AR.UTF-8 jueves 18 de marzo de 2010 08h'16:38 CST es_BO.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_CL.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_CO.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_CR.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_DO.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_EC.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_ES.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_GT.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_HN.UTF-8 jueves 18 de marzo de 2010 08:16:38 CST es_MX.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST es_NI.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST es_PA.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST es_PE.UTF-8 jueves 18 de marzo de 2010 08H16'39" CST es_PR.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST es_PY.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST es_SV.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST es_US.UTF-8 jueves 18 de marzo de 2010 08:16:39 a.m. CST es_UY.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST es_VE.UTF-8 jueves 18 de marzo de 2010 08:16:39 CST et_EE.UTF-8 neljapäev, 18, märts 2010 08:16:39 CST fi_FI.UTF-8 torstaina 18. maaliskuuta 2010 0
Re: [osol-discuss] Upgrade 133 -> 134, now can't boot anything :-(
On 11/03/2010 12:07, Rob McMahon wrote: Thanks for the suggestions, but I think this is my own fault. I think I've shot myself in the foot by enabling compression on rpool. Replying to myself in case anyone else gets themselves in this position. What worked for me was to burn a new 134 iso and boot from it. zpool import # lists available pools zpool import -f rpool# makes the pool available zfs set compression=off /rpool# undo the over-zealous compression beadm list # See alternative boot environments beadm activate opensolaris-133# Revert to previous environment - I couldn't find a way of fixing 134 directly zpool export rpool init 6 # Reboot into previous version # Once in 133 beadm activate opensolaris-134# Go to new release, new files are written uncompressed, I guess init 6 # Reboot into latest version And I'm back in action. I can't say this is the most efficient way to do it, but it's what worked for me. Rob -- E-Mail: rob.mcma...@warwick.ac.uk PHONE: +44 24 7652 3037 Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] B134 network issue
Hi, On Thu, Mar 18, 2010 at 02:20:17AM -0700, Karel Gardas wrote: > Hello, > so no, the issue is not somewhere else, but it's directly on the solaris and > it happens on both b134 and b111b (OS 2009.06). > The issue is this: OS runs on Lenovo T500 which provides wifi card and > e1000g0 card. When I boot and let OS boot without cable pluged into the > e1000g connector then network (routing!) will not work. I'm able to ping > machines on network (10.0.0.*), but routing will not work. For example ping > complains with `no route to host' message (when I ping something outside). As > I said, this happen on both b111b and b134. Now, I've not found it that > quickly since normally I came to office, put notebook on desk, plug network > cable to the e1000g0 connector and switch on and boot the OS. If I do this, > then network including routing works as expected. > To me this looks like an issue in nwamd or something of that kind. I'm using > defaultrouter configuration i.e. > ka...@thinkpad:~$ cat /etc/defaultrouter > 10.0.0.138 > ka...@thinkpad:~$ > > Now, the question is if this is already reported somewhere or if I shall > report it myself. > Thanks, > Karel > PS: general note: b134 looks really nice, much better than 133/132. Thanks > for this! Try to use old-good physical:default instead of the physical:nwam in case you have static network configuration on your box. /lib/svc/method/net-nwam -u .. then check your static configuration and (fast-)reboot. /j. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] how to get logging happening
On Wed, 17 Mar 2010, Luke Vanderfluit wrote: >Hi. > >I have a solaris 10 box that houses samba shares. The box becomes inaccessible >at unpredictable times. I want to enable logging to see what activity is going >on and log that to /var/adm/messages > >I have edited the syslog.conf file and added the following lines: >user.debug /var/adm/messages >user.info /var/adm/messages >user.crit /var/adm/messages >user.emerg /var/adm/messages >user.err/var/adm/messages >user.alert /var/adm/messages Luke, see syslog.conf(4) - you should use just one line with the highest level you need, it automatically logs all less eloquent levels. also, facility.level *must* be separated from the file via tabelators, not spaces, if that could be an issue there as well. I also suggest to log to a specific file, it will be easier to read then. Do not forget to manually touch the file before restarting the syslogd, it will not be automatically created. J. > >then I restart syslogd. I dont see any messages in /var/adm/messages other >than: >Mar 18 09:32:09 storage.interact syslogd: going down on signal 15 > >I want to see user activity to the samba shares... how do I do that...? > >TIA. > >Kr. >Luke Van > -- Jan Pechanec http://blogs.sun.com/janp ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] When will opensolaris fix the poweroff problem?
Plain-vanilla Dell Precision Workstation T7500; I also installed Osol on my older Precision Workstation 690. Same thing---inevitably sporadic power-off... -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] B134 network issue
Hello, so no, the issue is not somewhere else, but it's directly on the solaris and it happens on both b134 and b111b (OS 2009.06). The issue is this: OS runs on Lenovo T500 which provides wifi card and e1000g0 card. When I boot and let OS boot without cable pluged into the e1000g connector then network (routing!) will not work. I'm able to ping machines on network (10.0.0.*), but routing will not work. For example ping complains with `no route to host' message (when I ping something outside). As I said, this happen on both b111b and b134. Now, I've not found it that quickly since normally I came to office, put notebook on desk, plug network cable to the e1000g0 connector and switch on and boot the OS. If I do this, then network including routing works as expected. To me this looks like an issue in nwamd or something of that kind. I'm using defaultrouter configuration i.e. ka...@thinkpad:~$ cat /etc/defaultrouter 10.0.0.138 ka...@thinkpad:~$ Now, the question is if this is already reported somewhere or if I shall report it myself. Thanks, Karel PS: general note: b134 looks really nice, much better than 133/132. Thanks for this! -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
