Solaris 10 Samba - swat is in mainenance mode

I am trying to enable swat but can only get it to maintenance mode. Samba and winbind both enable ok. What do I need to do to get swat to go online?
I have:
{color:#000000}*SunOS troy 5.10 Generic_138889-08 i86pc i386 i86pc*{color}
I have added the following 2 lines to */etc/services*
swat 901/tcp
swat 901/udp
I have added the following two lines to */etc/inetd.conf*
netbios-ssn stream tcp nowait root /usr/sfw/sbin/smbd smbd
swat stream tcp nowait root /usr/sfw/sbin/swat swat
and applied the changes:
troy root>inetconv -i /etc/inetd.conf
I have the following smb.conf file:
[global]
workgroup=DOM
realm=DOM.FQN.UK
security=ADS
encrypt passwords = yes
password server = MMM-DC-01
preferred master = no
server string = "Samba on Troy"
log level = 10
log file = /var/adm/samba_log.%m
max log size = 50
winbind use default domain = yes
winbind trusted domains only = yes
idmap uid = 70000-80000
idmap gid = 70000-80000
winbind enum groups = yes
winbind enum users = yes
[vmbackup01samba]
path = /opt/local
valid users = DOM.FQN.UK\dcar
read only = No
and I have restarted inetd, samba, winbind and swat but swat goes into maintenance mode and there is no log file for it in /var/svc/log.

Is there an .xml file in /var/svc/manifest/network for it? What do you get with svcs -x and svcs -l?
Edited by: mdinaz on Jul 14, 2009 9:28 AM

Similar Messages

Solaris 10 Printer share by Samba SWAT. Then install onto windows client

Hello,
I am having trouble with below.
1) Installing printer on Solaris 10
2) Sharing the printer via SWAT
3) Install the printer on Solaris from Windows client.
Where can I find the basic information for above 3 which I need to achieve?
I have installed the printer locally onto Solaris 10, and was able to print, but I just can't share it to Windows.
And because of that, I am not sure if I am doing the local printer installation in the right way or not..
If anybody can lead me to a good website or good document for printer installation and sharing,
please let me know.
Regards,
Tanuki

Well, if you don't think the online Documentation helpful, then the better way is reading step-by-step instructions from a book. Get to local bookstore, i.e Barne&Nobles or Border or any big local bookstore, there should be pretty good book for Unix Administrator (Solaris version).
If you have time and think you can memorize then, read on the spot; otherwise, buy the book for future reference.
If that's not what you had in mind, then this link of free online book might help : http://www.oreilly.com/catalog/solaris8/chapter/ch04.html
Normally, oreilly online bookstore offers free books to accredited universities, colleges, and organizations. However, if that option isn't for you, it might even offer free sample chapters that might just suit your needs.
hoep it helps.
-van.

New to Solaris, Some Samba and NTFS issues.

Hi Im new to solaris and trying out ZFS which has been great.
Im haivng some trouble that I cant find up to date info on so here goes:
First how do you mount an NTFS volume in Solaris 11 Express?
I need to access the data on an NTFS drive to populate my new ZFS tank.
Secondly, I have read only access on my samba shares from windows machines but my smb.conf looks right. a copy of my smb.conf will follow
Any suggestions would be appreciated.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = share
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/samba/log/log.%m
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
passdb backend = smbpasswd
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/sfw/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/sfw/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[Series]
comment = TV Series
path = /home/Kirby/Series
public = yes
only guest = yes
writable = yes
printable = no

875739 wrote:
Hi Im new to solaris and trying out ZFS which has been great.
Im haivng some trouble that I cant find up to date info on so here goes:
First how do you mount an NTFS volume in Solaris 11 Express?
I need to access the data on an NTFS drive to populate my new ZFS tank.I never had a need for it but I think you'll have to compile fuse ntfs-3g manually.
http://web.archiveorange.com/archive/v/u46DbWSGcIzl7pexf4hQ
>
Secondly, I have read only access on my samba shares from windows machines but my smb.conf looks right. a copy of my smb.conf will follow
Any suggestions would be appreciated.You don't need to use Samba in Solaris 11 Express.
http://download.oracle.com/docs/cd/E19963-01/html/821-1448/gaynd.html#gayne

Samba/Swat in maintenance state

I am trying to share solaries folder for windows.
I am using solaries 10. I have made changes using swat https://127.0.0.1:901.
when I am checking status of samba using command svcs samba;
it is showing me status as maintenance .
how to bring samba online.
please help.

What do you see when you do svcs -x samba?

Solaris 10 x86 infiniband support for connected mode?

Anyone know when solaris 10 x86 is going to support connected mode infiniband?
Large MTU size is what I'm looking for, 65520 as opposed to 2044.
Running....
Solaris 10 10/08 s10x_u6wos_07b X86
X4600 with dual port pcie infiniband card.
thanks.
Edited by: njk3rd on Jul 5, 2010 11:06 AM

Hi, i'm Chris from Argentina.
Same Hardware A7n8x-e Deluxe, and same problem. Solaris 10 is unable to detect mi SATA harddrive.
I do have a PATA harddrive so i'll try to install it in there. But i want mi Sata to work.
I'll continue searching for a solution a while before using a pata hd.

Solaris 10 + Samba + LDAP/PAM?

Hi all,
I've got a long standing question that I need answered with relation to setup of Samba + LDAP on Solaris 10. Here is the general gist:
1. I've got a Solaris 10 host that is currently communicating with an OpenLDAP (OpenDirectory) master to provide user identity information. The Solaris 10 host simply acts as a place to have disk mounted via some large storage subsystems, which is then shared out via NFS to different places. Because I have used the ldapclient manual commands on the Solaris host, it understands UID's and GUID's from the OpenLDAP master
2. I want to change things a little bit. What I'd like to do, is have samba sharing out disk/exports/shares from the Solaris 10 host, but use my OpenLDAP credentials for users to log into the system with
What I'd like to know how to do is set up Samba on my Solaris 10 (x86) host so that a client can connect to it using their credentials stored on the OpenLDAP host, access their home directory etc.
I don't think it will be too hard - as most of the work is done in terms of the LDAP binds. I have used the following binding technique to make the Solaris 10 host aware of the OpenLDAP directory:
ldapclient -v manual -a credentialLevel=anonymous -a defaultSearchBase=dc=od-master,dc=example,dc=com -a serviceSearchDescriptor=passwd:cn=users,dc=od-master,dc=example,dc=com -a attributeMap=passwd:gecos=cn -a serviceSearchDescriptor=group:cn=groups,dc=od-master,dc=example,dc=com 192.168.0.1Because I've done this, I can now finger/id any UID or GUID that exists on the OpenLDAP host, and the Solaris host will know about it. The question is, how do I make samba aware of such things, let alone configure it to do so. I want users on their windows systems to simply be able to \\some.server.here.there\ and on their Mac OS X systems to smb://some.server.here.there with the credentials that are in the OpenLDAP master. There must be some simple way of telling samba where to get credential information from, right?
Thanks for your time!
z

Update 2 is pretty old, especially if you are talking about ZFS. There's been a variety of problems fixed in ZFS since U2. Were I to just guess out of the blue, you might be running into the ZFS eats all of RAM bug.
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6505658
If this is the case, it won't be just the samba server that's slow on the server. You should check this by doing the FTP after your samba server slows down and see if you get fast throughputs.
-r

How to boot solaris 10 on SunFireV20z in 32-bit mode.

Hi,
I have installed solaris 10 on SunFire V20z (AMD).
By default it is booting in 64-bit mode. How do I boot it in 32-bit mode.
# uname -a
SunOS bangpcisol4 5.10 Generic i86pc i386 i86pc
# isainfo -kv
64-bit amd64 kernel modules
Please suggest.
Thanks & Regards,
-GnanaShekar-

How do I automate this?Run the following command with root privileges: /usr/sbin/eeprom boot-file="kernel/unix"To switch back to 64 bits, run eeprom again: /usr/sbin/eeprom boot-file="kernel/amd64/unix "Please read the man page of "eeprom" for more information.

Solaris 9 & Samba

I'm new to Solaris but have a fresh install of Solaris 9 4/04 release. I did the full plus OEM install. I thought from what I read that this would install samba too. But, the only reference I can find to samba on this system is the smb.conf-example file. I can't find what looks like a working installation of Samba. Am I going to have to download Samba, or does it just not get installed in /usr/local like the examples I've read.

A Basic Samba Configuration File
The key to configuring Samba is its lone configuration file: smb.conf. This configuration file can be very simple or extremely complex, and the rest of this book is devoted to helping you get deeply personal with this file. For now, however, we'll show you how to set up a single file service, which will allow you to fire up the Samba daemons and see that everything is running as it should be. In later chapters, you will see how to configure Samba for more complicated and interesting tasks.
The installation process does not automatically create an smb.conf configuration file, although several example files are included in the Samba distribution. To test the server software, though, we'll use the following file. It should be named smb.conf and placed in the /usr/local/samba/lib directory.
[5] If you did not compile Samba, but instead downloaded a binary, check with the documentation for the package to find out where it expects the smb.conf file. If Samba came preinstalled with your Unix system, there is probably already an smb.conf file somewhere on your system.
[global]
     workgroup = SIMPLE
[test]
     comment = For testing only, please
     path = /export/samba/test
     read only = no
     guest ok = yes
This brief configuration file tells the Samba server to offer the directory /export/samba/test on the server as an SMB/CIFS share called test. The server also becomes part of the named workgroup SIMPLE, which each of the clients must also be a part of. (Use your own workgroup here if you already know what it is.) We'll use the [test] share in the next chapter to set up the Windows clients. For now, you can complete the setup by performing the following commands as root on your Unix server:
# mkdir /export/samba/test
# chmod 777 /export/samba/test
We should point out that in terms of system security, this is the worst setup possible. For the moment, however, we only wish to test Samba, so we'll leave security out of the picture. In addition, there are some encrypted password issues that we will encounter with Windows clients later on, so this setup will afford us the least amount of headaches.
If you are using Windows 98 or Windows NT Service Pack 3 or above, you must add the following entry to the [global] section of the Samba configuration file: encrypt passwords = yes. In addition, you must use the smbpassword program (typically located in /usr/local/samba/bin/) to reenter the username/password combinations of those users on the Unix server who should be able to access shares into Samba's encrypted client database. For example, if you wanted to allow Unix user steve to access shares from an SMB client, you could type: smbpassword -a steve. The first time a user is added, the program will output an error saying that the encrypted password database does not exist. Don't worry, it will then create the database for you. Make sure that the username/password combinations that you add to the encrypted database match the usernames and passwords that you intend to use on the Windows client side.

Solaris 10, Samba 3.0.25a - Server dies copying big files to ZFS volume

Hope someone can help me with this problem, cos I am at my wits end.
We have Solaris 10 Update 2 running on a Sunfire V215 Sparc Server with 2 large storage arrays running ZFS
When copying a large file via samba, after about say 200-300megs... the copy just stops... and the samba server becomes unresponsive for quite a while.
When we first noticed the problem, we had the original Samba 3.0.11 which shiped with SOL 10 Up2, so we hoped the upgrade to Samba 3.0.25a would fix the problem. No such luck.
I have tested with FTP (the same 2.6 GB file) and that transfers completely and very fast, so I am pretty damn sure its not a hardware issue.
I have tested with varios samba configurations. Vanilla configs, tweaked configs, configs which people claim solve some issues... again no luck.
I have looked around these forums and seen that some people have experience samba issues when upgrading from Sol 9 to Sol 10.
Please if ANYONE has any ideas what could be causing this and how to solve it, I would be extremely greatful
Thanks
//Steve
Edited by: reyortsed on Sep 23, 2008 12:29 PM

Update 2 is pretty old, especially if you are talking about ZFS. There's been a variety of problems fixed in ZFS since U2. Were I to just guess out of the blue, you might be running into the ZFS eats all of RAM bug.
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6505658
If this is the case, it won't be just the samba server that's slow on the server. You should check this by doing the FTP after your samba server slows down and see if you get fast throughputs.
-r

NTp Solaris 10 Slew or step mode

Hi Team,
Could you please let us know how we can check if server is running in SLEW or STEP mode in Solaris 10 OE .
I Dident find any command and also checked ntp.conf file for Disable pll entry but could not come to the actual result that if system running in Slew or Step .
Please let us know how we can verify the same.
also I request if possible where we can get more details about NTP on Solaris 10 .
Best Regards.

wiprosupport wrote:
Could you please let us know how we can check if server is running in SLEW or STEP mode in Solaris 10 OE .STEP isn't a mode, it's a single operation. If the daemon finds out that the time is "too far out" (128ms), then it will correct that time with a single step. If the offset is closer, then it will be trying to modify the system clock so that the offset is removed.
also I request if possible where we can get more details about NTP on Solaris 10 .Solaris 10 appears to ship with the same version of xntp that older Solaris distributions contained. It works in many situations, but is very, very old.
A good location for NTP information (on any OS) is probably comp.protocols.time.ntp. Several of the developers use that newsgroup. But they're not going to be interested in talking about the version that comes with Solaris due to its age. You may want to grab a more recent version and install it.
Darren

Core 2 Duo and solaris x86 11/06 works for me

This is FYI, since I seen (and posted) problems, but I haven't seen the solution posted.
I have successfully gotten solaris x86 11/06 to install and run on my core 2 duo machine. I had tried solaris x86 06/06, but I could only run in 32bit mode until patch 118855-19 was installed. It looks like 118855-33 is the baseline for 11/06.
With 06/06 I had to edit the grub command and add " kernel/unix" to the end of the 2nd line. This would force 32 bit mode rather than 64 bit. If I tried 64 bit, it would enter an endless reboot cycle. Once I installed the patch to 118855-19 I could run solaris 10 06/06 in 64 bit mode without issue.
Again, since solaris 10 11/06 is at 118855-33, it runs on my core2 machine straight from the install.
Hope this helps

On a laptop there is little point with running a 64-bit operating system unless it physically has more than 4gb of ram, or if you are processing datasets exceeding 4GB of ram. Unless you're into assembly or use Solaris for some reason to manipulate media, little is to be gained by using 64-bit versions if anything. The increased pointer, integer, and padding causes more memory to use for the same software, most software on 64-bit operating systems runs in 32-bit mode because there is no need to have 16 exabyte memory addressing capability for anything but media encoders, giant databases, or extremely bloated single-threaded software. Sun Java Creator takes a heck of a lot of ram, but even at peak it's still under 4GB. If you move files bigger than 4GB, the ability to memory map all 4096MB might have less overhead on a 64-bit operating system, but generally from an end-user perspective, especially on a fast Intel or Opteron system, you won't notice the difference much. Solaris is bi-arch, a large chunk of Windows Vista and XP x64 is bi-arch, and most of FreeBSD and Linux are bi-arch in 64-bit versions, as I said, no point in making everything 64-bit. 64-bit device drivers is an issue for every OS, you should stick with 32-bit on a laptop, and hold off on desktops unless you need extended assembly registers available only in 64-bit mode.

Use of __typeof__ in Solaris Studio 12.4

Solaris Studio 12.3 had a __typeof__ operator similar to decltype in C++11. This is available in a portable wrapper using the Boost macro BOOST_TYPEOF_TPL. It looks like the Solaris Studio team contributed the modification to Boost which added this in ticket 5745.
Now Solaris Studio 12.4 has a C++11 mode which supports decltype. However, is __typeof__ still supposed to work in Solaris Studio 12.4's C++03 mode? It doesn't seem to work as well as it used to.
The following program deduces the return type of operator() using __typeof__:
#include <boost/typeof/typeof.hpp>
#include <boost/type_traits/remove_reference.hpp>
#include <iostream>
#include <typeinfo>
// Helper to deduce the result type from a member function pointer.
template<typename T>
struct member_function_result_type
template<typename T, typename R, typename A1>
struct member_function_result_type<R (T::*)(A1) const>
    typedef typename boost::remove_reference<R>::type type;
template<typename T>
struct function_result_type
    typedef BOOST_TYPEOF_TPL(&T::operator()) F;
    typedef typename member_function_result_type<F>::type type;
template<typename R, typename A>
struct function_result_type<R (*)(A)>
    typedef typename boost::remove_reference<R>::type type;
struct my_functor
    float operator()(float numerator) const
        return numerator / 2.0f;
int main(int, char **)
    typedef typename function_result_type<my_functor>::type my_type;
    my_functor f;
    my_type ret = f(5.0f);
    if (typeid(my_type) == typeid(float))
        std::cout << "As expected " << ret << std::endl;
    else
        std::cout << "Oh dear " << ret << std::endl;
    return 0;
If you build this with Solaris Studio 12.3 as follows:
CC -m64 -I/usr/local/include/boost-1_54 main.cc
then it compiles and running a.out shows the return type of float has been correctly deduced.
However, with Solaris Studio 12.4 the same command:
CC -m64 -I/usr/local/include/boost-1_54 main.cc
results in:
"main.cc", line 23: Error: Unexpected type name "F" encountered.
"main.cc", line 42: Warning: "typename" must be used within a template.
1 Error(s) and 1 Warning(s) detected.
Now, obviously Solaris Studio 12.4 has a C++11 mode and it is possible to get this program to work by changing BOOST_TYPEOF_TPL to decltype and building with:
CC -std=c++11 -m64 -I/usr/local/include/boost-1_54 main.cc
But Solaris Studio 12.4's C++11 mode has other problems, so is there any way to somehow get a working __typeof__ or equivalent in Solaris Studio 12.4's C++03 mode?
(In case it makes any difference this is on Solaris 10 x86.)

I couldn't see that any of the items listed in the "Enforcement of C++ rules" section of the documentation would affect this program.
Here's a cut down version of the test program that doesn't use Boost:
#include <iostream>
#include <typeinfo>
// Helper to deduce the result type from a member function pointer.
template<typename T>
struct member_function_result_type
template<typename T, typename R, typename A1>
struct member_function_result_type<R (T::*)(A1) const>
    typedef R type;
template<typename T>
struct function_result_type
    typedef __typeof__(&T::operator()) F;
    typedef typename member_function_result_type<F>::type type;
template<typename R, typename A>
struct function_result_type<R (*)(A)>
    typedef R type;
struct my_functor
    float operator()(float numerator) const
        return numerator / 2.0f;
int main(int, char **)
    typedef function_result_type<my_functor>::type my_type;
    my_functor f;
    my_type ret = f(5.0f);
    if (typeid(my_type) == typeid(float))
        std::cout << "As expected " << ret << std::endl;
    return 0;
Interestingly this doesn't compile with either Solaris Studio 12.3 or Solaris Studio 12.4, but each gives different errors:
Solaris Studio 12.3:
CC -m64 main.cc
>> Assertion: unexpected type_builder::visit_unspec (../lnk/v2mangler.cc, line 1636)
    while processing main.cc at line 39.
Solaris Studio 12.4:
CC -m64 main.cc
"main.cc", line 20: Error: Unexpected type name "F" encountered.
1 Error(s) detected.
So Solaris Studio 12.4 is basically failing in the same way as the original test program that used the Boost wrappers. Solaris Studio 12.3 is failing with an assertion error that doesn't occur when the Boost wrappers are used.
It turns out that __typeof__ was only used in one place in our codebase (wrapped by Boost), so I've just removed it and implemented that code in a different way. So this isn't blocking upgrade of Solaris Studio, and we don't even have __typeof__ in our codebase any more, but I just thought you might be interested to have this program as a test case for future development.
It works fine with clang++ in C++03 mode on Mac OS X so I doubt the problem is caused by the source code not conforming to standard:
clang++ main.cc
./a.out
As expected 2.5
This case may be particularly tricky for a compiler to handle due to __typeof__ being applied to a pointer to a const member function.

Problems installing Solaris 10 on Dell PowerEdge 800

Hi,
I am experiencing some trouble when I attempt to install Solaris 10 on a Dell PowerEdge 800. It is equipped with two RAID disks controlled by a Dell CERC SATA 1.5/6ch (according to the BIOS).
The installation program reports that it cannot write to the disk. This happens when it is about to start installing files. Tried setting it to a single volume and disable RAID. Same thing. Read another article saying something about disabling IDE, well it doesn't seem to help ...
Any hints?

I have the same problem on a dell 750 with the SERC controller. I can add some more information but if you get a solution I would appreciate the detail.
1) If I install Solaris via the SERC in RAID 1 mode then the alarm on the SERC goes off as soon as I start to write to the disk.
2) I bypassed the SERC and installed on a single disk straight off the motherboard. Time the install crashed at the same point but this time the error message told me that the first available cylinder was number 3! Ah
3) I reconnected the disk via the SERC, rebuilt the RAID array and made a mistake. I created a RAID 0 (striped) array and installed the software starting from cylinder 3. I got a complete solaris install that rebooted fine and is fully working.
BUT I NEED A MIRRORED SYSTEM SO
4) I rebuild the machine again this time RAID 1 and again the crash occured at exactly the same point i.e. as soo as I start to write to the disk.
Whether or not DELL / Adaptec support Solaris should not be an issue. This is a BIOS configurable RAID controller that can be fully serviced (e.g. disks replaced) from the BIOS. The system sees the array as a disk via the controller and indeed it is seeing it.
The SERCs own data configuration data should be on sectors which are not visible to solaris VIA the SERC so we shouldnt be able to damage them but I suspect that this may not be the case.
I suspect that the answer is in the partition layout and who or what creates them (I dont mean the Solaris slices but the FDISK partitions)
To make matters worse, since I need the machine working I went back to disks straight of the motherboard and configured again and used metadevices to set up a fully mirrored systemas I have done many times before on sparc (but never on Solaris x86)
This worked fine but I thought that I would test bootability in the event of disk failure. There isnt any!
if disk 1 fails then the motherboard wont accept disk 2 unless you swap the cables and move it do disk 1 and by then the boot sectors are wrong for the address of the device. I can probably solve this by building both disks in slot one but who wants a mirrored server that you have to open up and move a cable when the disk fails. I think I may have to ditch SATA and go back to SCSI !

Solaris 10 on virtual pc , vmware or qemu ?

Hi, i'm new to Solaris. i was wondering if i could install Solaris 10 on any of these ?. My goal is get SCSA. My options are,
Intel Core 2 Duo, Intel 975 mobo (unsupported). or
Intel Pentium D, Intel 945 mobo (supported) or
getting old IBM Intellistation E pro (P4 1.7Ghz, i845 chipset) or ThinkCentre A51 (P4 3.06 Ghz, i915)
Core, D and ThinkCentre models would cost the same, and E Pro will be around $250 (including 19" monitor)
any suggestions ?. Thanks in advance.

I really doubt whether Solaris 10 will run properly (if at all) on Core 2 Duo. I have been trying to install on my Core 2 Duo for two months now with both Solaris 10 and the latest Solaris Express - no luck. As soon as the pc reboots after installing, I either find myself staring at a black screen or my box goes into endless rebooting.
I have noticed that I am not the only one who is affected by this weird behavior. I have read similar complaints from people who are also running Core 2 Duo, Pentium D or Centrino. I also found a forum which points out that neither of these CPUs is currently supported by Solaris, at least not in 64 bit mode (32 bit mode does appear to work, but I am just too fed up to even give it a try...). I guess Linus Torvalds was right to point out that hardware support under solaris is a hoax.
Whatever, the same behavoir appears to affect Solaris running inside vmware (although I cannot confirm this). Read this one for example :
http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/common/html/wwhelp.htm?context=guestos_new&file=guestos_solaris10.html

Symbolic links on samba network drives broken?

Note: I first posted this in Apple.com > Support > Discussions > Mac OS X v10.5 Leopard > Using Mac OS X Leopard where it was suggested I post here. In my readings it looks like 10.6 may solve some of this but I'm not sure.
I'm seeing the following sort of behaviour on all of the macs I have tested in the following configuration:
Network file server:
Solaris 10
samba 3.4.2
Macs:
Leopard 10.5.6
Connect to exported folders via smb in finder "connect to server". In the examples below abc123 is a remote folder.
Open terminal and try the following tests:
1. Attempting to remove a symbolic link fails.
* cd /Volumes/abc123/tmp
* touch foo
* ln -s foo .bar # this works
* rm .bar # fails with no message
* rm foo # succeeds
* rm .bar # fails with no message
If the symbolic link is to a socket then you at least get a message when rm fails ("rm: .parentlock: No such file or directory" as an example for a link created on the remote drive by Thunderbird or Firefox).
2. Removing linked file removes unlinked file??
* touch foo
* ln -s foo bart
* touch ._bart
* ls -la # observe that ._bart exists
* rm bart
* ls -la # observe that bart still exists, but that ._bart is gone!!!
3. Removing linked file does not work.
* ln -s bart ._bart
* rm bart # fails
4. Hard links do not delete either.
* touch foo
* ln foo ._bart
* rm foo
* ln -s bar ._bart # ln: ._bart: File exists
* rm ._bart # rm: ._bart: No such file or directory
5. Symbolic links are copied instead of the file contents.
* touch foo
* ln -s foo ._blaht
* cp ._blaht /tmp
and observe that, in /tmp, you have "._blaht -> foo" instead of the actual file.
So can anyone else reproduce any of the above problems? In my limited searching for samba related problems I did not see any posting about this type of situation. Also, everything works just fine on local drives.

Depending on the filesystem, Mac OS X creates ._foo files when you create a foo file, so you'll probably have to live with that. For example, for each file on my FAT32-formatted USB flash drive there is a ._xxx file. Others may be able to explain what these things are. I'm pretty sure they contain file metadata, perhaps like .DS_Store files created for other file systems.

Solaris 10 Samba - swat is in mainenance mode

Similar Messages

Maybe you are looking for