NFS for newbie

Hi all!
I have just bought a MacMini with OSX Server, and I started trying to configure NFS! However, nothing seems to work!
What did I do? I connected with the Server Admin app to my MacMini, and enabled NFS. When I connect to it with my iMac, Finder says that the server does not respond. This is what I find in Server Admin:
Under the server name I find "NFS", and clicking on the green light I can see:
NFS: Running
nfsd: Stopped
portmap: Stopped
rpc.lockd: Stopped
rpc.statd: Stopped
From my newbie point of view, I don't think it's a great thing that all services except NFS are stopped. Do I need to start them, and how? I don't see portmap in Settings > Services.
Anyway, under "File Sharing" in Server Admin app, I have a volume that I can "Unshare", so I think this is OK.
Can anyone explain me how to enable NFS? I thought it would be easier
Another probably silly question: can I enable only some users to connect to NFS?
Thanks & Cheers!!

Hi! I played around and I found that I needed to set up a mount point, and next explicitly enable NFS. Now it's all working! Of course, ACLs too!

Similar Messages

Which is better for newbies?

Which is better for newbies, Jgrasp or Netbeans? I need something that explains errors more thoroughly than Jgrasp.

Here's my code with 3 errors. Now bear in mind that my program has compiled completely and ran correctly up to this method. All I'm trying to do with this method is get the average of all grades in a multi-array. I researched and found some code that was similar to what I needed to do but it's not working out yet. All other methods in my program work perfectly but I can't get this one to compile.
public double getMean(int allGrades[][])
 int total = 0;
 for (int grade : allGrades)
 total += grade;
 System.out.println("Total is "+getMean(grades));
 return total/allGrades.length;
} // end class GradeBookGradebook.java:100: illegal start of type
 return total/allGrades.length;
 ^
Gradebook.java:100: <identifier> expected
 return total/allGrades.length;
 ^
Gradebook.java:100: <identifier> expected
 return total/allGrades.length;
 ^
3 errors

HELP ME GUYS WITH CREDIT ADVICE FOR NEWBIE

Thanks for reading! I just want to ask you guys, I'm looking to help my girlfriend open her first credit card. I have plenty with all of the creditors and I began with Capital One. I believe at that time I had my student loan reporting though. She has nothing on her report aside from a few inquiries (AT&T and a few store card HPs). She said some of her friends have been approved for a low CL Discover It card. I don't know if there is a Discover It offering for newbies or if they must just have something on their report. I recommended she get a Cap1 card. That way she can have her son on the card image and I know that since I've heard they triple pull they're pretty leanient. What do you guys think? Any advice on what secured card she should get should it come to that? Thanks very much again!

HappyCamper123 wrote:
Do NOT cosign for your girlfriend. If you break up, your finances could get messy.
Have her apply for an It card, they love clean, thin files. If that fails, go for a secured Boa card or Cap One credit steps. Maybe make her an AU on an Amex of yours to build history (you can artificially set a limit to limit your liability).Amex is the one I called first about AU and then Citi. I almost did it with Citi because surprisingly the rep for Amex wasn't very helpful. Should I (she) even be concerned with inquiries when she literally has no score anyway? Do they really impact a score that doesn't exist or do they hurt a score once one becomes available. The whole thing is I was just concerned that we'd apply for stuff and she woulnd't get approved and that she'd have another senseless inquiry. As I said, she already has several.

Online systems configured for newbies to experiment

Why does SDN not have online systems configured for newbies to experiment online.
Will this pose too much of an administrative task? with the skills available in this forum it should not be a problem.
or is it a question of making profit through the training academies which are not affordable to individuals not backed by their companies to learn on the technology?

An interesting thought, however with so many users we would need a server farm of test systems to handle it. And with users wanting to try so many different things it would be rather difficult to maintain the servers and have some sort of schedule for maintenance, resets, etc.

NFS for clustering

Hi
There two methods in using NFS for Oracle datafiles in RAC
1. creating ordinary datafiles in NFS shared path
2. creating zero filled files in NFS shared path and then using them as disk for ASM
My question is that which method is better in terms of performance for operational environment ?
thanks

TakhteJamshid wrote:
There two methods in using NFS for Oracle datafiles in RAC
1. creating ordinary datafiles in NFS shared path
2. creating zero filled files in NFS shared path and then using them as disk for ASM
My question is that which method is better in terms of performance for operational environment ?IMO, not using NFS at all.
The optimal and most performant architecture is the one with the minimal number of moving parts to achieve the desired result.
In the case of RAC, it means using ASM to manage the shared stored devices for you. It means that there should ideally be no unnecessary software layers between ASM and these shared storage devices. ASM should use the shared storage directly as block devices - and these block devices should be the LUNs visible via the multipath/powerpath driver software that "publishes" these (fibre channel/Infiniband/etc) storage LUNs for the o/s to use.
Throwing an IP layer and other s/w layers in between, affects both robustness and performance.

Using NFS for RAC

Hi I am planning to use NFS for RAc but I am not able to find the certified NAS devices.Where can I get the list
Thanks

NAS is NFS.
See
Following NFS storage vendors are supported: EMC, Fujitsu, HP, IBM, NetApp, Pillar Data, Sun, Hitachi.
NFS file servers do not require RAC certification. The NFS file server must be supported by the system and storage vendors.
Currently, only NFS protocol version 3 (NFSv3) is supported.
Hemant K Chitale

Tomcat Wiki: very important for newbies

Hi everyone!
I have a very important suggestion (important for newbies or ... me) for the tomcat wiki. To work with tomcat without problems you must have permissions on the configuration files. So i think the wiki must have something related to permissions and groups like
gpasswd -a <user> tomcat.
All the configuration files bundled with the tomcat package doesn't have the permissions for any user to read its content. The only easy way to have access to this files is adding your user to the tomcat group.
I hope this helps.
See ya!
PD: sorry if you notice my poor english.

Would that fix this mod_jk problem? Do you mean to say that I have those permissions when I actually edit those files?
I think the wiki is also mistaken assuming that JAVA_HOME is in the /opt directory.

HOWTO: Install Arch for Newbies

Hello,
Yesterday was my fist installation of Arch and i've found that the informations are not very well combined for a newbie/new to arch, am not newbie to linux but am new to arch so i've spend quite time to figure out some things or to know some links, due to this fact i've decided to write an easy guide that combine the whole installation from Downloading Till getting an up & running Arch with Gnome
the HOWTO can be found here please i need your opinions/corrections so we can make it as easy as installing ubuntu for newbies

Try my gdm.conf, it's an unchanged one, and normally it would work
# GDM Configuration file. You can use gdmsetup program to graphically
# edit this, or you can optionally just edit this file by hand. Note that
# gdmsetup does not tweak every option here, just the ones most users
# would care about. Rest is for special setups and distro specific
# tweaks. If you edit this file, you should send the HUP or USR1 signal to
# the daemon so that it restarts: (Assuming you have not changed PidFile)
# kill -USR1 `cat /var/run/gdm.pid`
# (HUP will make gdm restart immediately while USR1 will make gdm not kill
# existing sessions and will only restart gdm after all users log out)
# You can also use the gdm-restart and gdm-safe-restart scripts which just
# do the above for you.
# For full reference documentation see the gnome help browser under
# GNOME|System category. You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
# NOTE: Some of these are commented out but still show their default values.
# If you wish to change them you must remove the '#' from the beginning of
# the line. The commented out lines are lines where the default might
# change in the future, so set them one way or another if you feel
# strongly about it.
# Have fun! - George
[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=false
AutomaticLogin=
# Timed login, useful for kiosks. Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30
# The gdm configuration program that is run from the login screen, you should
# probably leave this alone
#Configurator=/opt/gnome/sbin/gdmsetup --disable-sound --disable-crash-dialog
# The chooser program. Must output the chosen host on stdout, probably you
# should leave this alone
#Chooser=/opt/gnome/libexec/gdmchooser
# The greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to
# get the new graphical greeter.
#Greeter=/opt/gnome/libexec/gdmlogin
# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
#RemoteGreeter=/opt/gnome/libexec/gdmlogin
# Launch the greeter with an additional list of colon seperated gtk
# modules. This is useful for enabling additional feature support
# e.g. gnome accessibility framework. Only "trusted" modules should
# be allowed to minimise security holes
#AddGtkModules=false
# By default these are the accessibility modules
#GtkModulesList=gail:atk-bridge:/opt/gnome/lib/gtk-2.0/modules/libdwellmouselistener:/opt/gnome/lib/gtk-2.0/modules/libkeymouselistener
# Default path to set. The profile scripts will likely override this
DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/bin
# Default path for root. The profile scripts will likely override this
RootPath=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/sbin:/opt/gnome/bin
# If you are having trouble with using a single server for a long time and
# want gdm to kill/restart the server, turn this on
#AlwaysRestartServer=false
# User and group used for running gdm GUI applicaitons. By default this
# is set to user gdm and group gdm. This user/group should have very
# limited permissions and access to ony the gdm directories and files.
User=nobody
Group=gdm
# To try to kill all clients started at greeter time or in the Init script.
# doesn't always work, only if those clients have a window of their own
#KillInitClients=true
LogDir=/var/log/gdm
# You should probably never change this value unless you have a weird setup
PidFile=/var/run/gdm.pid
# Note that a post login script is run before a PreSession script.
# It is run after the login is successful and before any setup is
# run on behalf of the user
PostLoginScriptDir=/opt/gnome/etc/gdm/PostLogin/
PreSessionScriptDir=/opt/gnome/etc/gdm/PreSession/
PostSessionScriptDir=/opt/gnome/etc/gdm/PostSession/
DisplayInitDir=/opt/gnome/etc/gdm/Init
# Distributions: If you have some script that runs an X server in say
# VGA mode, allowing a login, could you please send it to me?
#FailsafeXServer=
# if X keeps crashing on us we run this script. The default one does a bunch
# of cool stuff to figure out what to tell the user and such and can
# run an X configuration program.
XKeepsCrashing=/opt/gnome/etc/gdm/XKeepsCrashing
# Reboot, Halt and suspend commands, you can add different commands
# separated by a semicolon and gdm will use the first one it can find
RebootCommand=/sbin/shutdown -r now "Rebooted from gdm menu."
HaltCommand=/sbin/shutdown -h now "Halted from gdm menu."
SuspendCommand=/usr/bin/apm --suspend
# Probably should not touch the below this is the standard setup
ServAuthDir=/opt/gnome/var/gdm
# This is our standard startup script. A bit different from a normal
# X session, but it shares a lot of stuff with that. See the provided
# default for more information.
BaseXsession=/opt/gnome/etc/gdm/Xsession
# This is a directory where .desktop files describing the sessions live
# It is really a PATH style variable since 2.4.4.2 to allow actual
# interoperability with KDM. Note that <sysconfdir>/dm/Sessions is there
# for backwards compatibility reasons with 2.4.4.x
SessionDesktopDir=/etc/X11/sessions/:/etc/dm/Sessions/:/usr/share/xsessions/:/opt/gnome/share/gdm/BuiltInSessions/:/opt/gnome/share/xsessions/
# This is the default .desktop session. One of the ones in SessionDesktopDir
#DefaultSession=gnome.desktop
# Better leave this blank and HOME will be used. You can use syntax ~/ below
# to indicate home directory of the user. You can also set this to something
# like /tmp if you don't want the authorizations to be in home directories.
# This is useful if you have NFS mounted home directories. Note that if this
# is the home directory the UserAuthFBDir will still be used in case the home
# directory is NFS, see security/NeverPlaceCookiesOnNFS to override this behaviour.
UserAuthDir=
# Fallback if home directory not writable
UserAuthFBDir=/tmp
UserAuthFile=.Xauthority
# The X server to use if we can't figure out what else to run.
StandardXServer=/usr/X11R6/bin/X
# The maximum number of flexible X servers to run.
#FlexibleXServers=5
# And after how many minutes should we reap the flexible server if there is
# no activity and no one logged on. Set to 0 to turn off the reaping.
# Does not affect Xnest flexiservers.
#FlexiReapDelayMinutes=5
# the X nest command
Xnest=/usr/X11R6/bin/Xnest -audit 0 -name Xnest
# Automatic VT allocation. Right now only works on Linux. This way
# we force X to use specific vts. turn VTAllocation to false if this
# is causing problems.
FirstVT=7
VTAllocation=true
# Should double login be treated with a warning (and possibility to change
# vts on linux and freebsd systems for console logins)
#DoubleLoginWarning=true
# Should a second login always resume the current session and
# switch vts on linux and freebsd systems for console logins
#AlwaysLoginCurrentSession=true
# If true then the last login information is printed to the user before
# being prompted for password. While this gives away some info on what
# users are on a system, it on the other hand should give the user an
# idea of when they logged in and if it doesn't seem kosher to them,
# they can just abort the login and contact the sysadmin (avoids running
# malicious startup scripts)
#DisplayLastLogin=false
# Program used to play sounds. Should not require any 'daemon' or anything
# like that as it will be run when no one is logged in yet.
#SoundProgram=/usr/bin/play
# These are the languages that the console cannot handle because of font
# issues. Here we mean the text console, not X. This is only used
# when there are errors to report and we cannot start X.
# This is the default:
#ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh
# This determines whether gdm will honor requests DYNAMIC requests from
# the gdmdynamic command.
#DynamicXServers=false
# This determines whether gdm will send notifications to the console
#ConsoleNotify=true
[security]
# If any distributions ship with this one off, they should be shot
# this is only local, so it's only for say kiosk use, when you
# want to minimize possibility of breakin
AllowRoot=false
# If you want to be paranoid, turn this one off
AllowRemoteRoot=false
# This will allow remote timed login
AllowRemoteAutoLogin=false
# 0 is the most restrictive, 1 allows group write permissions, 2 allows all
# write permissions
RelaxPermissions=0
# Check if directories are owned by logon user. Set to false, if you have, for
# example, home directories owned by some other user.
CheckDirOwner=true
# Number of seconds to wait after a bad login
#RetryDelay=1
# Maximum size of a file we wish to read. This makes it hard for a user to DoS
# us by using a large file.
#UserMaxFile=65536
# If true this will basically append -nolisten tcp to every X command line,
# a good default to have (why is this a "negative" setting? because if
# it is false, you could still not allow it by setting command line of
# any particular server). It's probably better to ship with this on
# since most users will not need this and it's more of a security risk
# then anything else.
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
DisallowTCP=true
# By default never place cookies if we "detect" NFS. We detect NFS
# by detecting "root-squashing". It seems bad practice to place
# cookies on things that go over the network by default and thus we
# don't do it by default. Sometimes you can however use safe remote
# filesystems where this is OK and you may want to have the cookie in your
# home directory.
#NeverPlaceCookiesOnNFS=true
# XDMCP is the protocol that allows remote login. If you want to log into
# gdm remotely (I'd never turn this on on open network, use ssh for such
# remote usage that). You can then run X with -query <thishost> to log in,
# or -indirect <thishost> to run a chooser. Look for the 'Terminal' server
# type at the bottom of this config file.
[xdmcp]
# Distributions: Ship with this off. It is never a safe thing to leave
# out on the net. Setting up /etc/hosts.allow and /etc/hosts.deny to only
# allow local access is another alternative but not the safest.
# Firewalling port 177 is the safest if you wish to have xdmcp on.
# Read the manual for more notes on the security of XDMCP.
Enable=false
# Honour indirect queries, we run a chooser for these, and then redirect
# the user to the chosen host. Otherwise we just log the user in locally.
#HonorIndirect=true
# Maximum pending requests
#MaxPending=4
#MaxPendingIndirect=4
# Maximum open XDMCP sessions at any point in time
#MaxSessions=16
# Maximum wait times
#MaxWait=15
#MaxWaitIndirect=15
# How many times can a person log in from a single host. Usually better to
# keep low to fend off DoS attacks by running many logins from a single
# host. This is now set at 2 since if the server crashes then gdm doesn't
# know for some time and wouldn't allow another session.
#DisplaysPerHost=2
# The number of seconds after which a non-responsive session is logged off.
# Better keep this low.
#PingIntervalSeconds=15
# The port. 177 is the standard port so better keep it that way
#Port=177
# Willing script, none is shipped and by default we'll send
# hostname system id. But if you supply something here, the
# output of this script will be sent as status of this host so that
# the chooser can display it. You could for example send load,
# or mail details for some user, or some such.
Willing=/opt/gnome/etc/gdm/Xwilling
[gui]
# The specific gtkrc file we use. It should be the full path to the gtkrc
# that we need. Unless you need a specific gtkrc that doesn't correspond to
# a specific theme, then just use the GtkTheme key
#GtkRC=/opt/gnome/share/themes/Default/gtk-2.0/gtkrc
# The GTK+ theme to use for the gui
#GtkTheme=Default
# If to allow changing the GTK+ (widget) theme from the greeter. Currently
# this only affects the standard greeter as the graphical greeter does
# not yet have this ability
#AllowGtkThemeChange=true
# Comma separated list of themes to allow. These must be the names of the
# themes installed in the standard locations for gtk themes. You can
# also specify 'all' to allow all installed themes. These should be just
# the basenames of the themes such as 'Thinice' or 'LowContrast'.
#GtkThemesToAllow=all
# Maximum size of an icon, larger icons are scaled down
#MaxIconWidth=128
#MaxIconHeight=128
[greeter]
# Greeter has a nice title bar that the user can move
#TitleBar=true
# Configuration is available from the system menu of the greeter
#ConfigAvailable=true
# Face browser is enabled. This only works currently for the
# standard greeter as it is not yet enabled in the graphical greeter.
Browser=false
# The default picture in the browser
#DefaultFace=/opt/gnome/share/pixmaps/nobody.png
# User ID's less than the MinimalUID value will not be included in the
# face browser or in the gdmselection list for Automatic/Timed login.
# They will not be displayed regardless of the settings for
# Include and Exclude.
MinimalUID=1000
# Users listed in Include will be included in the face browser and in
# the gdmsetup selection list for Automatic/Timed login. Users
# should be separated by commas.
#Include=
# Users listed in Exclude are excluded from the face browser and from
# the gdmsetup selection list for Automatic/Timed login. Excluded
# users will still be able to log in, but will have to type their
# username. Users should be separated by commas.
Exclude=bin,daemon,mail,nobody
# By default, an empty include list means display no users. By setting
# IncludeAll to true, the password file will be scanned and all users
# will be displayed except users excluded via the Exclude setting and
# user ID's less than MinimalUID. Scanning the password file can be
# slow on systems with large numbers of users and this feature should
# not be used in such environments. The setting of IncludeAll does
# nothing if Include is set to a non-empty value.
#IncludeAll=false
# If user or user.png exists in this dir it will be used as his picture
#GlobalFaceDir=/opt/gnome/share/pixmaps/faces/
# File which contains the locale we show to the user. Likely you want to use
# the one shipped with gdm and edit it. It is not a standard locale.alias file,
# although gdm will be able to read a standard locale.alias file as well.
#LocaleFile=/opt/gnome/etc/gdm/locale.alias
# Logo shown in the standard greeter
#Logo=/opt/gnome/share/pixmaps/gdm-foot-logo.png
# The standard greeter should shake if a user entered the wrong username or
# password. Kind of cool looking
#Quiver=true
# The Actions menu (formerly system menu) is shown in the greeter, this is the
# menu that contains reboot, shutdown, suspend, config and chooser. None of
# these is available if this is off. They can be turned off individually
# however
SystemMenu=true
# Should the chooser button be shown. If this is shown, GDM can drop into
# chooser mode which will run the xdmcp chooser locally and allow the user
# to connect to some remote host. Local XDMCP does not need to be enabled
# however
#ChooserButton=true
# Welcome is for all console logins and RemoteWelcome is for remote logins
# (through XDMCP).
# DefaultWelcome and DefaultRemoteWelcome set the string for Welcome
# to "Welcome" and for DefaultWelcome to "Welcome to %n", and properly
# translate the message to the appropriate language. Note that %n gets
# translated to the hostname of the machine. These default values can
# be overridden by setting DefaultWelcome and/or DefaultRemoteWelcome to
# false, and setting the Welcome and DefaultWelcome values as desired.
# Just make sure the strings are in utf-8 Note to distributors, if you
# wish to have a different Welcome string and wish to have this
# translated you can have entries such as "Welcome[cs]=Vitejte na %n".
DefaultWelcome=true
DefaultRemoteWelcome=true
#Welcome=Welcome
#RemoteWelcome=Welcome to %n
# Don't allow user to move the standard greeter window. Only makes sense
# if TitleBar is on
#LockPosition=false
# Set a position rather then just centering the window. If you enter
# negative values for the position it is taken as an offset from the
# right or bottom edge.
#SetPosition=false
#PositionX=0
#PositionY=0
# Xinerama screen we use to display the greeter on. Not for true
# multihead, currently only works for Xinerama.
#XineramaScreen=0
# Background settings for the standard greeter:
# Type can be 0=None, 1=Image, 2=Color
#BackgroundType=2
#BackgroundImage=
#BackgroundScaleToFit=true
#BackgroundColor=#76848F
# XDMCP session should only get a color, this is the sanest setting since
# you don't want to take up too much bandwidth
#BackgroundRemoteOnlyColor=true
# Program to run to draw the background in the standard greeter. Perhaps
# something like an xscreensaver hack or some such.
#BackgroundProgram=
# if this is true then the background program is run always, otherwise
# it is only run when the BackgroundType is 0 (None)
#RunBackgroundProgramAlways=false
# Show the Failsafe sessions. These are much MUCH nicer (focus for xterm for
# example) and more failsafe then those supplied by scripts so distros should
# use this rather then just running an xterm from a script.
#ShowGnomeFailsafeSession=true
#ShowXtermFailsafeSession=true
# Normally there is a session type called 'Last' that is shown which refers to
# the last session the user used. If off, we will be in 'switchdesk' mode where
# the session saving stuff is disabled in GDM
#ShowLastSession=true
# Always use 24 hour clock no matter what the locale.
#Use24Clock=false
# Use circles in the password field. Looks kind of cool actually,
# but only works with certain fonts.
#UseCirclesInEntry=false
# Do not show any visible feedback in the password field. This is standard
# for instance in console, xdm and ssh.
#UseInvisibleInEntry=false
# These two keys are for the new greeter. Circles is the standard
# shipped theme. If you want gdm to select a random theme from a list
# then provide a list that is delimited by /: to the GraphicalThemes key and
# set GraphicalThemeRand to true. Otherwise use GraphicalTheme and specify
# just one theme.
#GraphicalTheme=circles
#GraphicalThemes=circles/:happygnome
GraphicalThemeDir=/opt/gnome/share/gdm/themes/
GraphicalThemeRand=false
# If InfoMsgFile points to a file, the greeter will display the contents of the
# file in a modal dialog box before the user is allowed to log in.
#InfoMsgFile=
# If InfoMsgFile is present then InfoMsgFont can be used to specify the font
# to be used when displaying the contents of the file.
#InfoMsgFont=Sans 24
# If SoundOnLogin is true, then the greeter will beep when login is ready
# for user input. If SoundOnLogin is a file and the greeter finds the
# 'play' executable (see daemon/SoundProgram) it will play that file
# instead of just beeping
#SoundOnLogin=true
#SoundOnLoginFile=
# If SoundOnLoginSuccess, then the greeter will play a sound (as above)
# when a user successfully logs in
#SoundOnLoginSuccess=false
#SoundOnLoginSuccessFile=
# If SoundOnLoginFailure, then the greeter will play a sound (as above)
# when a user fails to log in
#SoundOnLoginFailure=false
#SoundOnLoginFailureFile=
# The chooser is what's displayed when a user wants an indirect XDMCP
# session, or selects Run XDMCP chooser from the system menu
[chooser]
# Default image for hosts
#DefaultHostImg=/opt/gnome/share/pixmaps/nohost.png
# Directory with host images, they are named by the hosts: host or host.png
HostImageDir=/opt/gnome/share/hosts/
# Time we scan for hosts (well only the time we tell the user we are
# scanning actually, we continue to listen even after this has
# expired)
#ScanTime=4
# A comma separated lists of hosts to automatically add (if they answer to
# a query of course). You can use this to reach hosts that broadcast cannot
# reach.
Hosts=
# Broadcast a query to get all hosts on the current network that answer
Broadcast=true
# Set it to true if you want to send a multicast query to hosts.
Multicast=false
# It is an IPv6 multicast address.It is hardcoded here and will be replaced when
# officially registered xdmcp multicast address of TBD will be available
#Multicast_Addr=ff02::1
# Allow adding random hosts to the list by typing in their names
#AllowAdd=true
[debug]
# This will enable debugging into the syslog, usually not neccessary
# and it creates a LOT of spew of random stuff to the syslog. However it
# can be useful in determining when something is going very wrong.
Enable=false
[servers]
# These are the standard servers. You can add as many you want here
# and they will always be started. Each line must start with a unique
# number and that will be the display number of that server. Usually just
# the 0 server is used.
0=Standard
#1=Standard
# Note the VTAllocation and FirstVT keys on linux and freebsd.
# Don't add any vt<number> arguments if VTAllocation is on, and set FirstVT to
# be the first vt available that your gettys don't grab (gettys are usually
# dumb and grab even a vt that has already been taken). Using 7 will work
# pretty much for all linux distributions. VTAllocation is not currently
# implemented on anything but linux and freebsd. Feel free to send patches.
# X servers will just not get any extra arguments then.
# If you want to run an X terminal you could add an X server such as this
#0=Terminal -query serverhostname
# or for a chooser (optionally serverhostname could be localhost)
#0=Terminal -indirect serverhostname
# If you wish to run the XDMCP chooser on the local display use the following
# line
#0=Chooser
## Note:
# is your X server not listening to TCP requests? Perhaps you should look
# at the security/DisallowTCP setting!
# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X -audit 0
flexible=true
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Terminal]
name=Terminal server
# Add -terminate to make things behave more nicely
command=/usr/X11R6/bin/X -audit 0 -terminate
# Make this not appear in the flexible servers (we need extra params
# anyway, and terminate would be bad for xdmcp choosing). You can
# make a terminal server flexible, but not with an indirect query.
# If you need flexible indirect query server, then you must get rid
# of the -terminate and the only way to kill the flexible server will
# then be by Ctrl-Alt-Backspace
flexible=false
# Not local, we do not handle the logins for this X server
handled=false
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Chooser]
name=Chooser server
command=/usr/X11R6/bin/X -audit 0
# Make this not appear in the flexible servers for now, but if you
# wish to allow a chooser server then make this true. This is the
# only way to make a flexible chooser server that behaves nicely.
flexible=false
# Run the chooser instead of the greeter. When the user chooses a
# machine they will get this same server but run with
# "-terminate -query hostname"
chooser=true

Help needed for newbie EJB

Hi, all
I am a newbie in EJB and I am following the example in the URL:
http://www.huihoo.com/jboss/online_manual/3.0/
I am working on the 'interest' example in the first chapter.
When it come to 'Packaging and deploying the bean', I got some meaage like this:
ant intro-interest-jar
Buildfile: build.xml
validate-servlet:
validate-jboss:
fail_if_not_valid:
init:
[echo] Using JBoss directory=/opt/jboss
[echo] Using base classpath=/opt/jboss/client/jboss-j2ee.jar:/opt/jboss/client/jaas.jar:/opt/jboss/client/jbosssx-client.jar:/opt/jboss/client/jboss-client.jar:/opt/jboss/client/jnp-client.jar:/home/xiaobo/learningejb/examples/COULD_NOT_FIND_SERVLET_JAR
[echo] Using Source directory=/home/xiaobo/learningejb/examples
[echo] Using Build directory=/home/xiaobo/learningejb/examples/build-examples
intro-interest-jar:
compile:
ejb-jar:
[delete] Deleting directory /home/xiaobo/learningejb/examples/build-examples/interest/META-INF
[mkdir] Created dir: /home/xiaobo/learningejb/examples/build-examples/interest/META-INF
[copy] Copying 1 file to /home/xiaobo/learningejb/examples/build-examples/interest/META-INF
[copy] Copying 1 file to /home/xiaobo/learningejb/examples/build-examples/interest/META-INF
[jar] Building jar: /home/xiaobo/learningejb/examples/build-examples/interest/interest.jar
BUILD SUCCESSFUL
Total time: 2 seconds
Why did I get this:
/home/xiaobo/learningejb/examples/COULD_NOT_FIND_SERVLET_JAR.
But if I check the "interest.jar" by using 'jar -tvf interest.jar' in the "~/learningejb/examples/build-examples/interest$" directory, it seems it had all files and directories in it.
But if I copy this jar file into the deploy directory in jboss, and I check the log file 'server.log'
I found this error message:
2005-11-28 17:31:03,536 DEBUG [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification: javax.management.Notification[source=jboss.ejb:service=EJBDeployer,type=org.jboss.deployment.SubDeployer.stop,sequenceNumber=15,timeStamp=1133213463536,message=null,userData=org.jboss.deployment.DeploymentInfo@c36a9f52 { url=file:/opt/jboss-3.2.5/server/default/deploy/interest.jar }
deployer: org.jboss.ejb.EJBDeployer@3c9c31
status: Deployment FAILED reason: ejb-jar.xml must define a valid DOCTYPE!
state: FAILED
watch: file:/opt/jboss-3.2.5/server/default/deploy/interest.jar
lastDeployed: 1133210324921
lastModified: 1133210324000
mbeans:
Then I add the follwoing line into the 'ejb-jar.xml':
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
so the 'ejb-jar.xml' looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<description>JBoss Interest Sample Application</description>
<display-name>Interest EJB</display-name>
<enterprise-beans>
<session>
<ejb-name>Interest</ejb-name>
<home>org.jboss.docs.interest.InterestHome</home>
<remote>org.jboss.docs.interest.Interest</remote>
<ejb-class>org.jboss.docs.interest.InterestBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
and I rejar it and copy the jar file into the deploy directory. I still got the same error message in the log file???!!!
Please help!
X.Chen

It's a no brainer between the AirPort Extreme and Airport Express.
The AirPort Extreme has 6 wireless antennas up at the top of the "tower", while the AirPort Express has four, so the Extreme has significantly better wireless speed and range than the Express.
As you know, the broadcast power of wireless routers is limited by law, and most routers are running full blast. Apple routers are not known for their broadcast power, so what we cannot tell you is whether the Extreme will outperform the existing wireless router that you already have in terms of range.
Also as you know, the speed of your Internet connection is limited to the plan that you have with Verizon. An Apple router cannot take the speed of Internet connection that it receives from your Verizon plan and make it go any faster.
A user who has both the same Verizon router as you and an AirPort Extreme might be able to tell you how the products compare in his home.
But...and this is a big BUT...... the bottom line with any wireless router is that you will not know how well it performs in your home until you try it out in your home. To think otherwise would be foolhardy at best.
Buy from Apple and you have a 14 day return privilege in case things don't work as well as hoped. Other stores may offer a similar option. Check first, before you buy.

Live CD for newbies and dial up users

From comments I am receiving abut the usage of AL-AMLUG Live CD, it helps newbies to install the native Arch Linux in HDD. Without any "headage" it does all the major configures (X, sound, network, and LILO) for you. The "hd-install" includes Hwd (hardware detect) and net-install with DHCP & ADSL setup.
Does sounds good for a newbie? Anything good also include a "but...". Disadvantage with hd-install, in my opinion, you will miss the learning of Arch Linux's configure system what you may need for post configure of new hardwares and programs..... sooner or later you have to become an Archer
The live CD is also for the "dial up users" with 56k modems, when the packages in Arch Linux's latest installer CD getting outdated. Example, AL 0.5 was released July 21, 2003. The current live CD 0.4.2 with the base, KDE and common packages updated on February 12, 2004.
http://amlug.net/new-projects/live-cd/p … list-0.4.2
GNOME users may not be happy. For your information, there is still 280MB space on the live CD for more packages. Total space: 1.3GB (compressed to 700MB).
AL-AMLUG Live CD project page:
http://amlug.net/new-projects/live-cd/a … ve-cd.html

beniro,
after week of not even touching this thread i still have to say that i fail to see what is derogatory in my comments. derrogatory is where you put down something for the sake of putting something down. i hardly ever do something like that. i may be blunt but hardly ever derrogatory.
look in the mirror? i have done that alot i have looked in the mirror i have tried to understand the way some people came to the conclusioned they did about me. perhaps i a m blind or stupid but when have i ever not tried to get something positive for the community? when i look in that mirro i see someone who put alot of time and effort into helping the community with problems. i see somebody that where ever they have gone always express what they feel despite what blowback may happen. i don't believe in bottling things up. in the end though all people see is the negative.
nifan,
there are lots of ways to help a friend out installling any distro. but in the end if you don't know the guts then expect things to go bad at some point. linux is not designed for someone who just wants the computer to do everything. indeed if linux were like that then there would be a whole host of security risks presented.
as for me slamming arch. well if you didn't notice i having only been too willing to always air out arch's dirty laundry. i have been harping on the documentation and so have many others. should those others move on too while the developers/community continue to bury their heads in the sand and feel they can keep marching on? if somebody didn't do who would and where would arch be then?
i am here EVERYDAY. EVERYDAY since i joined this forum. i have asked and answered questions, i contributed on the irc channel, i worked for the distro everyday for almiost a year. i know what was going what went on. i still point out some thigns to aid the developers. in the end my view of kiss never really strayed from the documented version of arch's kiss statement and i felt arch had and was continuing to. there were just too many small things that bothered me and i decided to use another distro.
now that i have moved on though i needed something to keep my desire to help occupied and crux does not have a forum nor can i help out that much on irc because it is distro mainly used by europeans and our clock are just not synced. i still know arch fiarly well and actually crux is very similar so why not help. i have nothing against the community.
why do i get bitter then. well to beat dead horse. i try to help or try to voice an opinion and the response i commonly get back a tirade against my person. now it is at the point now where some people do not or refuse to see any constructive or helpful posts i make here. take al ook at rasat he is someone who has been the victim of many a criticism from me and he never once made any insults towards me nor did he ever not put the blinders on to what i was saying. after nearly a year of taking the odd jab from me he still knows exactly why make the comments towards his projects i do.
in the end i don't really care what he does as his work does bring people to the arch community. i just try and make sure that he can design his projects in such a way as to not create a pile of mindless users that need their hand held through everything. from what i remember of early versions of hwd for example he made it still a very hands on approach for the user. ultimately that is what i wanted him to hear and he did.
if you don't think that the system taking control of your work environment is a burden on the community take a look at just how much help we need to give here and on the mail list. if people had come from a more hands on environment they would rarely have to use irc, forums or mail lists. linux is hard to get used to because it is desigened to be hands on sytem and anyone who does not want this should really not be using it. thats mean but true. with ease comes security risks.
belive me i am lazy i came from the least hands on distro before arch and i would NEVER go back to distro not like arch or crux or ... i have learned alot and there is very few issues i cannot figure out. arch's kiss approach taught me alot and crux has brought me back to it.
in the end i am here to help and if you doubt that then well you just should not bother with any of my posts because i WILL piss you off eventually whether i am trying to or not.

General place for newbie datamodeler questions?

With the production release of SQL Developer Data Modeler I'd assume that this forum will draw a bunch of new users. Is there a better place to ask some pretty simple, newbie like questions that won't bother the more seasoned members?
For instance, I am working in a Rails environment, which has some stringent naming conventions, one of which is that all of the primary key columns are numeric and called "id", with the foreign key linked columns called <table_name>_id. When engineering a logical model to a relational model, the added foreign key columns are all "id#". Is there a way I can define a naming rule to keep me from having to redo the relation column names?
Also, we have a standard set of columns (mostly Rails related) which appear in every table. Can I define a generation rule which automatically includes these tables?
Thanks

Thank you. I will try changing that setting.
IS there a setting which tells the relational model to automatically create pk and fk indexes? I haven't seen one, and manually setting them up is a tedious task. --sw

NFS for portable home directories not working

I just recently tried to move our PHD's over to NFS instead of AFP to allow for fast user switching and some other reasons.
However it doesn't work at all... The automount seems to work fine, as I can browse to /Network/Servers/servername/Users/ fine, but when the user tries to sync, a dialog pops up:
The sync could not complete because your network home at "nfs://servername/Users" is currently unavailable.
Try again later when it is available.
and then in the console it shows:
com.apple.SystemUIServer.agent[14236] mount_nfs: /Volumes/Users: Operation not permitted
HomeSync[14369] HomeSync.syncNow: Unable to mount server URL at 'nfs://servername/Users', status = 65.
com.apple.SystemUIServer.agent[14236] HomeSync[14369:903] HomeSync.syncNow: Unable to mount server URL at 'nfs://servername/Users', status = 65.
It seems like its trying to mount it at /Volumes/Users, but it can't (because a normal user can't mount nfs volumes?(..as far as i know))...and furthermore I don't know why it needs to mount it at /Volumes/Users when it's already automounted at /Network/Servers/servername/Users

I just managed to get my first sync to work.
My server exports /opt/home/<user> but not /opt/home since each user has a separate lvm volume. What worked was the following:
dscl . -delete /Users/<user> dsAttrTypeStandard:OriginalHomeDirectory
dscl . -append /Users/<user> dsAttrTypeStandard:OriginalHomeDirectory "<homedir><url>nfs://find/opt/home/<user></url><path></path></homedir>"
This is similar to what I saw on http://managingosx.wordpress.com/2009/02/19/leopard-mobileaccounts-and-nfs-homes / except putting the users name (in place of <user> as part of the url instead of part of the path.
The value for dsAttrTypeStandard:OriginalHomeDirectory was formerly /Network/Servers/<server>/opt/home/<user> which is a perfectly good directory, but not a url. I don't know why it wouldn't use the directory and manufactured a url instead.
By changing the value back to default and making my server export /opt/home, I'm still able to sync. Naturally I like this solution much better.
Doesn't seem like this solution will help you much if a given user can sync on some machines and not others, unless maybe you have different export rules to different machines in your network.

Host String for Newbie

I'm trying (in vain) to start sql*plus but am failing on the Host String: parm.
I know my instance is up because oem, auqa-studio and jdbc all operate a-okay.
Where do you suppose Oracle keeps its' documentation on this cryptic parm? Certainly this "host string" must have a format. I've tried every format I can think of.
Getting ORA-12560 and ORA-12170.
I believe the format is something like 123.66.7.99:1521/ORCL
Hate to call Oracle support for such a newbie problem.
Thanx in advance.

123.66.7.99:1521/ORCLWhich version are you on ? That syntax (easy connect naming method) works on 10g only.
Where do you suppose Oracle keeps its' documentation on this cryptic parm? See http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14196/network.htm#sthref173
Try using Net Configuration Assistant (netca on Unix/Linux) to configure your connect string.

Solution other than nfs for centralized baskup location on Unix?

Good afternoon,
I am trying to setup RMAN and am currently in discussions with our Unix team. They have expressed a certain uneasiness in using NFS mounts on multiple machines to achieve the same results as creating a share on W2K. Is there an alternative to using NFS that will accomplish the same results?
Thanks for any help/advice you can give me.
Sebastian DiFelice

Q: An alternative to NFS ?
A: That would be Samba / CIFS.
Really though you need to ask the Unix team why they object to NFS ie: is this a throughput / network traffic problem or something else?
If you're planning to centralise your backup solution through an existing network you'll run into this problem all the time.

For Newbie To Check First

For MacBook Newbie that required answers, check this link first, for it is provide well manage information and most up to date trouble shooting for MacBook.
http://www.apple.com/support/macbook/
I, myself still find something usefull here and there for the link provided there.
Enjoy and Good Luck.

BigDaddyLoveHandles wrote:
sabre150 wrote:
for(Person person : listPersons.clone()){
What if listPersons is of type List<Person> (and that's a good thing!) -- then clone isn't public. Yep - but one can use the List.toArray( new Person[0]) then instead.
And that use of clone is a hack anyhowdy, as you well know.Not a hack at all.
>
Solution: if you want to iterate and remove, you need to be a mensch and use the iterator explicitly:
for(Iterator<Person> i = persons.iterator(); i.hasNext(); ) {
Person person = i.next();
if (... some condition ...) {
i.remove();
}Easy!Not all Iterator allow remove() since it is an "optional operation".

NFS for newbie

Similar Messages

Maybe you are looking for