[osol-discuss] problems with cifs
Today I tried to setup the cifs server on an b125 indiana for our new active directory (windows 2008) All is working fine (kerberos ldap and so on), just the cifs server seems to not run in ad mode so it tries to treat the ad users as guests. smbadm join -u ... fails, so it looks like I need to configure the smb/server manually, could some one give me an advice what values are needed where (svccfg -s smb/sevrer editprop)? smbadm join -u admin [fqdn] After joining [fqdn] the smb service will be restarted automatically. Would you like to continue? [no]: yes Enter domain password: Joining [fqdn] ... this may take a minute ... failed to find any domain controllers for [fqdn] /export/home/tkadmin/msrpc.d -p `pgrep smbd`dtrace: script '/export/home/tkadmin/msrpc.d' matched 554 probes CPU IDFUNCTION:NAME 1 1 :BEGIN MSRPC Trace Started 1 56214 smb_trace:entry msdcsLookupADS: rhea.[fqdn] [192.168.2.3] 1 56215 ndo_trace:entry LSARPC Local Security Authority 1 56489 smbrdr_open_pipe:entry rhea [fqdn] admin \lsarpc 1 56497 smbrdr_open_pipe:return 4294967295 1 56215 ndo_trace:entry LSARPC Local Security Authority 1 56489 smbrdr_open_pipe:entry rhea [FQDN] ADMIN \lsarpc 1 56497 smbrdr_open_pipe:return 4294967295 dtrace: pid 5194 has exited 1 2 :END MSRPC Trace Ended smime.p7s Description: S/MIME Cryptographic Signature ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Old(ish) Sparc Support
1) Sorry for the multiple posts, I recevied a server error each time. 2) Posting here a private reply, please reply to the forum not by eMail: Sun has never supported any piece of hardware forever - all of them eventually have support dropped. sun4c support was dropped from Solaris 8, sun4d from Solaris 9, sun4m Ultra 1 from Solaris 10, it's just time for the next round in the next Solaris release. This might sound like a provocatory post, but I think that it is necessary to give Sun a wake-up call on this matter. Then you're sending it to the wrong place - a few engineers read opensolaris-help, but I doubt any of the VP's who decide what to fund will ever know you posted, and it's going to be a lot harder sell now. In case you haven't read the press, Sun is losing money, and isn't going to solve that by spending more on supporting hardware that hasn't been sold in year and isn't likely to bring in enough paid support contracts to cover the expense of providing that support What Sun's VPs fail to understand and acknowledge is that most opensource contributors are enthusiastic and with no access to sufficient funds to purchase NEW and SUPPORTED Sun hardware to dedicate to their hobby. They require access to inexpensive hardware, and like it or not this is normally sourced second-hand on eBay. Sun have pursued the right avenue to open their software, but they will be able to expand contribution exponentially only by continuing to support their older and inexpensive hardware. At least they should be doing the right thing to open the source code of every hardware component Sun no longer plan to support commercially, to encourage their continued use and support in the open market. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Old(ish) Sparc Support
Jensen Lee wrote: At least they should be doing the right thing to open the source code of every hardware component Sun no longer plan to support commercially, to encourage their continued use and support in the open market. opening code or hardware documentation is expensive. So that too is a difficult option at best. Cheers, -- Shawn Walker ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 2009.06 won't boot into GUI... video driver issue.
Had the same issue (booted GUI from live CD fine. Didn't from installation) installing as a guest OS in VirtualBox. Ended up being insuffient video RAM. VirtualBox set the VRAM to 12MB. I up'd it to 64MB and booted into GUI with no issues. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Problems with hal service on OpenSolaris 2009.06
Hi all,
tomorrow I have executed dmesg and I see this error:
Oct 29 12:38:26 hobbiton svc.startd[7]: [ID 652011 daemon.warning]
svc:/system/hal:default: Method /lib/svc/method/svc-hal start failed with exit
status 127.
Oct 29 12:38:27 hobbiton last message repeated 2 times
Oct 29 12:38:27 hobbiton svc.startd[7]: [ID 748625 daemon.error] system/hal:default
failed: transitioned to maintenance (see 'svcs -xv' for details)
after that I have executed svcs -xv and I see:
r...@hobbiton:/var/svc/log# svcs -xv
svc:/system/hal:default (Hardware Abstraction Layer daemon)
State: maintenance since Thu Oct 29 12:38:27 2009
Reason: Start method failed repeatedly, last exited with status 127.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/man -s 1M hal
See: /var/svc/log/system-hal:default.log
Impact: 1 dependent service is not running:
svc:/system/filesystem/rmvolmgr:default
But if I try to start rmvolmgr service nothing happens, continues offline:
r...@hobbiton:/var/svc/log# svcadm enable
svc:/system/filesystem/rmvolmgr:default
r...@hobbiton:/var/svc/log# svcs -a |grep rmvol
offline12:38:12 svc:/system/filesystem/rmvolmgr:default
Where is the problem??
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problems with hal service on OpenSolaris 2009.06
carlopmart wrote: Hi all, tomorrow I have executed dmesg and I see this error: Oct 29 12:38:26 hobbiton svc.startd[7]: [ID 652011 daemon.warning] svc:/system/hal:default: Method /lib/svc/method/svc-hal start failed with exit status 127. Oct 29 12:38:27 hobbiton last message repeated 2 times Oct 29 12:38:27 hobbiton svc.startd[7]: [ID 748625 daemon.error] system/hal:default failed: transitioned to maintenance (see 'svcs -xv' for details) after that I have executed svcs -xv and I see: r...@hobbiton:/var/svc/log# svcs -xv svc:/system/hal:default (Hardware Abstraction Layer daemon) State: maintenance since Thu Oct 29 12:38:27 2009 Reason: Start method failed repeatedly, last exited with status 127. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/man -s 1M hal See: /var/svc/log/system-hal:default.log Impact: 1 dependent service is not running: svc:/system/filesystem/rmvolmgr:default But if I try to start rmvolmgr service nothing happens, continues offline: r...@hobbiton:/var/svc/log# svcadm enable svc:/system/filesystem/rmvolmgr:default r...@hobbiton:/var/svc/log# svcs -a |grep rmvol offline12:38:12 svc:/system/filesystem/rmvolmgr:default Where is the problem?? svc:/system/filesystem/rmvolmgr:default is a dependant service of svc:/system/hal:default. This means you need to correct svc:/system/hal:default before svc:/system/filesystem/rmvolmgr:default to get it to run. The first thing to do in trying to fix this is read your log file for hal, located at /var/svc/log/system-hal:default.log. This might supply a clue to whats failing. Paul ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problems with hal service on OpenSolaris 2009.06
Paul Gress wrote:
carlopmart wrote:
Hi all,
tomorrow I have executed dmesg and I see this error:
Oct 29 12:38:26 hobbiton svc.startd[7]: [ID 652011 daemon.warning]
svc:/system/hal:default: Method /lib/svc/method/svc-hal start failed
with exit status 127.
Oct 29 12:38:27 hobbiton last message repeated 2 times
Oct 29 12:38:27 hobbiton svc.startd[7]: [ID 748625 daemon.error]
system/hal:default failed: transitioned to maintenance (see 'svcs -xv'
for details)
after that I have executed svcs -xv and I see:
r...@hobbiton:/var/svc/log# svcs -xv
svc:/system/hal:default (Hardware Abstraction Layer daemon)
State: maintenance since Thu Oct 29 12:38:27 2009
Reason: Start method failed repeatedly, last exited with status 127.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/man -s 1M hal
See: /var/svc/log/system-hal:default.log
Impact: 1 dependent service is not running:
svc:/system/filesystem/rmvolmgr:default
But if I try to start rmvolmgr service nothing happens, continues
offline:
r...@hobbiton:/var/svc/log# svcadm enable
svc:/system/filesystem/rmvolmgr:default
r...@hobbiton:/var/svc/log# svcs -a |grep rmvol
offline12:38:12 svc:/system/filesystem/rmvolmgr:default
Where is the problem??
svc:/system/filesystem/rmvolmgr:default is a dependant service of
svc:/system/hal:default.
This means you need to correct svc:/system/hal:default before
svc:/system/filesystem/rmvolmgr:default to get it to run.
The first thing to do in trying to fix this is read your log file for
hal, located at /var/svc/log/system-hal:default.log. This might supply
a clue to whats failing.
Paul
Thanks Paul, I have solved the problem reinstalling hal package.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 2009.06 won't boot into GUI... video driver issue.
Had the same issue (booted GUI from live CD fine. Didn't from installation) installing as a guest OS in VirtualBox. Ended up being insuffient video RAM. VirtualBox set the VRAM to 12MB. I up'd it to 64MB and booted into GUI with no issues. I suspect this is a virtualbox issue, when 1. the 32-bit solaris kernel is running 2. the virtualbox guest additions are installed 3. cpu hardware virtualization (amd-v, vt-x) is not enabled IIRC, the Xorg segfault is not 100% reproducible; I suspect that your vbox guest will crash Xorg with 64MB video run, too, sooner or later. http://defect.opensolaris.org/bz/show_bug.cgi?id=8993 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 2009.06 won't boot into GUI... video driver issue.
I've installed 2009.06 on a Dell R710 that is going to be running a ZFS based NAS. When installing the OS form the live CD, the GUI loads just fine. After the OS is installed, the screen blinks several times like it's trying to boot into the GUI but eventually gives up and gives me a console log-in screen. According to Dell, the R710 uses a Matrox G200 for video. What is logged to Xorg's log file, /var/log/Xorg.0.log ? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 2009.06 won't boot into GUI... video driver issue.
Greg Heck wrote: Had the same issue (booted GUI from live CD fine. Didn't from installation) installing as a guest OS in VirtualBox. Ended up being insuffient video RAM. VirtualBox set the VRAM to 12MB. I up'd it to 64MB and booted into GUI with no issues. Hi, I've only just joined the list, and I have no reference to the original mail thread as it obviously pre-dates me joining. I'm posting this in case it helps someone, so please forgive me if what I cover has already been said. I recently installed installed my first Opensolaris install (2009.06) and had problems getting a GUI after installation as well. But in my case, this occurred several times due to name resolution not working properly, which I've since resolved. The first thing I did after building the machine, was remove all references to opensolaris in /etc/hosts and creating a new line with the public IP address and the new hostname (in conjunction /etc/nodename and a few others). However at some point in the installation I did all of the following, and each one resulted in the loss of the GUI: 1. Disabled NWAM and did not create a /etc/defaultrouter 2. Copied /etc/nsswitch.dns to /etc/nsswitch.conf, without network access to the only DNS servers listed in /etc/resolv.conf 3. Enabled (802.3ad) LACP link aggregation in active mode, when the corresponding setup on the Cisco ports hadn't yet been configured (thereby dropping the box of the network). So, basically if you don't have working name resolution, you are also going to have this problem. As soon as I rectified these issues, name resolution worked and so did the GUI (after a reboot). Hope that helps whomever originally posted. Regards, -- Stewart Walters IT Systems Manager BGC Australia Pty Ltd Phone: 08 9334 4646 Fax: 08 9334 4660 Mobile: 0429 100 465 Email: s...@bgc.com.au ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Driver trouble on Nevada...
Hi, I have several types of IBM BladeCenter blades (mostly HS20 and LS20.) The BladeCenter manages these blades through a BMC with IPMI, and provides access to the serial console (ttyb) of the blades through the Serial Over LAN (SOL) feature of the BMC. When I user Solaris10 on these blades, Access to the serial console is fine. When I install SXCE (sNVb120 through 125 at least,) the console connection is terminated (not gibberish - The BMC stops sending the SOL data) shortly after the kernel boots, and the management module for the BladeCenter reports that 'SOL is not ready' for the blade I'm using, until I reboot it. I've played a bit with the BMC BIOS Settings, but I don't think that's the problem since this works fine in s10. How can I collect more info, or narrow this problem down further so that I can file a useful bug report? The output from booting SXCE sNV b125, as you can see it disconnects after loading the sysidcfg info, previous builds used to disconnect while 'Configuring /dev' if I recall. SunOS Release 5.11 Version snv_125 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. NOTICE: Invalid iBFT table 0x1 Configuring /dev WARNING: emlxs: ddi_modopen drv/fct failed: err 2 Custom JumpStart Reading ZFS config: done. Setting up Java. Please wait... Serial console, reverting to text install Beginning system identification... Searching for configuration file(s)... Using sysid configuration file 172.30.171.30:/ex/Inst/SysID/Def/sysidcfg Search complete. Discoveri system console -T blade[3] SOL is not ready system The 'system' prompt is the CLI for the mmanagement module. The 'console -T blade[3]' command is me trying to reconnect to the SOL console. Anyone know of any changes in sNV that might have triggered this? It's making all of these blades useless for OpenSolaris. -Kyle ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] firefox does not see printers
I am running build 121 with firefox 3.5.1. Even thought the system can see network printers and can print to them, firefox will not list any printers and will only print to file?? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [driver-discuss] Driver trouble on Nevada...
I tried booting again with -kv : module /platform/i86pc/kernel/amd64/unix: text at [0xfb80, 0xfb938f93] data at 0xfbc0 module /kernel/amd64/genunix: text at [0xfb938fa0, 0xfbb8f897] data at 0xfbc80b40 Loading kmdb... module /kernel/misc/amd64/kmdbmod: text at [0xfbcf0730, 0xfbd939a7] data at 0xfbd939b0 module /kernel/misc/amd64/ctf: text at [0xfbb8f8a0, 0xfbb9a1f7] data at 0xfbdaed10 SunOS Release 5.11 Version snv_125 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. features: 614dcpuid,mwait,cx16,sse3,asysc,htt,sse2,sse,sep,pat,cx8,pae,mca,mmx,cmov,de,pge,mtrr,msr,tsc,lgpg mem = 8387812K (0x1fff39000) Using default device instance data initialized model-specific module 'cpu_ms.GenuineIntel' on chip 0 core 0 strand 0 root nexus = i86pc pseudo0 at root pseudo0 is /pseudo scsi_vhci0 at root scsi_vhci0 is /scsi_vhci npe0 at root: space 0 offset 0 npe0 is /p...@0,0 PCI Express-device: i...@1f, isa0 NOTICE: Invalid iBFT table 0x1 pseudo-device: acpippm0 acpippm0 is /pseudo/acpi...@0 pseudo-device: ppm0 ppm0 is /pseudo/p...@0 ramdisk0 at root ramdisk0 is /ramdisk root on /ramdisk:a fstype ufs SMBIOS v2.3 loaded (2026 bytes)acpinex0 at root acpinex0 is /fw pseudo-device: dld0 dld0 is /pseudo/d...@0 PCI Express-device: pci8086,3...@3, pcieb0 pcieb0 is /p...@0,0/pci8086,3...@3 PCIE-device: pci8086,3...@0,2, pcieb2 pcieb2 is /p...@0,0/pci8086,3...@3/pci8086,3...@0,2 PCIE-device: pci1014,2...@1, bge0 bge0 is /p...@0,0/pci8086,3...@3/pci8086,3...@0,2/pci1014,2...@1 PCIE-device: pci1014,2...@1,1, bge1 bge1 is /p...@0,0/pci8086,3...@3/pci8086,3...@0,2/pci1014,2...@1,1 Ethernet address = 0:14:5e:3d:5a:f3 ISA-device: asy0 asy0 is /p...@0,0/i...@1f/a...@1,3f8 ISA-device: asy1 asy1 is /p...@0,0/i...@1f/a...@1,2f8 PCI Express-device: pci8086,2...@1c, pci_pci0 pci_pci0 is /p...@0,0/pci8086,2...@1c PCI Express-device: pci8086,2...@1e, pci_pci1 pci_pci1 is /p...@0,0/pci8086,2...@1e PCI Express-device: pci1014,2...@1d, uhci0 uhci0 system The one thing I can think of, is that IBM warns on these blades that the network connection for the BMC is shared (hijacked) from bge0, and that if you PXE boot over bge0, the PXE code will reset the bge interface in a way the will disconnect the SOL connection. Given this, I wonder if the disconnection is a (delayed) consequence of the bge0 driver loading shortly before the disconnection? -Kyle Kyle McDonald wrote: Hi, I have several types of IBM BladeCenter blades (mostly HS20 and LS20.) The BladeCenter manages these blades through a BMC with IPMI, and provides access to the serial console (ttyb) of the blades through the Serial Over LAN (SOL) feature of the BMC. When I user Solaris10 on these blades, Access to the serial console is fine. When I install SXCE (sNVb120 through 125 at least,) the console connection is terminated (not gibberish - The BMC stops sending the SOL data) shortly after the kernel boots, and the management module for the BladeCenter reports that 'SOL is not ready' for the blade I'm using, until I reboot it. I've played a bit with the BMC BIOS Settings, but I don't think that's the problem since this works fine in s10. How can I collect more info, or narrow this problem down further so that I can file a useful bug report? The output from booting SXCE sNV b125, as you can see it disconnects after loading the sysidcfg info, previous builds used to disconnect while 'Configuring /dev' if I recall. SunOS Release 5.11 Version snv_125 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. NOTICE: Invalid iBFT table 0x1 Configuring /dev WARNING: emlxs: ddi_modopen drv/fct failed: err 2 Custom JumpStart Reading ZFS config: done. Setting up Java. Please wait... Serial console, reverting to text install Beginning system identification... Searching for configuration file(s)... Using sysid configuration file 172.30.171.30:/ex/Inst/SysID/Def/sysidcfg Search complete. Discoveri system console -T blade[3] SOL is not ready system The 'system' prompt is the CLI for the mmanagement module. The 'console -T blade[3]' command is me trying to reconnect to the SOL console. Anyone know of any changes in sNV that might have triggered this? It's making all of these blades useless for OpenSolaris. -Kyle ___ driver-discuss mailing list driver-disc...@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/driver-discuss ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problems with cifs
Solved, http://mail.opensolaris.org/pipermail/cifs-discuss/2008-October/000893.html Am 29.10.2009 16:35, schrieb Florian Manschwetus: Today I tried to setup the cifs server on an b125 indiana for our new active directory (windows 2008) All is working fine (kerberos ldap and so on), just the cifs server seems to not run in ad mode so it tries to treat the ad users as guests. smbadm join -u ... fails, so it looks like I need to configure the smb/server manually, could some one give me an advice what values are needed where (svccfg -s smb/sevrer editprop)? smbadm join -u admin [fqdn] After joining [fqdn] the smb service will be restarted automatically. Would you like to continue? [no]: yes Enter domain password: Joining [fqdn] ... this may take a minute ... failed to find any domain controllers for [fqdn] /export/home/tkadmin/msrpc.d -p `pgrep smbd`dtrace: script '/export/home/tkadmin/msrpc.d' matched 554 probes CPU IDFUNCTION:NAME 1 1 :BEGIN MSRPC Trace Started 1 56214 smb_trace:entry msdcsLookupADS: rhea.[fqdn] [192.168.2.3] 1 56215 ndo_trace:entry LSARPC Local Security Authority 1 56489 smbrdr_open_pipe:entry rhea [fqdn] admin \lsarpc 1 56497 smbrdr_open_pipe:return 4294967295 1 56215 ndo_trace:entry LSARPC Local Security Authority 1 56489 smbrdr_open_pipe:entry rhea [FQDN] ADMIN \lsarpc 1 56497 smbrdr_open_pipe:return 4294967295 dtrace: pid 5194 has exited 1 2 :END MSRPC Trace Ended ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org smime.p7s Description: S/MIME Cryptographic Signature ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] firefox does not see printers
Mike DeMarco wrote: I am running build 121 with firefox 3.5.1. Even thought the system can see network printers and can print to them, firefox will not list any printers and will only print to file?? I have this problem too, on 2009.06 (svn 111b), using CUPS. If you check evince (PDF reader) it will likely have the same problem. What I have found out is that certain applications combined with GTK have problems with the CUPS dialog box. It's not unique to Opensolaris either, among the other links I found where this happening, on Linux I found this post (http://forums.mozillazine.org/viewtopic.php?f=38t=675475start=0st=0sk=tsd=a). What I haven't found is the reason why this happens and a specific solution. The only solutions I've come across to date were very anecdotal, sometimes included advice such as I rebuilt the machine and now it works or the forum post requesting help was left unanswered. Thunderbird, doesn't seem to have such a problem, funnily enough. The best information I've come across to date is that there might be a missing library that Firefox uses for the CUPS printing dialog box, but Thunderbird doesn't. That might account for why not everyone experiences the problem. If you open a Firefox tab, type in about:config, and filter the results by searching for the word print you'll see references there to first network printer that you would normally expect to see in the CUPS dialog box (in my case, that is a networked printer called act00). So it can see the printer information from CUPS, it just doesn't display a whole list of printers to choose from like it's supposed to. Mind you in my situation, my CUPS server is situated on a Debian Linux box and CUPS on Opensolaris is configured with a /etc/cups/client.conf file pointing to it. While I don't think it has an affect, I haven't ruled it out yet either. Regards, Stewart ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to make syslogger write to a fifo?
Brian Ruthven - Solaris Network Sustaining - Sun UK brian.ruth...@sun.com writes: Hi Harry, I've got nothing canned which I can quickly pass on, however, anything I gather will be from google ;-) The top three hits searching for writing smf manifest look useful: http://www.sun.com/bigadmin/content/selfheal/sdev_intro.jsp http://wikis.sun.com/display/BigAdmin/SMF+Short+Cuts http://blogs.warwick.ac.uk/chrismay/entry/solaris_smf_manifest/ [...] Jesus... after looking at those URL a bit I feel like just start boohooing and go home. This SMF stuff seems horribly complicated to me. They use terms like `JBoss' with no explanation.. And the XML itself just seem vastly overdone for something that should be fairly simple. Hopefully that is enough to get you started. I'd suggest copying the manifest from a simple service such as utmp.xml and customise it to your needs. If your service needs a startup script, then you should include /lib/svc/share/smf_include.sh so you can use the correct exit codes to signal the right things to the framework. I guess it will be a start... but man I don't understand hardly any of it. To attach a script to an existing service and make it restart when that service restarts is not really something that should require yards and yards of code, several documents, and god only knows what else. Its tempting to just write a perl script, that looks for the service to be running, and starts up if it is. Is that a really bad approach for this? `this' in case it has gotten away in the thread is to run a script that reads from a named-pipe.. that the syslogger writes everything to. The purpose of the script is to have finely grained control over writing various things to logs... using regular expressions. And after starting on the script, I realized I might want to change the regular expressions as the script runs. So far, I've figured out a way to do that I think, by making the script read a secondary file every five minutes. I might write a regular expression and matching log file in the secondary file and the script as it runs will start looking for those. And writing hits to the new log. So far I plan just to use matching pairs in the secondary file like this. REGEX LOG.log What I haven't really got into yet is the best way to have this script running in the background... checking for syslog to be running. That is, the script would never stop running even if the syslogger shut down. Maybe even some kind of `trap' in the script where it would send me a message in the event it was killed. (At least for some kinds of KILL) That's where it starts to look like it might be better to insinuate this script in there through SMF. I'd really like to see a simplified example of how that might be done. Maybe there is an example like that in the URLS you posted. I haven't gotten very far looking into them. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [driver-discuss] Driver trouble on Nevada...
Kyle McDonald wrote: The one thing I can think of, is that IBM warns on these blades that the network connection for the BMC is shared (hijacked) from bge0, and that if you PXE boot over bge0, the PXE code will reset the bge interface in a way the will disconnect the SOL connection. Given this, I wonder if the disconnection is a (delayed) consequence of the bge0 driver loading shortly before the disconnection? -Kyle Just on that note, and I know this is going to sound like a typical IBM response, but have you taken the Bladecenter chassis BIOS, BMC and RSAII firmware revisions all to the latest level? For that matter, have you also taken the Blade BIOS and BMC firmware to the latest revision? I roll my eyes every time I get that response from IBM. But with the IBM Bladecenters - I just go straight to the latest firmware before I even call them now. Applying the latest firmware revisions often do fix up the quirky problems you can receive on BIOS's, BMC's and RSAII Adaptors. Regards, Stewart ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] adp driver the extra repository
Can we expect the adp driver (present in SXCE build 125) to be included into the OpenSolaris extra repository at some point in the future? That driver supports a bunch of old Adaptec HBAs--the AHA 2940 (aka AIC7861) being one of them--and seems to be distributable only under binary form, which is why it was never integrated into OpenSolaris. Still, it would be really nice to have, especially for people using old hardware. As an aside, Linux does provide source code for a similar driver. I myself would be greatly satisfied with a binary only driver. To get my 2940 to work under nv_b125, I had to download the full DVD image of the latest SXCE (3.7GB) and install the adp driver from there. Kind of overkill, I'd say... -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [driver-discuss] Driver trouble on Nevada...
Stewart Walters wrote: Kyle McDonald wrote: The one thing I can think of, is that IBM warns on these blades that the network connection for the BMC is shared (hijacked) from bge0, and that if you PXE boot over bge0, the PXE code will reset the bge interface in a way the will disconnect the SOL connection. Given this, I wonder if the disconnection is a (delayed) consequence of the bge0 driver loading shortly before the disconnection? -Kyle Just on that note, and I know this is going to sound like a typical IBM response, but have you taken the Bladecenter chassis BIOS, BMC and RSAII firmware revisions all to the latest level? For that matter, have you also taken the Blade BIOS and BMC firmware to the latest revision? I roll my eyes every time I get that response from IBM. I know. It's like Windows service people asking you if you've rebooted yet. But with the IBM Bladecenters - I just go straight to the latest firmware before I even call them now. Applying the latest firmware revisions often do fix up the quirky problems you can receive on BIOS's, BMC's and RSAII Adaptors. When I ran in to this problem the first time (about a year ago) I did have them up to date. I'll have to go check the current versions and download any I don't have, but since S10 is working fine, I didn't think of it. -Kyle Regards, Stewart ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Old(ish) Sparc Support
On Thu, Oct 29, 2009 at 12:16 PM, Shawn Walker swal...@opensolaris.org wrote: Jensen Lee wrote: At least they should be doing the right thing to open the source code of every hardware component Sun no longer plan to support commercially, to encourage their continued use and support in the open market. opening code or hardware documentation is expensive. So that too is a difficult option at best. Only if the release of said documentation is an afterthought, not a part of the documentation process. Besides, there's already the documentation project that Sun has. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
