Sun Managers,
Thanks go to all who replied to my question regarding changing the
Solaris 2.4 vold process's root directory since the /vol path conflicted
with one of my automounter paths.
Solutions:
The root directory that vold uses could be changed under Solaris 2.3,
but Sun took this ability away in Solaris 2.4, but will put it back in Solaris
2.5. So current options are:
(1) Don't use vold until Solaris 2.5 or patch for 2.4 comes out
(2) Wait for Solaris 2.5
(3) Wait for Solaris 2.4 patch for vold (if one is ever made available)
(4) Change automount maps to use something other than /vol for volume
mounting.
(5) Use Solaris 2.3
I will use option 1 above for now until option 2 or 3 are available.
My original post:
>
> Sun Managers,
>
> I have just installed my first Solaris 2.X system (SS20 running
> Solaris 2.4). We have been using /vol as one of our automount points to
> do volume mounting of NFS filesystems on our SunOS systems. However,
> the vold process in Solaris 2.4 wants to use /vol for it's root directory.
>
> Is there a way that I can change this to /vold or some other path?
> The manpages and answerbook say that /vol is the default root path, but I
> can't find any reference that tells me how to change the default to
> something else.
>
> At this point, my workaround is to turn off vold. But long term,
> I'd like to be able to use vold still. And I don't want to have to change
> my automount maps to use a new path.
>
> Any suggestions? I'll summarize.
>
> Thanks...Tom
Replies from Sun Managers:
>From allan@stewpot.home.networx.com Fri Mar 17 06:20:56 1995
>
> Under 2.3 there is an option to change the directory that vold uses,
> it works kinda.. I had the same problem you have, was using /vol for
> our automount directories.. Finally gave up and used /base (I wanted
> to use /v but was out voted).
>
> My complete solution was to add to the auto.master file
>
> /base auto.vol
>
> So that on all platforms other than Solaris it dupped the /vol
> directories under /base. And on Solaris machines there is a
> auto_master file with out a reference to /vol..
>
> --
> ----------------------------------------------------------------------
> Gopher Stew | allan@eskimo.com
> The Rodent King | allan@stewpot.home.networx.com
> | stewart@networx.com
> \|/ |
> oOo <--- {his paw mark and Royal Seal} |
>From blenherr@analytics.abb.com Fri Mar 17 07:19:09 1995
>
> Tom,
> Under 2.3 you used to be able to use the -d option to vold to specify an
> alternat mount point. But.....out of the kindness of their heart.....Sun
> took that option off in 2.4. I currently have vold disabled and a RFE
> logged with Sun via our maintenance provider. They claim it will be fixed
> in 2.5 (Solaris 96)
>
> Sorry I don't have better news. If you find a work around, let me know.
>
> Bill
>
> ***************************************************
>
> AAA BBB BBB Bill Lenherr
> A A B B B B CAD Analyst
> AAAAA BBBB BBBB blenherr@analytics.abb.com
> A A B B B B Phone 1-304-647-4358
> A A BBBB BBBB Fax 1-304-647-3697
>
> Asea Brown Boveri - Process Analytics
> 843 North Jefferson Street
> Lewisburg, West Virginia 24901
>
> ***************************************************
>From victor@estwmg.wm.estec.esa.nl Fri Mar 17 08:52:16 1995
>
> We do the same automount-y stuff with /vol and I got
> around it with :
>
> o kill vold with "/etc/init.d/volmgt stop"
> o mkdir /volalt (for example)
> o modify volmgt to use /usr/sbin/vold -d /volalt ...
>
> and the volume manager starts to use /volalt for its stuff.
>
> Mind you, I can't get volume managed CDs or Floppies to unmount or
> eject properly. I probably need to hack around with /etc/vold.conf or
> something.
>
> I hope that helps,
>
> Victor Fieldhouse (Computer Resources International)
> ------------------------------------------------------------------------------
> WM System Administrator, Tel. : +31 1719 83882 (fax 85420)
> European Space Agency, I'net : victor@wm.estec.esa.nl
> ESA/ESTEC, Keplerlaan 1, DECnet: 29729::VFIELDHO
> 2201 AZ Noordwijk, The Netherlands BITNET: VFIELDHO@ESTEC
>From @uu4.psi.com:hermes!atmel.com!sozoa Fri Mar 17 09:18:16 1995
>
> I haven't tried this, but vold is controlled by /etc/vold.conf. I just
> checked mine (Solaris 2.3), and found some paths starting with /vol*. You
> might try changing that to /vold* (be sure to create that directory) and see
> what happens.
>
> Steve Ozoa
> CAD System Administrator 408-436-4292
> ATMEL Corporation fax 408-436-4200
> sozoa@atmel.com pager 408-233-5966
>From karen.lythgoe@sfwmd.gov Fri Mar 17 12:10:25 1995
>
> Tom,
>
> If it helps any you are not alone. We heavily rely on /vol for mail and
> major applications at our site and encountered problems when we first
> installed 2.3 last year. Under 2.3 you could specify an alternate root
> directory with the -d option when starting up vold. We did this and then
> modified vold.conf to reflect /vol_mnt instead of /vol. This made volume
> manager fairly functional and yet didn't hose up our automounted filesystems.
> Unfortunately the -d option appears to be missing from 2.4 (maybe Sun thought
> they would fix vold?).
>
> I look forward to your summary, but if we stumble across a workaround I will
> forward it to you. We have reported the problem to Sun but they have not
> been helpful so far.
>
> --Karen
>
> /\_/\
> ( 0'0 )
> > (_) <
> ==========================ooO=====Ooo===================================
> Karen Lythgoe
> UNIX System Administrator
> South Florida Water Management District
> Phone: (407) 687-6520
> Fax: (406) 687-6442
> Email: karen@sfwmd.gov
>From ratnerj@gcm.com Fri Mar 17 13:04:55 1995
>
> Hi,
> Sorry, can't be done. I quote from a Sun source who answered
> this question for me some time ago:
>
> "In Solaris 2.3 we supported an option to vold to use an alternate
> root, but it was flawed, in that such utility commands as "eject"
> wouldn't work unless you remembered to pass an option for where the
> new root was upon each invocation.
>
> "So, in Solaris 2.4, we removed this ability all together (for right or
> wrong). In Solaris 2.5 it's back, but it's done correctly, in that,
> once you start vold with the alternate root, then all of the other
> auxiliary commands work correctly (without even having to remember
> where the alternate root is!). To handle not knowing where the root
> may be, the libvolmgt routine volmgt_root() (which has always existed)
> can be used to tell you where it is (and this routine return "/vol" if
> you haven't changed to root, of course)."
>
> We'll both just have to wait for 2.5.
>
> Hope this helps,
> Jerry Ratner
_____ ___ Tom L. Schmidt, Manager, Component Characterization
| | / \ Micron Technology, Inc.
| | \___ 2805 E. Columbia Rd. Mail Stop 376 P.O. Box 6
| | \ Boise, Idaho USA 83707-0006
| |____\___/ tschmidt@pefs1.micron.com
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:19 CDT