Sponsored Content
Operating Systems Solaris Compiling Error in Samba 3.4.1 on Solaris 10 Post 302456476 by hergp on Friday 24th of September 2010 10:10:16 AM
Old 09-24-2010
sathya47, you have to edit autogen.sh and replace every occurrence of "which" with "ksh whence". Then try again to run autogen.sh
This User Gave Thanks to hergp For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

Error on compiling php for GD on SOLARIS 10

Hi everyone, I have SUn E250 server running solaris 10. I have installed apache 2 + MySQL + PHP-5.1.4 following the guidelines on this website http://meljr.com/~meljr/AMPSolaris10.html Excellent document for first time installation. Now, because I wanted to use Coppermine Photo Gallery, I... (9 Replies)
Discussion started by: callingrohit
9 Replies

2. UNIX and Linux Applications

Compiling samba 3.0.27a under AIX

I try to compile Samba 3.0.27a under AIX with LDAP and KErberos. The configure work fine: CFLAGS: -I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include ./configure --prefix=/opt/pware/samba/3.0.27a... (1 Reply)
Discussion started by: BenediktS
1 Replies

3. AIX

Compiling samba 3.0.27a under AIX

Compiling samba 3.0.27a under AIX I try to compile Samba 3.0.27a under AIX with LDAP and KErberos. The configure work fine: CFLAGS: -I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include ./configure... (2 Replies)
Discussion started by: BenediktS
2 Replies

4. Solaris

Samba Compiling questions

OS: Solaris 10 I downloaded a binary from samba.org (3.0.24) I extracted the file and ran the following command: # ./configure --prefix=/usr/sfw --with-configdir=/etc/sfw --with-winbind Now I am trying to understand the compile process but I can't find many answers online ... (10 Replies)
Discussion started by: Keepcase
10 Replies

5. AIX

Compiling samba from source in AIX 5.3

Hello all. I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs with no issues, but when the time comes to make, this happens: make: make 1254-025 There must be an existing description file or specify a target. ... (4 Replies)
Discussion started by: raidzero
4 Replies

6. Solaris

Problem compiling Samba 3.5.1 on Solaris 10 with gcc (3.4.6)

I'm getting this error when 'Linking shared library bin/libtalloc.so.2'... anyone know what's up here? Using CFLAGS = -O -I. -I/source/samba-3.5.1/source3 -I/source/samba-3.5.1/source3/../lib/popt -I/source/samba-3.5.1/source3/iniparser/src -Iinclude -I./include -I. -I. -I./../lib/replace... (6 Replies)
Discussion started by: son_t
6 Replies

7. Programming

Sun Solaris C++ Compiling Error

Hello. I'm using SunStudio 12 Update 1. When compiling for x86, everything works fine. When compiling for SPARC, I get the following errors. I linked libCstd.so.1 explicitly, but I get the same errors. Would anyone be kind enough to step me through resolving this? Thank you very much. **... (2 Replies)
Discussion started by: acheong87
2 Replies

8. UNIX for Dummies Questions & Answers

Compiling samba problem

People i download the lastest version of samba i`am tryng to compile it in a solaris 9 i'm reading the how to of samba, i am in the first step making the autogen.sh but show me this when i do ./autogen.sh ./autogen.sh: running script/mkversion.sh ./script/mkversion.sh: 'include/version.h'... (0 Replies)
Discussion started by: enkei17
0 Replies

9. UNIX Benchmarks

error compiling bm software under Solaris 10

anyone tried it , under Solaris 10 using make (part of SUNWsprot) and gcc 4.6 compiler.. got an error complaining about the Makefile script syntax... I don't think that's compatible at all... (2 Replies)
Discussion started by: ppchu99
2 Replies

10. UNIX for Beginners Questions & Answers

Compiling Samba 4.4.5

I am running Fedora V21 and had their default Samba installed. But I wanted to put up a PDC with ADS, so I uninstalled samba and down loaded the Samba 4.4.5 source along with the Kerberos devel kit etc. I then configured and compiled etc and it indicated it was successful. But I can't load the... (0 Replies)
Discussion started by: griffinmt
0 Replies
scconf_dg_rawdisk(1M)					  System Administration Commands				     scconf_dg_rawdisk(1M)

NAME
scconf_dg_rawdisk - add, change or update raw-disk device group configuration SYNOPSIS
scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true] scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true | false] scconf -c -D name=diskgroup,autogen=true scconf -r -D device_service_name [,nodelist=node[:node]...] [,globaldev=gdev1,...] DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. The scconf_dg_rawdisk utility adds, changes or updates raw-disk device group configuration A raw disk is a disk that is not being used as part of a volume manager volume or metadevice. Raw-disk device groups allow you to define a set of disks within a disk device group. At system boot, by default, a raw-disk device group is created for every Disk ID pseudo driver (DID) device in the configuration. By con- vention, the raw-disk device group names are assigned at initialization and are derived from the DID names. For every node added to a raw- disk disk device group, the scconf utility verifies that every device in the group is physically ported to the node. The scconf -a (add) command can be used to create a raw-disk device group with multiple disk devices configured in it. A raw-disk device group is created for every disk device in the cluster at boot time. Before you can add a new raw-disk device group, devices to be used in the new group must be removed from the device group created at boot time. Then a new raw-disk device group can be created containing these devices. This is accomplished by creating a list of these devices in the globaldev option of scconf along with a potential primary node preference list in the nodelist option. If the device group already exists, only new nodes and global devices will be added and nodes or devices which are part of an existing device group will be ignored. If the preferenced suboption is not given with the-a option to create a new device group, then it is, by default, false. However, if the preferenced suboption is specified for the existing device group with a value of true or false, an error is returned. This is done in order to maintain the existing nodelist preference state. If a device group should be mastered by only a particular node then it should be configured with the otheroption set to localonly=true. Only one node can be specified in the node list to create a localonly device group. The scconf -c (change) command is used to change the order of the potential primary node preference, to enable or disable failback, to set the desired number of secondaries, and to add more global devices to the device group. If you want to change the order of node preference list, then all the nodes currently existing in the device group must be specified in the nodelist. In addition, if you are changing the order of node preference, you must also set the preferenced suboption to true. If the preferenced suboption is not specified with the change, the already established true or false setting is used. New nodes cannot be added using the change form of the command. Change option can also be used for changing a device group to localonly device group and vice-versa. To change a device group to a localonly device group, set otheroption to localonly=true. Specify localonly=false to set it back to not the localonly device group. nodelist must already be set to a list of one node, or an error results. It is legal to specify a nodelist with the change form of the command, when you set localonly to true. This is, however, redundant, since the list can only contain the single node that is already configured. It would be an error to specify any other than the node that is already configured. The scconf -r (remove) command can be used to remove the nodes, global devices, and the device group name from the cluster device-group configuration. If nodes or global devices are specified with the device-group name, they are removed from the device group first. After the last device and node are removed from the device group, the device group is also removed from cluster configuration. If only the name of the device group is given (no nodes or devices at all), the entire device group is removed. If a raw-disk device name is registered in a raw-disk device group, then it cannot be registered in a Solaris Volume Manager device group or a VERITAS Volume Manager device group. OPTIONS
See the scconf(1M) man page for the list of supported generic options. The following action options are used to describe the actions performed by the command. Only one action option is allowed in the command. The following action options are supported: -a Add a new raw-disk device group to the cluster configuration. You can also use this option to change the device group configuration. -c Change the ordering of the node preference list, change preference and failback policy, change the desired number of secondaries, and also add more devices to the device group with the globaldev option. It is also used to set a device group as local only. -r Remove the raw-disk device group name from the cluster. The autogen flag is an indicator of the scconf command. This command does not list devices with the autogen property unless the -v command line option is used. When a device is used with the change form of the scconf command, the device's autogen property is reset, or set to false, unless autogen=true is also specified. EXAMPLES
Example 1 Using scconf Commands The following scconf commands create a raw-disk device group, change the order of the potential primary nodes, change preference and fail- back policy, change the desired number of secondaries, and remove the raw-disk device group from the cluster configuration. host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1:host2:host3,preferenced=false,failback=enabled, numsecondaries=,globaldev=d1,globaldev=d2 host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1,globaldev=d1,globaldev=d2,localonly=true, globaldev=d1,globaldev=d2 host1# scconf -c -D name=rawdisk_groupname, nodelist=host3:host2:host1,preferenced=true,failback=disabled, numsecondaries=2,globaldev=d4,globaldev=d5 host1# scconf -c -D name=rawdisk_groupname,localonly=true host1# scconf -r -D name=rawdisk_groupname host1# scconf -r -D name=rawdisk_groupname,nodelist=host1,host2 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), attributes(5) Sun Cluster 3.2 13 Aug 2007 scconf_dg_rawdisk(1M)
All times are GMT -4. The time now is 02:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy