Bandwidth manager with Solaris

Hi all !
Is there a tool for bandwidth manager like pf-altq in BSDs or other in Linux ?
Thanks in advance.
roberto

Download and install:
ntop:
http://www.ntop.org/
iftop:
http://www.ex-parrot.com/~pdw/iftop/
Gary

Similar Messages

  • Bandwidth manager with Solaris 10

    Hi all
    I newbie with solaris and would like to test the IPQoS feature to use for bandwidth limit in a isp.
    I just readed the oficial IPQoS Sun tutorial but I looking for simples examples to limit the bandwidth per ip (clients).
    Someone knows where can find more examples.
    Thanks in advance.
    roberto

    Did you checked this one out already?
    http://docs.sun.com/app/docs/doc/816-4554/6maoq028g?a=view
    //M.

  • Experience with Solaris 10 Memory Management

    Dear Forum!
    Using Note 724713 we installed a couple of R3 Systems on Solaris 10. Independently which R3 Version is used we observe much more memory problems as with prior solaris releases or other operating systems like AIX.
    For instance1: We moved three R3 Systems from a server with solaris 8 to a server with solaris 10. We didnt change memory parameters of R3 and the databases (oracle). The solaris 10 server has the same amount of memory (8GB) like the solaris 8 server. Now, on the solaris 10 server we can only start two R3 systems, the third one doesnt start because no memory can be allocated. The memory parameter of all component slightly overload the main memory. Because the systems are not productive they mostly idle and performance loss due to paging and even swapping didnt worry us. Not even that the third system didnt start, the whole OS was a kind of freezed and no more work was possible, also not on the other two R3 systems which were already startet.
    For instance2:
    On another server with 16GB memory we startet an installation of a sapsystem and the sapinst crashed due to memory absence. Admittedly, here the main memory was also a bit overloaded, but this is not unusal here and I never saw sapinst crashing because of this.
    In both cases Swapspace was adequate.
    Do you have similar  experiences? Or any tipps to solve the problem.
    Thanks
    Andreas

    this is strange. Although /etc/user_attr shows
    /etc/user_attr shows
    adm::::profiles=Log Management
    lp::::profiles=Printer Management
    postgres::::type=role;profiles=Postgres Administration,All
    root::::auths=solaris.*,solaris.grant;profiles=Web Console Management,All;lock_after_retries=no;min_label=admin_low;cle
    arance=admin_high
    qp7adm::::project=QP7
    oraqp7::::project=QP7
    sapadm::::project=QP7
    smdadm::::project=QP7
    the process list show that the processes of the user sidadm run in project "system" only the oracle user project is ok:
    root@pi7q #  ps -eo user,pid,ppid,project,args
        USER   PID  PPID  PROJECT COMMAND
      oraqp7  1783  3652      QP7 ora_q001_QP7
      oraqp7   125  3652      QP7 ora_mmon_QP7
      qp7adm  1884  1862   system dw.sapQP7_DVEBMGS00 pf=/usr/sap/QP7/SYS/profile/QP7_DVEBMGS00_pi7q
      oraqp7 20464  3652      QP7 oracleQP7 (LOCAL=NO)
      daemon  4416  3652   system /usr/lib/nfs/nfs4cbd
      qp7adm  1870  1862   system icman -attach pf=/usr/sap/QP7/SYS/profile/QP7_DVEBMGS00_pi7q
      oraqp7 20462  3652      QP7 oracleQP7 (LOCAL=NO)
        root 14658 25510 user.root bash
      oraqp7   105  3652      QP7 ora_dbw1_QP7
      oraqp7  2980  3652      QP7 oracleQP7 (LOCAL=NO)
        root  5819  3652   system ./tGAgent.d -d
      oraqp7  2544  3652      QP7 oracleQP7 (LOCAL=NO)
      smdadm  5639  3652   system /usr/sap/SMD/SMDA02/exe/sapstartsrv pf=/usr/sap/SMD/SYS/profile/SMD_SMDA02_pi7q
      qp7adm  1900  1862   system dw.sapQP7_DVEBMGS00 pf=/usr/sap/QP7/SYS/profile/QP7_DVEBMGS00_pi7q
        root  4443  3668   system /usr/lib/saf/sac -t 300

  • Monitoring services in zones with Solaris container Manager

    I need to know how to Manage Solaris services (SMF) in sparse zone with Solaris container manager.
    I have navigated all the documentation and I have not found any clue.
    I installed the Sun management center (SMC) server on a server box and the agents on others. I can manage the SMF of the global zone by drilling down via the console GUI. But having access to the container manager, I have to go via https connection. And drilling down on the zone did not reveal that SMF can be monitored.
    Please if you have any idea, share it with me.

    Hi,
    check these:
    - Version of webserver latest is 3.1
    # smcwebserver -V
    - check webconsole is started and running
    # smcwebserver status
    Sun Java(TM) Web Console is running
    # svcs webconsole
    STATE STIME FMRI
    online 19:38:06 svc:/system/webconsole:console
    # svcs -pl webconsole
    fmri svc:/system/webconsole:console
    name java web console
    enabled true
    state online
    next_state none
    state_time Wed Feb 10 19:38:06 2010
    logfile /var/svc/log/system-webconsole:console.log
    restarter svc:/system/svc/restarter:default
    contract_id 64
    dependency require_all/none svc:/milestone/network (online)
    dependency require_all/refresh svc:/milestone/name-services (online)
    dependency require_all/none svc:/system/filesystem/local (online)
    dependency optional_all/none svc:/system/filesystem/autofs (online) svc:/network/nfs/client (online)
    dependency require_all/none svc:/system/system-log (online)
    process 843 /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4
    - check port 6789 is listen mode
    # netstat -an | grep 6789
    *.6789 *.* 0 0 49152 0 LISTEN
    if the output show
    localhost .6789 *.* 0 0 49152 0 LISTEN
    than do these:
    - check that the tcp_listen of webconsole service is true, default is false
    # svccfg -s webconsole listprop options/tcp_listen
    options/tcp_listen boolean false
    # svcadm disable svc:/system/webconsole:console
    # svccfg -s webconsole setprop options/tcp_listen=true
    # svccfg -s webconsole listprop options/tcp_listen
    options/tcp_listen boolean true
    # svcadm enable svc:/system/webconsole:console
    Regards

  • Solaris Bandwidth Manager

    Hi every one.
    I just Installed the Solaris OS 5.10 10/08 on a new Dell Vostro 200. I downloaded the Solaris Bandwidth Manager Documentations but can't find the software itself in solaris.
    Does the software come bundled in solaris 10 or does one get it separate?

    I have moved this question to the Network Configuration Forum here [http://forums.sun.com/thread.jspa?threadID=5354258|http://forums.sun.com/thread.jspa?threadID=5354258]. Please follow the link.
    Sorry for any inconveniences.
    Regards
    Nyantos.

  • Solaris 8 client setup with solaris 9 ldap

    I have managed to install iplanet directory server 5.1 that comes with solaris 9 using the utility idsconfig. As far as i can tell, all went well. Now i'm trying to initialize a solaris 8 client to authenticate to the iDS 5.1 on my solaris 9 box. What do i have to do on the solaris 8 client to "initialize it"? I've tried using ldapclient on the solaris 8 client as follows:
    # ldapclient -v -P default x.x.x.x
    but i keep getting the following errors:
    findDN rename(/var/ldap/ldap_client_file.orig, /var/ldap/ldap_client_file) failed!
    findDN rename(/var/ldap/ldap_client_cred.orig, /var/ldap/ldap_client_cred) failed!
    There are no files in /var/ldap. I thought that one uses ldapclient to create them. Am i wrong?
    Also, the output from idsconfig says that a 'NisDomainObject' was added to my domain but looking at the object classes in iDS5.1, there is no nisdomainobject.
    I also noticed that when i run the command domain on my solaris 8 box, there's no output. Do i need to set the domain on my solaris 8 client? I have the domain defined in /etc/resolv.conf.
    Stewart

    hi Stewart,
    You may find what you are looking for in the following technical note: http://knowledgebase.iplanet.com/ikb/kb/articles/7966.html
    It is called: "Cookbook for Solaris 8 client with Directory Server 5.1/Solaris 9" :-)
    Hope this will help you.
    Cheers / Damien.

  • Ports management in Solaris 10 Zones

    Hi,
    I am new in this area. We have a software vendor who stated that their applications should be able to:
    - open TCP connections to ports in the ranges 21400-21404 and 50000-50199 on the server
    - telnet port 23 for Galaxy 2000, http port 80 for Viewpoint (Server); etc.
    - IngresNet is on listen address I3 (port 21400).
    We have a Server & Storage infrastructure policy of implementing all Unix based applications on Solaris 10 Zones clustered on two nodes.
    Will there be a problem with the vendor requests?. To me, it is about independent port management within Solaris 10 zones
    Thanks in advance.

    Does this imply there are no ports which are common/shared between the Global and local zones.
    If there are, does it mean that opening one in that group of ports in the local zone will automatically implied its equivalent in the global is also opened?

  • [SOLVED] SGA_MAX_SIZE pre-allocated with Solaris 10?

    Hi all,
    I'm about to build a new production database to migrate an existing 8.1.7 database to 10.2.0.3. I'm in the enviable position of having a good chunk of memory to play with on the new system (compared with the existing one) so was looking at a suitable size for the SGA... when something pinged in my memory about SGA_MAX_SIZE and memory allocation in the OS where some platforms will allocate the entire amount of SGA_MAX_SIZE rather than just SGA_TARGET.
    So I did a little test. Using Solaris 10 and Oracle 10.2.0.3 I've created a basic database with SGA_MAX_SIZE set to 400MB and SGA_TARGET 280MB
    $ sqlplus
    SQL*Plus: Release 10.2.0.3.0 - Production on Wed Jan 30 18:31:21 2008
    Copyright (c) 1982, 2006, Oracle.  All Rights Reserved.
    Enter user-name: / as sysdba
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    SQL> show parameter sga
    NAME                                 TYPE        VALUE
    lock_sga                             boolean     FALSE
    pre_page_sga                         boolean     FALSE
    sga_max_size                         big integer 400M
    sga_target                           big integer 280MSo I was expecting to see the OS pre-allocate 280MB of memory but when I checked the segment is actually the 400MB (i.e. SGA_MAX_SIZE) (my database owner is 'ora10g'):
    $ ipcs -a
    IPC status from <running system> as of Wed Jan 30 18:31:36 GMT 2008
    T         ID      KEY        MODE        OWNER    GROUP  CREATOR  
    CGROUP CBYTES  QNUM QBYTES LSPID LRPID   STIME    RTIME    CTIME
    Message Queues:
    T         ID      KEY        MODE        OWNER    GROUP  CREATOR  
    CGROUP NATTCH      SEGSZ  CPID  LPID   ATIME    DTIME    CTIME
    Shared Memory:
    m         22   0x2394e4   rw-r---   ora10g   10gdba   ora10g  
    10gdba     20  419438592  2386  2542 18:31:22 18:31:28 18:28:18
    T         ID      KEY        MODE        OWNER    GROUP  CREATOR  
    CGROUP NSEMS   OTIME    CTIME
    Semaphores:
    s         23   0x89a070e8 ra-r---   ora10g   10gdba   ora10g  
    10gdba   154 18:31:31 18:28:18
    $ I wasn't sure whether Solaris 10 was one of the OSs with truly dynamic memory for the SGA but had hoped it was... this seems to say different. Really I'm just after some confirmation that I'm reading this correctly.
    Thanks.
    Joseph
    Message was edited by:
    Joseph Crofts
    Edited for clarity

    I don't want to get bogged down in too many details, as the links provided in previous posts have many details of SGA tests and the results of what happened. I just want to add a bit of explanation about the Oracle SGA and shared memory on UNIX and Solaris in particular.
    As you know Oracle's SGA is generally a single segment of shared memory. Historically this was 'normal' memory and could be paged out to the swap device. So a 500 MB SGA on a 1 GB physical memory system, would allocate 500 MB from the swap device for paging purposes, but might not use 500 MB of physical memory i.e. free memory might not decrease by 500 MB. How much physical memory depended on what pages in the SGA were accessed, and how frequently.
    At some point some people realised that this paging of the SGA was actually slowing performance of Oracle, as now some 'memory' accesses by Oracle could actually cause 'disk' accesses by paging in saved pages from the swap device. So some operating systems introduced a 'lock' option when creating a shared memory segment (shmat system call if memory serves me). And this was often enabled by a corresponding Oracle initialisation parameter, such as lock_sga.
    Now a 'locked' SGA did use up the full physical memory, and was guaranteed not to be paged out to disk. So Oracle SGA access was now always at memory speed, and consistent.
    Some operating systems took advantage of this 'lock' flag to shared memory segment creation to implement some other performance optimisations. One is not to allocate paging storage from swap space anyway, as it cannot be used by this shared memory segment. Another is to share the secondary page tables within the virtual memory sub-system for this segment over all processes attached to it i.e. one shared page table for the segment, not one page table per process. This can lead to massive memory savings on large SGAs with many attached shadow server processes. Another optimisation on this non-paged, contiguous memory segment is to use large memory pages instead of standard small ones. On Solaris instead of one page entry covering 8 KB of physical memory, it covers 8 MB of physical memory. This reduces the size of the virtual memory page table by a factor of 1,000 - another major memory saving.
    These were some of the optimisations that the original Red Hat Enterprise Linux had to introduce, to play catch up with Solaris, and to not waste memory on large page tables.
    Due to these extra optimisations, Solaris chose to call this 'locking' of shared memory segments 'initimate shared memory' or ISM for short. And I think there was a corresponding Oracle parameter 'use_ism'. This is now the default setting in Oracle ports to Solaris.
    As a result, this is why when Oracle grabs its shared memory segment up front (SGA_MAX_SIZE), it results in that amount of real physical memory being allocated and used.
    With Oracle 9i and 10g when Oracle introduced the SGA_TARGET and other settings and could dynamically resize the SGA, this messed things up for Solaris. Because the shared memory segment was 'Intimate' by default, and was not backed up by paging space on the swap device, it could never shrink in size, or release memory as it could not be paged out.
    Eventually Sun wrote a work around for this problem, and called it Dynamic Intimate Shared Memory (DISM). This is not on by default in Oracle, hence you are seeing all your shared memory segments using the same amount of physical memory. DISM allows the 'lock' flag to be turned on and off on a shared memory segment, and to be done over various memory sizes.
    I am not sure of the details, and so am beginning to get vague here. But I remember that this was a workaround on Sun's part to still get the benefits of ISM and the memory savings from large virtual memory pages and shared secondary page tables, while allowing Oracle to manage the SGA size dynamically and be able to release memory back for use by other things. I'm not sure if DISM allows Oracle to mark memory areas as pageable or locked, or whether it allows Oracle to really grow and shrink the size of a single shared memory segment. I presumed it added yet more flags to the various shared memory system calls.
    Although DISM should work on normal, single Solaris systems, as you know it is not enabled by default, and requires a special initialisation parameter. Also be aware that there are issues with DISM on high end Solaris systems that support Domains (F15K, F25K, etc.) and in Solaris Zones or Containers. Domains have problems when you want to dynamically remove a CPU/Memory board from the system, and the allocations of memory on that board must be reallocated to other memory boards. This can break the rule that a locked shared memory segment must occupy contiguous physical memory. It took Sun another couple of releases of Solaris (or patches or quarterly releases) before they got DISM to work properly in a system with domains.
    I hope I am not trying to teach my granny to suck eggs, if you know what I mean. I just thought I'd provide a bit more background details.
    John

  • Sun update manager with patch manager

    I need to use both products since I have systems running Solaris 10, 9 and 8. Is there a way to get them to work together?
    Ideally, I would like to have 1 system talk to SUN to manage the application and downloads. I would want the system to distribute the patches to all the other systems.

    Yes, this is possible. We would recommend setting up Sun Update Manager on Solaris 10 as your patch proxy (with a connection to Sun). Both Update Manager on Solaris 10 and Patch Manager on Solaris 8 and 9 can then be configured as clients.

  • Problems with Solaris 11 11/11

    Hi,
    I need your help because I have problems with Solaris 11 11/11 installed in a Dell Latitude E4310.
    Here, there are the problems:
    1- No it power off with shutdown or init 5 or init 0 only work well the reboot.
    2- It can not connect to the wifi with wpa, no receive ip by dhcp, the driver of the card is "iwp"
    Thanks.
    Jorge
    Edited by: jdangelo on Nov 16, 2011 1:49 PM
    Edited by: jdangelo on Nov 17, 2011 2:51 PM

    Here is the info of my laptop;
    Manufacture name:Dell Inc.
    Manufacture model:Latitude E4310
    64 Bit:True
    OS version:SunOS solaris 5.11 11.0 i86pc i386 i86pc
    CPU Type:Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
    CPU Number:1
    Number Of Cores Per Processor:2
    Number Of Threads Per Processor:4
    Bios/Firmware Maker:Dell Inc. Version:A05 Release Date:11/20/2010
    prtconf -pv:
    System Configuration: Oracle Corporation i86pc
    Memory size: 3958 Megabytes
    System Peripherals (PROM Nodes):
    Node 0x000001
    bios-boot-device: '80'
    stdout: 00000000
    name: 'i86pc'
    Node 0x000002
    existing: 00c21000.00000000.02bc6001.00000000
    name: 'ramdisk'
    Node 0x000003
    acpi-namespace: '\_SB_.PCI0'
    compatible: 'pciex_root_complex'
    device_type: 'pciex'
    reg: 00000000.00000000.00000000.00000000.00000000
    #size-cells: 00000002
    #address-cells: 00000003
    name: 'pci'
    Node 0x000004
    reg: 00000000.00000000.00000000.00000000.00000000
    compatible: 'pci8086,44.1028.410.2' + 'pci8086,44.1028.410' + 'pci1028,410' + 'pci8086,44.2' + 'pci8086,44' + 'pciclass,060000' + 'pciclass,0600'
    model: 'Host bridge'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000000
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '0'
    class-code: 00060000
    revision-id: 00000002
    vendor-id: 00008086
    device-id: 00000044
    name: 'pci1028,410'
    Node 0x000005
    acpi-namespace: '\_SB_.PCI0.VID_'
    assigned-addresses: 83001010.00000000.f0000000.00000000.00400000.c3001018.00000000.e0000000.00000000.10000000.81001020.00000000.000060b0.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
    reg: 00001000.00000000.00000000.00000000.00000000.03001010.00000000.00000000.00000000.00400000.43001018.00000000.00000000.00000000.10000000.01001020.00000000.00000000.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
    compatible: 'pci8086,46.1028.410.2' + 'pci8086,46.1028.410' + 'pci1028,410' + 'pci8086,46.2' + 'pci8086,46' + 'pciclass,030000' + 'pciclass,0300'
    model: 'VGA compatible controller'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000000
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    device_type: 'display'
    unit-address: '2'
    class-code: 00030000
    revision-id: 00000002
    vendor-id: 00008086
    device-id: 00000046
    name: 'display'
    Node 0x000006
    acpi-namespace: '\_SB_.PCI0.GLAN'
    assigned-addresses: 8200c810.00000000.f5400000.00000000.00020000.8200c814.00000000.f5480000.00000000.00001000.8100c818.00000000.00006040.00000000.00000020
    reg: 0000c800.00000000.00000000.00000000.00000000.0200c810.00000000.00000000.00000000.00020000.0200c814.00000000.00000000.00000000.00001000.0100c818.00000000.00000000.00000000.00000020
    compatible: 'pci8086,10ea.1028.410.5' + 'pci8086,10ea.1028.410' + 'pci1028,410' + 'pci8086,10ea.5' + 'pci8086,10ea' + 'pciclass,020000' + 'pciclass,0200'
    model: 'Ethernet controller'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '19'
    class-code: 00020000
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 000010ea
    name: 'pci1028,410'
    Node 0x000007
    acpi-namespace: '\_SB_.PCI0.EHC2'
    assigned-addresses: 8200d010.00000000.f5470000.00000000.00000400
    reg: 0000d000.00000000.00000000.00000000.00000000.0200d010.00000000.00000000.00000000.00000400
    compatible: 'pci8086,3b3c.1028.410.5' + 'pci8086,3b3c.1028.410' + 'pci1028,410' + 'pci8086,3b3c.5' + 'pci8086,3b3c' + 'pciclass,0c0320' + 'pciclass,0c03'
    model: 'Universal Serial Bus EHCI compliant'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1a'
    class-code: 000c0320
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b3c
    name: 'pci1028,410'
    Node 0x000008
    acpi-namespace: '\_SB_.PCI0.HDEF'
    assigned-addresses: 8300d810.00000000.f5460000.00000000.00004000
    reg: 0000d800.00000000.00000000.00000000.00000000.0300d810.00000000.00000000.00000000.00004000
    compatible: 'pciex8086,3b57.1028.410.5' + 'pciex8086,3b57.1028.410' + 'pciex8086,3b57.5' + 'pciex8086,3b57' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci8086,3b57.1028.410.5' + 'pci8086,3b57.1028.410' + 'pci1028,410' + 'pci8086,3b57.5' + 'pci8086,3b57' + 'pciclass,040300' + 'pciclass,0403'
    model: 'Mixed Mode device'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1b'
    class-code: 00040300
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b57
    name: 'pci1028,410'
    Node 0x000009
    acpi-namespace: '\_SB_.PCI0.RP01'
    slot-names: 00000001.746f6c53.00003333
    reg: 0000e000.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b42.5' + 'pciex8086,3b42' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b42.5' + 'pci8086,3b42' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00005000.81000000.00000000.00005000.00000000.00001000.82000000.00000000.f4000000.82000000.00000000.f4000000.00000000.01400000
    bus-range: 00000001.00000001
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000000
    devsel-speed: 00000000
    interrupts: 00000001
    unit-address: '1c'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b42
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b42'
    Node 0x00000a
    acpi-namespace: '\_SB_.PCI0.RP02'
    slot-names: 00000001.746f6c53.00003433
    reg: 0000e100.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b44.5' + 'pciex8086,3b44' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b44.5' + 'pci8086,3b44' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00004000.81000000.00000000.00004000.00000000.00001000.82000000.00000000.f2c00000.82000000.00000000.f2c00000.00000000.01400000
    bus-range: 00000002.00000002
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000001
    devsel-speed: 00000000
    interrupts: 00000002
    unit-address: '1c,1'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b44
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b44'
    Node 0x000013
    acpi-namespace: '\_SB_.PCI0.RP02.PXSX'
    assigned-addresses: 83020010.00000000.f2c00000.00000000.00002000
    reg: 00020000.00000000.00000000.00000000.00000000.03020010.00000000.00000000.00000000.00002000
    compatible: 'pciex8086,422c.8086.1321.35' + 'pciex8086,422c.8086.1321' + 'pciex8086,422c.35' + 'pciex8086,422c' + 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,422c.8086.1321.35' + 'pci8086,422c.8086.1321' + 'pci8086,1321' + 'pci8086,422c.35' + 'pci8086,422c' + 'pciclass,028000' + 'pciclass,0280'
    model: 'Network controller'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    subsystem-vendor-id: 00008086
    subsystem-id: 00001321
    unit-address: '0'
    class-code: 00028000
    revision-id: 00000035
    vendor-id: 00008086
    device-id: 0000422c
    name: 'pci8086,1321'
    Node 0x00000b
    acpi-namespace: '\_SB_.PCI0.RP03'
    slot-names: 00000001.746f6c53.00000038
    reg: 0000e200.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b46.5' + 'pciex8086,3b46' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b46.5' + 'pci8086,3b46' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00003000.81000000.00000000.00003000.00000000.00001000.82000000.00000000.f1800000.82000000.00000000.f1800000.00000000.01400000
    bus-range: 00000003.00000003
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000002
    devsel-speed: 00000000
    interrupts: 00000003
    unit-address: '1c,2'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b46
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b46'
    Node 0x000014
    acpi-namespace: '\_SB_.PCI0.RP03.PXSX'
    assigned-addresses: 82030010.00000000.f1830000.00000000.00000100
    reg: 00030000.00000000.00000000.00000000.00000000.02030010.00000000.00000000.00000000.00000100
    compatible: 'pciex1180,e822.1028.410.1' + 'pciex1180,e822.1028.410' + 'pciex1180,e822.1' + 'pciex1180,e822' + 'pciexclass,080500' + 'pciexclass,0805' + 'pci1180,e822.1028.410.1' + 'pci1180,e822.1028.410' + 'pci1028,410' + 'pci1180,e822.1' + 'pci1180,e822' + 'pciclass,080500' + 'pciclass,0805'
    model: 'SD Host controller'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '0'
    class-code: 00080500
    revision-id: 00000001
    vendor-id: 00001180
    device-id: 0000e822
    name: 'pci1028,410'
    Node 0x00000c
    acpi-namespace: '\_SB_.PCI0.RP04'
    slot-names: 00000001.746f6c53.00000039
    reg: 0000e300.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b48.5' + 'pciex8086,3b48' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b48.5' + 'pci8086,3b48' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00002000.81000000.00000000.00002000.00000000.00001000.82000000.00000000.f0400000.82000000.00000000.f0400000.00000000.01400000
    bus-range: 00000004.00000009
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000003
    devsel-speed: 00000000
    interrupts: 00000004
    unit-address: '1c,3'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b48
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b48'
    Node 0x00000d
    acpi-namespace: '\_SB_.PCI0.EHCI'
    assigned-addresses: 8200e810.00000000.f5450000.00000000.00000400
    reg: 0000e800.00000000.00000000.00000000.00000000.0200e810.00000000.00000000.00000000.00000400
    compatible: 'pci8086,3b34.1028.410.5' + 'pci8086,3b34.1028.410' + 'pci1028,410' + 'pci8086,3b34.5' + 'pci8086,3b34' + 'pciclass,0c0320' + 'pciclass,0c03'
    model: 'Universal Serial Bus EHCI compliant'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1d'
    class-code: 000c0320
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b34
    name: 'pci1028,410'
    Node 0x00000e
    acpi-namespace: '\_SB_.PCI0.P0P1'
    slot-names: 0000002f.746f6c53.6c530031.0032746f.746f6c53.6c530033.0034746f.746f6c53.00000032
    reg: 0000f000.00000000.00000000.00000000.00000000
    compatible: 'pci8086,2448.a5' + 'pci8086,2448' + 'pciclass,060401' + 'pciclass,0604'
    model: 'Subtractive Decode PCI-PCI bridge'
    bus-range: 0000000a.0000000a
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pci'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    unit-address: '1e'
    class-code: 00060401
    revision-id: 000000a5
    vendor-id: 00008086
    device-id: 00002448
    name: 'pci8086,2448'
    Node 0x00000f
    #size-cells: 00000001
    #address-cells: 00000002
    ranges: 00000001.00000000.81000000.00000000.00000000.00000022.00000001.00000024.81000000.00000000.00000024.00000002.00000001.00000028.81000000.00000000.00000028.00000002.00000001.0000002c.81000000.00000000.0000002c.00000006.00000001.00000034.81000000.00000000.00000034.00000002.00000001.00000038.81000000.00000000.00000038.00000002.00000001.0000003c.81000000.00000000.0000003c.00000002.00000001.00000040.81000000.00000000.00000040.00000004.00000001.0000004e.81000000.00000000.0000004e.00000006.00000001.00000060.81000000.00000000.00000060.00000002.00000001.00000063.81000000.00000000.00000063.00000003.00000001.00000067.81000000.00000000.00000067.00000001.00000001.00000070.81000000.00000000.00000070.00000008.00000001.00000070.81000000.00000000.00000070.00000001.00000001.00000080.81000000.00000000.00000080.00000022.00000001.000000a4.81000000.00000000.000000a4.00000002.00000001.000000a8.81000000.00000000.000000a8.00000002.00000001.000000ac.81000000.00000000.000000ac.00000002.00000001.000000b0.81000000.00000000.000000b0.00000006.00000001.000000b8.81000000.00000000.000000b8.00000002.00000001.000000bc.81000000.00000000.000000bc.00000002.00000001.000000c0.81000000.00000000.000000c0.00000020.00000001.000000f0.81000000.00000000.000000f0.00000001.00000001.00000400.81000000.00000000.00000400.00000080.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000500.81000000.00000000.00000500.00000080.00000001.00000680.81000000.00000000.00000680.00000020.00000001.00000930.81000000.00000000.00000930.00000001.00000001.00000934.81000000.00000000.00000934.00000001.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00001000.81000000.00000000.00001000.00000014.00000001.0000164e.81000000.00000000.0000164e.00000002.00000001.0000ffff.81000000.00000000.0000ffff.00000001.00000000.f54c0000.82000000.00000000.f54c0000.00001000.00000000.f8000000.82000000.00000000.f8000000.04000000.00000000.fed00000.82000000.00000000.fed00000.00000400.00000000.fed10000.82000000.00000000.fed10000.00004000.00000000.fed18000.82000000.00000000.fed18000.00002000.00000000.fed1c000.82000000.00000000.fed1c000.00024000.00000000.fed45000.82000000.00000000.fed45000.0004b000.00000000.fee00000.82000000.00000000.fee00000.00100000.00000000.ff000000.82000000.00000000.ff000000.01000000.00000000.ff000000.82000000.00000000.ff000000.01000000
    acpi-namespace: '\_SB_.PCI0.LPCB'
    device_type: 'isa'
    reg: 0000f800.00000000.00000000.00000000.00000000
    compatible: 'pci8086,3b0f.1028.410.5' + 'pci8086,3b0f.1028.410' + 'pci1028,410' + 'pci8086,3b0f.5' + 'pci8086,3b0f' + 'pciclass,060100' + 'pciclass,0601'
    model: 'ISA bridge'
    power-consumption: 00000001.00000001
    devsel-speed: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f'
    class-code: 00060100
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b0f
    name: 'isa'
    Node 0x00001c
    unit-address: '1,60'
    interrupts: 00000001.0000000c
    reg: 00000001.00000060.00000001.00000001.00000064.00000001
    name: 'i8042'
    Node 0x00001d
    compatible: 'pnpPNP,303'
    device-type: 'keyboard'
    interrupts: 00000001.0000000c
    reg: 00000000
    acpi-namespace: '\_SB_.PCI0.LPCB.PS2K'
    model: 'System keyboard'
    name: 'keyboard'
    Node 0x00001e
    compatible: 'pnpPNP,f03'
    device-type: 'mouse'
    reg: 00000001
    interrupts: 0000000c
    acpi-namespace: '\_SB_.PCI0.LPCB.PS2M'
    model: 'PS/2 Port for PS/2-style Mice'
    name: 'mouse'
    Node 0x00001f
    interrupts: 00000004
    reg: 00000001.000003f8.00000008
    model: 'Standard serial port'
    compatible: 'PNP0500'
    name: 'asy'
    Node 0x000010
    acpi-namespace: '\_SB_.PCI0.SAT0'
    assigned-addresses: 8100fa10.00000000.00006090.00000000.00000008.8100fa14.00000000.00006080.00000000.00000004.8100fa18.00000000.00006070.00000000.00000008.8100fa1c.00000000.00006060.00000000.00000004.8100fa20.00000000.00006020.00000000.00000020.8200fa24.00000000.f5440000.00000000.00000800
    reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800
    compatible: 'pci8086,3b2f.1028.410.5' + 'pci8086,3b2f.1028.410' + 'pci1028,410' + 'pci8086,3b2f.5' + 'pci8086,3b2f' + 'pciclass,010601' + 'pciclass,0106'
    model: 'SATA AHCI 1.0 Interface'
    power-consumption: 00000001.00000001
    66mhz-capable:
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000003
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f,2'
    class-code: 00010601
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b2f
    name: 'pci1028,410'
    Node 0x000011
    acpi-namespace: '\_SB_.PCI0.SBUS'
    assigned-addresses: 8300fb10.00000000.f5430000.00000000.00000100.8100fb20.00000000.00006000.00000000.00000020
    reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020
    compatible: 'pci8086,3b30.1028.410.5' + 'pci8086,3b30.1028.410' + 'pci1028,410' + 'pci8086,3b30.5' + 'pci8086,3b30' + 'pciclass,0c0500' + 'pciclass,0c05'
    model: 'SMBus (System Management Bus)'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000003
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f,3'
    class-code: 000c0500
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b30
    name: 'pci1028,410'
    Node 0x000012
    assigned-addresses: 8300fe10.00000000.f5420000.00000000.00001000
    reg: 0000fe00.00000000.00000000.00000000.00000000.0300fe10.00000000.00000000.00000000.00001000
    compatible: 'pci8086,3b32.1028.410.5' + 'pci8086,3b32.1028.410' + 'pci1028,410' + 'pci8086,3b32.5' + 'pci8086,3b32' + 'pciclass,118000' + 'pciclass,1180'
    model: 'DSP/DAP controllers'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000003
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f,6'
    class-code: 00118000
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b32
    name: 'pci1028,410'
    Node 0x000015
    device_type: 'acpirootnex'
    compatible: 'SOLA0001' + 'acpirootnex' + 'SOLA0002' + 'acpivirtnex'
    acpi-namespace: '\'
    name: 'fw'
    Node 0x000016
    unit-address: '1'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000000
    acpi-processor-id: 00000001
    acpi-namespace: '\_PR_.CPU0'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x000017
    unit-address: '2'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000004
    acpi-processor-id: 00000002
    acpi-namespace: '\_PR_.CPU1'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x000018
    unit-address: '3'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000001
    acpi-processor-id: 00000003
    acpi-namespace: '\_PR_.CPU2'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x000019
    unit-address: '4'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000005
    acpi-processor-id: 00000004
    acpi-namespace: '\_PR_.CPU3'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x00001a
    unit-address: '0'
    compatible: 'acpidevice' + 'SOLA0002' + 'acpivirtnex'
    acpi-namespace: '\_SB_'
    device_type: 'acpidevice'
    name: 'sb'
    Node 0x00001b
    io-space: 00000000.00000020.00000020.00000002.00000024.00000002.00000028.00000002.0000002c.00000002.0000002e.00000002.00000030.00000002.00000034.00000002.00000038.00000002.0000003c.00000002.00000040.00000004.0000004e.00000002.00000050.00000004.00000060.00000001.00000061.00000001.00000063.00000001.00000064.00000001.00000065.00000001.00000067.00000001.00000070.00000008.00000070.00000001.00000080.00000001.00000081.00000011.00000092.00000001.00000093.0000000d.000000a0.00000002.000000a4.00000002.000000a8.00000002.000000ac.00000002.000000b0.00000002.000000b2.00000002.000000b4.00000002.000000b8.00000002.000000bc.00000002.000000c0.00000020.000000f0.00000001.00000400.00000080.000004d0.00000002.00000500.00000080.00000680.00000020.00000930.00000001.00000934.00000001.00000cf8.00000008.00001000.00000004.00001004.00000010.0000164e.00000002.0000ffff.00000001
    device-memory: f54c0000.00001000.f8000000.04000000.fed00000.00000400.fed10000.00004000.fed18000.00001000.fed19000.00001000.fed1c000.00004000.fed20000.00020000.fed45000.0004b000.fee00000.00100000.ff000000.01000000.ff000000.01000000
    dma-channels: 00000004
    interrupts: 00000000.00000001.00000002.00000008.0000000c.0000000d
    name: 'used-resources'
    prtdiag:
    System Configuration: Dell Inc. Latitude E4310
    BIOS Configuration: Dell Inc. A05 11/20/2010
    ==== Processor Sockets ====================================
    Version Location Tag
    Intel(R) Core(TM) i5 CPU M 560 @ 2.67GH CPU 1
    ==== Memory Device Sockets ================================
    Type Status Set Device Locator Bank Locator
    Unknown in use 0 DIMM_A BANK 0
    unknown empty 0 DIMM_B BANK 2
    ==== On-Board Devices =====================================
    "Intel GM45 Graphics"
    NETWORK_NAME_STRING
    ==== Upgradeable Slots ====================================
    ID Status Type Description
    0 available PCI Express x16 J5C1
    1 available PCI Express J6C2
    2 in use PCI Express J6D2
    3 in use PCI Express J7C1
    4 available PCI Express J7D2
    System Information:
    Manufacturer:Dell Inc.
    Product:Latitude E4310
    BIOS Information:
    Vendor:Dell Inc.
    Version:A05
    Release Date:11/20/2010
    BIOS Revision: BIOS Revision:4.6
    Firmware Revision:
    MotherBoard Information:
    Product:0D8H24
    Manufacturer:Dell Inc.
    Version:A00
    Onboard Devices:[Video,Disabled]"Intel GM45 Graphics"
    CPU Information:
    Processor 0:
    Processor Socket Type:CPU 1
    Processor Manufacturer:Intel
    Current Voltage:0.0V
    External Clock:533MHZ
    Max Speed:4000MHZ
    Current Speed:2666MHZ
    Memory Information:
    Physical Memory: 4G (4G)
    Maximum Memory Support: 4096G
    Memory Subsystem 0:
    Array Used Function:System memory
    Memory Error Correction Supported:None
    Maximum Array Capacity:8G
    Number of Memory Devices:2
    Memory Device 0:
    Memory Device Locator:DIMM_A
    Total Width:64
    Data Width:64
    Installed Size:4096M
    Memory Device Type:Unknown
    Speed:1067MHZ
    Memory Device 1:
    [Not Installed]

  • Resource Management and Solaris Zones Developer Guide

    Solaris Information Products ("Pubs") is creating a
    developer guide for resource management and Solaris Zones.
    The department is seeking input on content from application
    developers and ISVs.
    We plan to discuss the different categories of applications
    that can take advantage of Solaris resource management
    features, and provide implementation examples that discuss
    the particular RM features that can be used.
    Although running in a zone poses no differences to most
    applications, we will describe any possible limitations and
    offer appropriate workarounds. We will also provide
    information needed by the ISV, such as determining
    the appropriate system calls to use in a non-global zone.
    We plan to use case studies to document the zones material.
    We would like to know the sorts of topics that you would
    like to see covered. We want to be sure that we address
    your specific development concerns with regard to these
    features.
    Thank you for your comments and suggestions.

    Hi there, i'm using solaris resource management in a
    server with more thant 2thousand acounts.
    Created profiles for users, defaul, staff, root and
    services.Seeing the contents of your /etc/project file could be helpful.
    But while using rctladm to enable syslog'ing, I set up
    global flags of "deny" and "no-local-action" in almos
    everything.The flags on the right hand side of the rctladm(1M) output are read-only:
    they are telling you the characteristics of the resource control in question (what
    operations the system will allow the resource control to take).
    Now, many aplications don't work because they are
    denied enough process.max-stack-size and
    process.max-file-descriptor for them to work.
    Applications such has prstat.If prstat(1) is failing due to the process.max-file-descriptor control value, that's
    probably a bug. prstat(1) is more likely bumping into the limit to assess how many file
    descriptors are available, and then carrying on--you're just seeing a log message since
    prstat(1) tested the file descriptor limit, and you've enabled syslog for that control. Please
    post the prstat(1) output, and we'll figure out if something's breaking.
    I don't find a way to disable the global flags. You can't. I would disable the syslog action on the process.max-stack-size control first;
    there is an outstanding bug on this control, in that it will report a false triggering event--
    no actual effect to the process. (If you send me some mail, I will add you as a call record
    on the bug.)
    Can anyone tell me:
    how to disable global flags?
    how to disable and enable solaris resource management
    all together?You could raise all of the control values, but the resource control facility (like the resource
    limit facility it superseded) is always active. Let's figure out if you're hitting the bug I mentioned,
    and then figure out how to proceed.
    - Stephen
    Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems
    [email protected]

  • Bandwidth Management for Software

    Is there a utility out there that would allow you to allocate specific amounts of bandwidth any software could use? In many download managers (such as Speed Download, Limewire, Azul, etc.) you can easily set the total amount of bandwidth and even per file download parameters. I have always been surprised that browsers such as Safari and even iTunes does not allow you to control the amount of bandwidth it is to use when downloading.
    I often find myself in situations where I need to download a large file, and yet be able to continue to surf for example, or else I would like to keep the setting in my iTunes to download podcasts automatically when I launch it. Both Safari and iTunes, will take as much bandwidth as you can throw at them which means that it can grind every other on line activity to a halt (specially when you do not have a blazing fat connection).
    Anyone know of any such software?
    Thanks.

    Shahin wrote:
    Thanks, but I don't understand what this has to do with bandwidth management? Perhaps I do not understand the capabilities of nice, but isn't nice just a way to prioritize applications and services? How would you use it to allocate bandwidth?
    By giving various jobs different priorities, the effective bandwidth is limited. If you use 100% of the bandwidth for 1% of the time and 0% of the bandwidth for 99% of the time, you are effectively giving the "niced" app only 1% of your bandwidth. And since a computer is digital, there is really no such thing as "instantaneous" bandwidth, as there is in other areas of communication.
    If you have 10 processes running and each consumes 10% of your total bandwidth, it does not matter whether the processes are time-shared or bandwidth-limited, when considered over any reasonable period of time.

  • Help with Solaris.....any help would be nice

    I have to write a paper comparing and contrasting Solaris with DOS/MSDOS.....you wouldnt think this would be hard but it is......is ththere a place where I can find a head to head comparsion? If not perhaps some of you familiar with Solaris could give me some points to start with......I should point out I have never used or seen Solaris I am completely new to this area and it may seem simple but the truth is Im a little overwhelmed by all the information....cant see the forrest for the trees...........so any help would be nice ....thanks in advance

    Hi,
    Solaris is so much more advanced an OS than DOS that a comparison is not straightforward, but here are some less than exhaustive suggestions. Please bear in mind I m not a DOS person, and these are just my personal thoughts on the subject; apologies to Microsoft afficionados for any mistakes.
    Similarities:
    Both DOS and Solaris are Operating Systems. They provide access to machine resources, like a printer port, or a disk ( through the filesystem), by providing an Application Programming Interface, thus saving programmers from learning the underlying details and machine language of each machine they use. So for example in DOS compiler routines make use of INT 21h to access system services.In solaris we use the system call interface (which does a similar thing underneath).
    They also both provide a command shell for ordinary users. In DOS we have command.com, in Solaris you may use Korn shells for example.
    Differences
    DOS is a single user operating system. Solaris is multiuser, multitasking and multiprocessing.
    That is to say Solaris supports multiple programs running on the system at the same time. It will context switch between them to give the illusion of concurrency on a uniprocessor system (time-slicing). On a multiprocessor some tasks will run concurrently.
    Many users can log on to a Solaris system (via a serial terminals, or a network connection (telnet or X windows)) and run programs at the same time. Full networking facilities are built in.
    Dos only provides the ability to fileshare across the network, using the add on Lan Manager.
    Because multiple users run processes (threads/tasks ...) concurrently, Solaris provides extensive security, which DOS doesnt. Each process is owned by a user and runs in its own virtual memory space and is prevented from interfering with any other process memory or other users processes. The operating system and its data is held in protected kernel memory and not directly accessible to processes, so malfunctioning user program cant crash the system accidentally or maliciously.
    Devices and files are protected through filesystem permissions, so a device or file has an owner, a group owner and various permissions attributes such as read/write/execute.
    Solaris also implements filesystem Access Control Lists (ACLs).
    Solaris runs in 32bit protected mode on x86 processors, giving it access to the full address range of the processor (4GB using 4k pages). DOS uses the 16bit segmented memory model.
    On ultrasparc systems or the forthcoming Intel Itanium systems, Solaris runs in 64bit mode, giving it access to vastly more memory and
    faster computation. (note also DOS only runs on x86 processors).
    Who are you writing the paper for? It would probably help some of the readers here with posting suggestions. Some specific questions would be good too.
    However, you should try to get access to a solaris system on a network and maybe have a friendly sysadmin show you around a bit.
    Do you know anyone with a LINUX system? Solaris and LINUX are variants of the UNIX OS and for your purposes a comparison of LINUX and DOS may suffice.
    Hope that is some help.
    Ralph
    SUN DTS

  • WAAS - Bandwidth Management support?

    WAAS - Bandwidth Management support?

    Sorry, I had a problem with the web. My comment was:
    I know that other products such as Juniper's WXC supports Bandwidth Management. Does Cisco WAAS support it too?
    Bandwidth Management means:
    - Guarantee a minimum bandwidth for your most critical applications.
    - Set maximum bandwidths to limit (or drop) low-priority traffic.
    - Set priorities to determine how the “excess” bandwidth is allocated.
    Thanks in advance.
    José Luis

  • Qos/bandwidth management possible from 2950?

    Hello,
    I was curious as to how granular I can be with bandwidth management on a C2950 switch. What I would like is to be able to restrict any SESSION to 300 kilobits or less depending on the IP Traffic type. Basically what I have is MS Terminal Servers connected to a C2950 switch in turn connected to a c2621 router which in turn sends RDP,Printing and Web Traffic back to clients, who are connected using PPPoe w/ C837's. Is it even possible to be able to restrict bandwidth by session, anywhere in this setup?
    Thanks for any help. I just started researching QOS, Bandwidth Management and am lost as to where I should be looking for help. Due to the fact that I want to restrict by single sessions not by total amount of traffic, its confusing trying to get help.

    You can do this with a 2950, as long as you run the EI image (enhanced). Check the QOS section where it says Policing in this document. Its in pdf format.
    http://www.cisco.com/application/pdf/en/us/guest/products/ps628/c2001/ccmigration_09186a00801cde4b.pdf
    HTH
    Sankar
    PS: please remember to rate posts!

Maybe you are looking for