9 More Discussions You Might Find Interesting
1. Solaris
Hey guys,
i'm pretty sure this is simple enough so i'll go quick. I must be missing something but can't pinpoint it.
NOTE: Yes, i should be using proftpd but the architect team is a pain in the butt and it is not possible right now.
Sol10 FTP server (zoned) MS vista ftp client.
Login... (1 Reply)
Discussion started by: maverick72
1 Replies
2. Solaris
Hi,
im new to Solaris (10) and need some help please.
Situation: Actually is there a Linux (SLES11) OpenLDAP-Server and authentification of Linux-Maschines works pretty sweet. Now i want to put the SOL10 (Sparc) boxes in....
Problem: User Authentification via OpenLDAP on Sol10 doesn´t work... (3 Replies)
Discussion started by: Panzerkampfwagn
3 Replies
3. Solaris
I just ran the latest ( 9-27-11) solaris patch set on my sparc testbed ( ultra80 ). Brought down to single user mode and ran patches as I always have. When I rebooted it after completion it came up with the following error on boot.
"Fast Access Data MMU Miss".
I can boot to a cdrom in... (5 Replies)
Discussion started by: bow tie klr
5 Replies
4. Solaris
Hi
What kind of Sun machine, you recommend to buy in order to learn Solaris 10 administration ?
I need machine where I can train the following sol10 features :
- zfs
- solstice suite (RAID 0+1, RAID 5, RAID 1 + 0 )
- containers
Please advice sth for reasonable price.
thx for help. (8 Replies)
Discussion started by: presul
8 Replies
5. Solaris
Hello all. I am going to build an x86 Solaris box. Sun only offers it in a 64 bit flavor.
I want to put MySQL on this box. MySQL only comes in a 32 bit version for x86 Solaris.
Can I run 32 bit apps on a 64 bit x86 Solaris machine?
Thanks! (4 Replies)
Discussion started by: RobertSubnet
4 Replies
6. Solaris
I've got a console that seems to be hung. all other services (ip, etc) work perfectly. in fact, its still in production... we just don't have console access. so i there are two consoles on this guy.. scfc0 and scfc1. using iompadm from fujitsu, this is what i got:
# ./iompadm -c FJSVscf3 info... (1 Reply)
Discussion started by: pupp
1 Replies
7. Solaris
i've decided to try out an x86 system with sol10. however, i can't get my 3com 3C905TX-B to work. i checked the hcl and it says it runs natively. anyone having similar issues or seen a fix for this? i'll be happy to supply more info. Note: i do not see this in /etc/path_to_inst. so it looks like... (1 Reply)
Discussion started by: pupp
1 Replies
8. Solaris
we have a solaris 10 box (V440)
we are looking for a way to set the stack size for all processes on the system.
we know we can use ulimit -s
$ ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited... (2 Replies)
Discussion started by: robsonde
2 Replies
9. UNIX for Advanced & Expert Users
I got the source tarbal from mysql.com of the latest version about 3.23.
When I compile it, I get some errors of assembler etc.
I start ./configure with these settings
CC=gcc CFLAGS="-O6" \
CXX=gcc CXXFLAGS="-O6 -felide-constructors -fno-exceptions -fno-rtti" \
./configure... (1 Reply)
Discussion started by: mrsaint
1 Replies
BUNDLE-CONFIG(1) BUNDLE-CONFIG(1)
NAME
bundle-config - Set bundler configuration options
SYNOPSIS
bundle config [name [value]]
DESCRIPTION
This command allows you to interact with bundler's configuration system. Bundler retrieves its configuration from the local application
(app/.bundle/config), environment variables, and the user's home directory (~/.bundle/config), in that order of priority.
Executing bundle config with no parameters will print a list of all bundler configuration for the current bundle, and where that configura-
tion was set.
Executing bundle config <name> will print the value of that configuration setting, and where it was set.
Executing bundle config <name> <value> will set that configuration to the value specified for all bundles executed as the current user. The
configuration will be stored in ~/.bundle/config.
BUILD OPTIONS
You can use bundle config to give bundler the flags to pass to the gem installer every time bundler tries to install a particular gem.
A very common example, the mysql gem, requires Snow Leopard users to pass configuration flags to gem install to specify where to find the
mysql_config executable.
gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config
Since the specific location of that executable can change from machine to machine, you can specify these flags on a per-machine basis.
bundle config build.mysql --with-mysql-config=/usr/local/mysql/bin/mysql_config
After running this command, every time bundler needs to install the mysql gem, it will pass along the flags you specified.
CONFIGURATION KEYS
Configuration keys in bundler have two forms: the canonical form and the environment variable form.
For instance, passing the --without flag to bundle install(1) bundle-install.1.html prevents Bundler from installing certain groups speci-
fied in the Gemfile(5). Bundler persists this value in app/.bundle/config so that calls to Bundler.setup do not try to find gems from the
Gemfile that you didn't install. Additionally, subsequent calls to bundle install(1) bundle-install.1.html remember this setting and skip
those groups.
The canonical form of this configuration is "without". To convert the canonical form to the environment variable form, capitalize it, and
prepend BUNDLE_. The environment variable form of "without" is BUNDLE_WITHOUT.
LIST OF AVAILABLE KEYS
The following is a list of all configuration keys and their purpose. You can learn more about their operation in bundle install(1) bun-
dle-install.1.html.
path (BUNDLE_PATH)
The location on disk to install gems. Defaults to $GEM_HOME in development and vendor/bundler when --deployment is used
frozen (BUNDLE_FROZEN)
Disallow changes to the Gemfile. Defaults to true when --deployment is used.
without (BUNDLE_WITHOUT)
A :-separated list of groups whose gems bundler should not install
bin (BUNDLE_BIN)
Install executables from gems in the bundle to the specified directory. Defaults to false.
gemfile (BUNDLE_GEMFILE)
The name of the file that bundler should use as the Gemfile. This location of this file also sets the root of the project, which is
used to resolve relative paths in the Gemfile, among other things. By default, bundler will search up from the current working
directory until it finds a Gemfile.
In general, you should set these settings per-application by using the applicable flag to the bundle install(1) bundle-install.1.html com-
mand.
You can set them globally either via environment variables or bundle config, whichever is preferable for your setup. If you use both, envi-
ronment variables will take preference over global settings.
June 2012 BUNDLE-CONFIG(1)