hallo Darac,
Darac Marjal writes:
> On 01/04/2024 07:55, Felix Natter wrote:
>
> hello debian-users,
>
> I configured autofs for /home:
>
> * -fstype=nfs,rw,soft,bg,intr SERVER:/share/&
>
> Just to point out that this is "/share", not "/home".
On 01/04/2024 07:55, Felix Natter wrote:
hello debian-users,
I configured autofs for /home:
* -fstype=nfs,rw,soft,bg,intr SERVER:/share/&
Just to point out that this is "/share", not "/home". You might have set
user's home directories to be /share/, but you'
hello debian-users,
I configured autofs for /home:
* -fstype=nfs,rw,soft,bg,intr SERVER:/share/&
But now the login as "admin" does not work any more, since
it tries to mount SERVER:/share/admin -> Is it possible to exclude
a user from automounting?
The workaround [1] I us
Hi.
On Tue, 10 Jan 2017 19:32:54 -0500
Harry Putnam wrote:
> Reco writes:
>
> [...]
>
> >> ls /prj/d0 or ls /prj/dv both fail. However another share on that
> >> same setup on the solaris host `gv' and 2x comes up as expected.
> >
> > You lost me here. If 'd0' and 'dv' are share name
e shares (Solaris host 2x) they are share names.
[...]
>> So ls /prj/gv after a pause shows /prj/gv/merb/
>
> Therefore 'gv' is a host name and 'merb' is a share on that host.
> Assuming you're using stock auto.net.
> Debug autofs output confirms this
ls /prj/gv after a pause shows /prj/gv/merb/
Therefore 'gv' is a host name and 'merb' is a share on that host.
Assuming you're using stock auto.net.
Debug autofs output confirms this:
update_offset_entry: parse(sun): updated multi-mount offset /merb ->
-fstype=nfs4,soft,intr,nodev,nosuid,async gv:/merb
Reco
. At least these are defaults starting with
> Solaris 10.
>
> The thing that's broken here is autofs, not NFS implementation.
I finally got around to trying the auto.net file you mentioned in your
first reply in this thread.
I still cannot read it and understand what it does but I
other things you mentioned.
>
> The `-hosts' line in auto.master has been commented out from the start.
>
> Must be shipped with autofs that way, as I did not do it.
>
> So then apparently it is not #828217 at the bottom of this. Or at
> least not because of `net
m the start.
Must be shipped with autofs that way, as I did not do it.
So then apparently it is not #828217 at the bottom of this. Or at
least not because of `net -hosts' being in play.
^^^
> addr=192.168.1.42 0 0
Ok, that simplifies things somewhat. So it's tcp-over-ipv4 type of NFS4
without any security worth mentioning.
> > 3) Stop autofs, start it like this:
> >
> > /usr/sbin/automount -fd
> >
> > Mount a filesystem. Watch
Reco writes:
[...]
> Won't it be fun otherwise?
>
> The good thing is - autofs is working as intended.
> The bad thing is - mount is failing.
,
| NOTE: I've rearranged your post to put the next question and answer at
| the bottom of this reply
`
[...] mis
Hi.
On Mon, 09 Jan 2017 08:14:51 -0500
Harry Putnam wrote:
> Reco wrote:
> > Note that it be simplified to:
> >
> > * --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/&
>
> I created /etc/auto.nfs and tried that forumulation. Restarted
> autofs
Reco writes:
[...]
> And it gone haywire from here.
Hehe... thats a good description...
> Autofs has a concept of master map ( auto.master(5) ) which can contain
> lines referring to either direct or indirect maps ( autofs(5) ).
>
> /etc/auto.master.d is intended for exten
Reco wrote:
> [1] http://blog.tomecek.net/post/automount-with-systemd/
Note: this only works with static mounts.
If you want to use any kind of automatic mapping you can't do this with
systemd.
Grüße,
S°
--
Sigmentation fault. Core dumped.
Hi.
On Sun, 08 Jan 2017 13:37:32 -0500
Harry Putnam wrote:
> I've edited /etc/auto.master by adding this line:
>
> /projects-nfs /etc/auto.master.d/prj-nfs.autofs --timeout=180
And it gone haywire from here.
Autofs has a concept of master map ( auto.master(
,
| NOTE: A similar post was accidently posted to gentoo list but was
| intended to be posted here
`
Setup: Running Debian jessie-stable
I've never used autofs and am trying to get it setup.
Following the debian wiki and an Ubuntu howto.
Also this site:
http://www.linuxtech
Hello.
I've setup autofs in Debian 7 to automount iso's when it is accessed via
samba. At start it was working fine. I've setup --timeout=5. But as
number of iso's grew, autofs started just to create the folders for the
corresponding iso's while no content was i
Quoting Mimiko (vbv...@gmail.com):
> On 03.04.2015 23:21, David Wright wrote:
> >I'm as yet unconvinced. I can't see in your original posting where
> >you've told ZFS how to manage mounting your volumes.
>
>
> In my original post I've wrote:
>
> zfs create -V 4T zfspool/backup
> zfs create -V 1T
On 03.04.2015 23:21, David Wright wrote:
Those scripts have logging lines. Have you read their output?
Yes, there are logging, But there is no any suspection lines in that log
files. Only error is given when it's trying to mount devices so there are:
/backup/network - error mounting
/backup/o
On 03.04.2015 23:21, David Wright wrote:
I'm as yet unconvinced. I can't see in your original posting where
you've told ZFS how to manage mounting your volumes.
In my original post I've wrote:
zfs create -V 4T zfspool/backup
zfs create -V 1T zfspool/network
zfs create -V 1T zfspool/op
mount
Quoting Mimiko (vbv...@gmail.com):
> On 01.04.2015 17:55, Reco wrote:
> > No, the problem is related to the Debian indeed. As ZFS is used as an
> > LVM here, so you might as well replace those fancy/dev/zvol/* with
> > something conventional, and the problem will still remain.
I'm as yet unconvinc
On 01.04.2015 17:55, Reco wrote:
> No, the problem is related to the Debian indeed. As ZFS is used as an
> LVM here, so you might as well replace those fancy/dev/zvol/* with
> something conventional, and the problem will still remain.
>
> Consider the following /etc/fstab.
>
> /dev/sda1 /backup
Hi.
On Wed, 1 Apr 2015 10:33:29 -0400
Dan Ritter wrote:
> On Wed, Apr 01, 2015 at 02:15:32PM +0300, Mimiko wrote:
> > The question is, is there are method better to overcome this
> > problem? How to specify mount order? How to enable zfs import early?
> I suspect you will need to talk to the
nt() can mount other disks.
>
> The question is, is there are method better to overcome this
> problem? How to specify mount order? How to enable zfs import early?
>
> Second problem arises for autofs. I've setup it, so in /backup are
> some iso files. But when autofs st
d it. First time do_mount()
mounts only /backup, second time do_mount() can mount other disks.
The question is, is there are method better to overcome this problem?
How to specify mount order? How to enable zfs import early?
Second problem arises for autofs. I've setup it, so in /backup a
Hi,
Thank you very much for your help.
Replacing
ikki-fstype=ntfs,gid=46,dmask=002,fmask=113 :/dev/ikki
with
ikki-fstype=fuse,gid=46,dmask=002,fmask=113 :ntfs-3g#/dev/ikki
solved the problem.
ntfs-3g was already installed on my system.
Regards.
Thierry
On Sun, 16 Nov 2
Hi.
On Sun, 16 Nov 2014 12:42:31 +0100
Thierry Rascle wrote:
> The automounting used to work for all of the entries, but now does not
> for the three entries with "-fstype=ntfs".
Install ntfs-3g, replace
-fstype=ntfs,gid=46,dmask=002,fmask=113 :/dev/ikki jacala
with
-fstype=fuse,gid=46,
Hi list,
I'm using sid, with wmii as my only window manager and desktop
environment.
I'm using autofs for automounting my external devices:
- CD/DVD drives,
- USB sticks formatted as FAT or NTFS,
- external hard disk drives formatted has EXT4 or NTFS. or NTFS),
CD-ROM drives, ext
hi,
I'm trying to get autofs with LDAP working. We have two file servers (old/new)
and several LDAP entries, like described in:
/usr/share/doc/autofs-ldap/examples/ldap-automount-rfc2307-bis-auto.direct:
===
# extended LDIF
#
# LDAPv3
# base with scope
su
Soul Makossa wrote:
> I'm trying to get the following to work on Debian Squeeze 6.6
Although I have previously used the autofs automounter quite a bit now
time has passed and my memory has grown vague. But seeing no one else
with an answer I will respond hoping to be helpful.
> /etc/
Hi,
I've been trying to export an autofs-mounted filesystem via NFS, but I can't
get it to work. Basically when I try to mount such export on the client,
mount.nfs gets stuck and never completes.
Autofs seems to work correctly. because after starting the daemon on the server
and say, d
Tom H wrote:
> Bob Proulx wrote:
> > A pet peeve of mine is "share". Windows has "shares". Unix has
> > "filesystems". NFS is itself a Network File System. So saying
> > Network File System Share feels like saying a Personal PIN
> > Number. It would make me happier if people just referred to
> > th
On Tue, Jul 31, 2012 at 11:20 PM, Bob Proulx wrote:
> T o n g wrote:
>> Bob Proulx wrote:
>>> T o n g wrote:
>>>>
>>>> My Autofs auto-mounted NFS share looks like this:
>
> A pet peeve of mine is "share". Windows has "shares"
On Thu, Aug 2, 2012 at 12:38 AM, T o n g wrote:
> On Tue, 31 Jul 2012 10:44:14 -0400, Tom H wrote:
>>
>> 1) Does the mount work if you export with nfsv3 specified?
>
> Hmm... that might be the way. How can I do that?
>
> I remember that I have to specify nfsv3 on the client/nfsmount side to
> get
On Tue, 31 Jul 2012 10:44:14 -0400, Tom H wrote:
> 1) Does the mount work if you export with nfsv3 specified?
Hmm... that might be the way. How can I do that?
I remember that I have to specify nfsv3 on the client/nfsmount side to
get the straight-mount work for my uid and gid.
Thanks
--
Ton
T o n g wrote:
> Bob Proulx wrote:
> > T o n g wrote:
> >> My Autofs auto-mounted NFS share looks like this:
A pet peeve of mine is "share". Windows has "shares". Unix has
"filesystems". NFS is itself a Network File System. So saying
Network Fi
On Sun, Jul 29, 2012 at 2:37 PM, T o n g wrote:
>
> My Autofs auto-mounted NFS share looks like this:
>
> drwxr-xr-x 9 4294967294 4294967294 45056 2011-04-12 09:47 tmp/
>
> I.e., the user id and group id are all mapped wrong.
>
> I have identical user ids and group
On Sun, 29 Jul 2012 18:06:31 -0600, Bob Proulx wrote:
> T o n g wrote:
>> My Autofs auto-mounted NFS share looks like this:
>>
>> drwxr-xr-x 9 4294967294 4294967294 45056 2011-04-12 09:47 tmp/
>>
>> I.e., the user id and group id are all mapped wrong.
>
T o n g wrote:
> My Autofs auto-mounted NFS share looks like this:
>
> drwxr-xr-x 9 4294967294 4294967294 45056 2011-04-12 09:47 tmp/
>
> I.e., the user id and group id are all mapped wrong.
>
> I have identical user ids and groups between my NFS sharing stations, so
&
Hi,
My Autofs auto-mounted NFS share looks like this:
drwxr-xr-x 9 4294967294 4294967294 45056 2011-04-12 09:47 tmp/
I.e., the user id and group id are all mapped wrong.
I have identical user ids and groups between my NFS sharing stations, so
previously, prior to using Autofs I just use
sshfs via autofs. Right now it seems to be working but actually I must have
done something wrong because if I login with www-data on server2 and go to
the user media directory which is owned by www-data I get a permission
denied when I try to write.
This is my /etc/auto.master:
/home/server2/user_
On Mi, 07 mar 12, 13:30:12, Sylvain wrote:
> 2012/3/7 Camaleón :
> > Anyway, I would have expected some kind of warning at the logs coming
> > from backuppc indicating a problem for accessing to the configured mount
> > point which was not available at that time and thus failing.
>
> Me too, and I
On Wed, 07 Mar 2012 13:30:12 +0100, Sylvain wrote:
> 2012/3/7 Camaleón :
>> Anyway, I would have expected some kind of warning at the logs coming
>> from backuppc indicating a problem for accessing to the configured
>> mount point which was not available at that time and thus failing.
>
> Me too,
2012/3/7 Camaleón :
> Anyway, I would have expected some kind of warning at the logs coming
> from backuppc indicating a problem for accessing to the configured mount
> point which was not available at that time and thus failing.
Me too, and I didn't understand why I wasn't getting anything in the
; with "service backuppc status".
>
> Yes, the /removable/sbackup/backuppc directory is empty since autofs has
> not started yet and thus has not created the directory yet.
Okay, then the service is started but fails.
>> Mmm, I would open a bug against the package it sel
On Wed, Mar 7, 2012 at 2:46 AM, Sylvain wrote:
> 2012/3/6 Tom H :
>>
>> AFAICT, a bug should be filed against backuppc to change its init
>> script to have "$remote_fs" (or "$all"!) in "Required-Start" or
>> "autofs" in "
2012/3/6 Tom H :
> AFAICT, a bug should be filed against backuppc to change its init
> script to have "$remote_fs" (or "$all"!) in "Required-Start" or
> "autofs" in "Should-Start".
autofs doesn't seem to be included in $remote_fs
a service is not
started by default cannot be considered a bug or error "per se".
> Note that my /var/lib/backuppc directory points to
> /removable/sbackup/backuppc which is my external USB HDD mounted by
> autofs, which is in /etc/rc*.d/S21autofs (backuppc is
> /etc/rc*.d/S
/etc/init.d/backuppc start, it works just fine. There
> are also startup scripts in /etc/rc*.d/. My backuppc version is
> 3.2.1-2 (I'm running a testing install).
>
> Note that my /var/lib/backuppc directory points to
> /removable/sbackup/backuppc which is my external USB HDD mou
t, it works just fine. There
are also startup scripts in /etc/rc*.d/. My backuppc version is
3.2.1-2 (I'm running a testing install).
Note that my /var/lib/backuppc directory points to
/removable/sbackup/backuppc which is my external USB HDD mounted by
autofs, which is in /etc/rc*.d/S21autofs
also startup scripts in /etc/rc*.d/. My backuppc version is
3.2.1-2 (I'm running a testing install).
Note that my /var/lib/backuppc directory points to
/removable/sbackup/backuppc which is my external USB HDD mounted by
autofs, which is in /etc/rc*.d/S21autofs (backuppc is
/etc/rc*.d/S21backup
Stephane Durieux wrote:
> A simple question:
> from a server point of view does autofs costs less (cpu, io, memory)
> than "traditionnal" nfs ?
AutoFS is simply a automated mount service for NFS. AutoFS doesn't
replace NFS. The autofs simply gets nfs going by mounting r
Hello,
A simple question:
from a server point of view does autofs costs less (cpu, io, memory) than
"traditionnal" nfs ?
From a client point of view I think the fact to unmount directories frees
ressources?
But does a moint point consumes so much (memory ?)
And concerning t
e dead and can be used for debugging. But from an open ssh
session I can restart autofs and then the shutdown goes further.
First I tried to remove /usr/local/bin from the PATH variable in
/etc/profiles. But this doesn't not help, because a lot of init scripts
define theire own PATH variabl
On Fri, Apr 15, 2011 at 10:59 AM, Aniruddha wrote:
> On Tue, Apr 12, 2011 at 11:07 PM, Klistvud wrote:
>> Dne, 12. 04. 2011 20:52:08 je Aniruddha napisal(a):
>
>>> I tried with and without quotes, with the label and formatting the
>>> drive as ext3. I restarte
On Tue, Apr 12, 2011 at 11:07 PM, Klistvud wrote:
> Dne, 12. 04. 2011 20:52:08 je Aniruddha napisal(a):
>> I tried with and without quotes, with the label and formatting the
>> drive as ext3. I restarted autofs. None of these worked. When I cd to
>> /var/autofs/removable
ate vfat...
I tried with and without quotes, with the label and formatting the
drive as ext3. I restarted autofs. None of these worked. When I cd to
/var/autofs/removable it's empty.
It's supposed to be empty. After you cd to it, try issuing:
ls usb
Or, even better, use the --ghost op
the label and formatting the
drive as ext3. I restarted autofs. None of these worked. When I cd to
/var/autofs/removable it's empty. My current settings:
# cat /etc/auto.master
/var/autofs/removable /etc/auto.removable --timeout=2,sync,nodev,nosuid
# cat /etc/auto.removable
usb
Dne, 12. 04. 2011 17:39:35 je Aniruddha napisal(a):
I try to automagically mount an usb drive following the autofs
instructions in the wiki ( http://wiki.debian.org/AutoFs ). For some
reason it just doesn't work. I can't find any relevant error message
in messages or syslog. Any i
I try to automagically mount an usb drive following the autofs
instructions in the wiki ( http://wiki.debian.org/AutoFs ). For some
reason it just doesn't work. I can't find any relevant error message in
messages or syslog. Any ideas where I can begin to troubleshoot? Thanks!
#
On Sat, 05 Mar 2011 19:28:39 +0530, L V Gandhi wrote:
> On Sat, Mar 5, 2011 at 5:21 PM, Camaleón wrote:
>> > Any solutions to mount with ownership of user?
>>
>> As per "man 5 autofs":
>>
>> (...)
>>
>> If you use the automounter for a f
gt; UUID=84C0-F18B
>
> (...)
>
> > Any solutions to mount with ownership of user?
>
> As per "man 5 autofs":
>
> (...)
>
> If you use the automounter for a filesystem without access permissions
> (like vfat), users usually can't write on such a f
fat,rw,uid=1000,umask=022,posix,shortname=winnt
> UUID=84C0-F18B
(...)
> Any solutions to mount with ownership of user?
As per "man 5 autofs":
(...)
If you use the automounter for a filesystem without access permissions
(like vfat), users usually can't write on such a files
,umask=022,posix,shortname=winnt
UUID=84C0-F18B
I tried both /dev/ehd and UUID methods.
/var/autofs/removable/ehd is mounted as root.root.
I tried chown as sudo. There also I failed.
lvgandhi@lvgvaio:~$ sudo chown lvgandhi /var/autofs/removable/ehd
chown: changing ownership of `/var/autofs/removable
--- On Tue, 3/23/10, Brian wrote:
> From: Brian
> Subject: Monitoring AutoFS in SNMP
> To: "Debian User"
> Date: Tuesday, March 23, 2010, 10:00 AM
> I am trying to find a MIB to monitor
> AutoFS but everything I find is tied to the current pid
> AutoFS i
> If it spawns a new process each time it mounts a new
> partition, would it
> not have a parent process that would at least be constant
> on the server?
> If that's the case, maybe you should just monitor the
> parent process.
> Otherwise, it would make sense to monitor a partition
> instead of
> We are using autofs to mount cdrom and dvd iso images. There
> are nearly 100 of them. Too many to really monitor
> individually so we wanted to just monitor autofs. It looks
> to me like each auto.* file in /etc spawns it's own process
> and pid. And the pid c
> > I am trying to find a MIB to monitor AutoFS but
> everything I
> > find is tied to the current pid AutoFS is running
> under which
> > of course changes each time it is restarted making it
> useless
> > as a monitoring metric.
>
> I'm not famil
> > I am trying to find a MIB to monitor AutoFS but
> everything I find
> > is tied to the current pid AutoFS is running under
> which of
> > course changes each time it is restarted making it
> useless as a
> > monitoring metric.
>
> ??? Isn't that a
> I am trying to find a MIB to monitor AutoFS but everything I
> find is tied to the current pid AutoFS is running under which
> of course changes each time it is restarted making it useless
> as a monitoring metric.
I'm not familiar with autofs but if you do a
On 2010-03-23 09:00, Brian wrote:
I am trying to find a MIB to monitor AutoFS but everything I find
is tied to the current pid AutoFS is running under which of
> course changes each time it is restarted making it useless as a
> monitoring metric.
??? Isn't that a *good* thing?
I am trying to find a MIB to monitor AutoFS but everything I find is tied to
the current pid AutoFS is running under which of course changes each time it is
restarted making it useless as a monitoring metric.
Has anyone setup SNMP to monitor AutoFS or a similar type of daemon on a Debain
Solved!
On Sun, Jan 10, 2010 at 9:38 AM, Mike Castle wrote:
> Oh ... I just remembered... / on the ldap server was full, and I ended
> up nuking a lot of stuff on that partition. I wonder if I got overly
> zealous and deleted something important. I hope not.
Not sure if I deleted too much, or
Has anyone else noticed that autofs has stopped working on testing?
I'm really just digging into the debugging process, so may not have
read all of the necessary docs quite yet.
I've had autofs working for /home and a /share hierarchy for quite
some time now, and haven't had to
On 12.04.09 01:34, Stephen Guzik wrote:
> Automounting used to work fine with gnome in squeeze. Then I
> installed and removed autofs and now it seems to be disabled. Does
> anyone know how to recover the original behaviour?
automount mounts filesystems automatically when someone&#x
Hi,
Automounting used to work fine with gnome in squeeze. Then I
installed and removed autofs and now it seems to be disabled. Does
anyone know how to recover the original behaviour?
Thanks,
Stephen
Hello List,
on my (little) cluster, I used autofs to mount
the `/home' directory on the worker nodes:
is it possible (and recommended) to give a negative
niceness to automount ? what is the Debian to do so ?
Thanks in advance,
Jerome
--
Jerome BENOIT
jgmbenoit_at_mailsnare_dot_net
Robert Cates wrote:
Hi, and thanks for your help!
I have not made any changes to the default configuration for autofs. The
truth is, I'm not even sure I need it installed. I thought it sounded like
a nice feature, but I haven't done anything with it yet.
This machine is a
Hi, and thanks for your help!
I have not made any changes to the default configuration for autofs. The
truth is, I'm not even sure I need it installed. I thought it sounded like
a nice feature, but I haven't done anything with it yet.
This machine is a server, so therefore no KDE or
Robert Cates wrote:
Hi all,
to get right straight to my question – i was wanting to know which is
the proper file system to choose for a (normal) USB 2.0 data/flash
stick – autofs, usbfs or maybe vfat? The stick is of course usable
under Windows as well as linux (from kernel 2.4.x). I
Hi all,
to get right straight to my question - i was wanting to know which is the
proper file system to choose for a (normal) USB 2.0 data/flash stick -
autofs, usbfs or maybe vfat? The stick is of course usable under Windows as
well as linux (from kernel 2.4.x). I believe I need to set
Bruno Cochofel wrote:
Hi, I have this config of autofs:
# auto.master
/var/autofs/removable /etc/auto.removable --timeout=2
/var/autofs/nfs /etc/auto.misc --timeout=60
# auto.removable
# devices
cdrom -fstype=iso9660,ro,sync,nodev,nosuid
Hi, I have this config of autofs:
# auto.master
/var/autofs/removable /etc/auto.removable --timeout=2
/var/autofs/nfs /etc/auto.misc --timeout=60
# auto.removable
# devices
cdrom -fstype=iso9660,ro,sync,nodev,nosuid
:/dev/cdrom
floppy -fstype=auto
Hi Martin,
the initscript is unable to find your auto.master map. Unless
you've modified the initscript, it expects an object of class
automountMap with ou=auto.master _below_ LDAPBASE. Have a look at
] /usr/share/doc/autofs-ldap/README.ldap_master
for an example.
Regards,
Jan
signatur
On Thu, May 10, 2007 at 06:16:08PM +0200, Martin Marcher wrote:
> Hello,
>
> i'm trying to get autofs pull everything from ldap (even auto.master)
>
> Now the situation is the following having an auto.master as below and
> nsswitch.conf with !automount: files" pull
Hello,
i'm trying to get autofs pull everything from ldap (even auto.master)
Now the situation is the following having an auto.master as below and
nsswitch.conf with !automount: files" pulls the map from ldap (because
auto.master says to...), but nsswitch.conf with "automount: l
Hi,
> I can't seem to figure out a *very* simple automount configuration
> (I've done this before, but it was over two years ago :-( ).
>
> After much work (and not enough understanding!), I have succeed in
> automounting a remote /home directory on a loc
Hi,
In your config,
/etc/auto.master:
/home /etc/auto.misc --timeout 60
This should be fine ...
/etc/auto.misc:
home-fstype=nfs,hard,intr 1.2.3.4:/home
But, this line should be
* -fstype=nfs,hard,intr 1.2.3.4:/home/&
I
onfig: Debian/etch
>
> I can't seem to figure out a *very* simple automount configuration
> (I've done this before, but it was over two years ago :-( ).
>
> After much work (and not enough understanding!), I have succeed in
> automounting a remote /home directory on a lo
Config: Debian/etch
I can't seem to figure out a *very* simple automount configuration
(I've done this before, but it was over two years ago :-( ).
After much work (and not enough understanding!), I have succeed in
automounting a remote /home directory on a local client usi
Dieter Roels wrote:
Joao Carlos de Lima Roscoe wrote:
I have a bunch of autofs mounts in my etch box, whose doesn't show in my
filesystem tree until I explicitly use them, with a cd command, for
instance
(ok, this is the intend autofs behaviour);
My Solaris 9 boxes show a diff
Joao Carlos de Lima Roscoe wrote:
I have a bunch of autofs mounts in my etch box, whose doesn't show in my
filesystem tree until I explicitly use them, with a cd command, for
instance
(ok, this is the intend autofs behaviour);
My Solaris 9 boxes show a different behaviour: autofs resourc
I have a bunch of autofs mounts in my etch box, whose doesn't show in my
filesystem tree until I explicitly use them, with a cd command, for instance
(ok, this is the intend autofs behaviour);
My Solaris 9 boxes show a different behaviour: autofs resources do show
in the filesystem tree
On 08.07.06 08:48, wehn wrote:
> Ah, updating to unstable seems to have resolved the- only one device at
> a time problems.
>
> And the multiple partition thing is working now that I found out
> "-fstype=auto,sync,rw,uid=1000,gid=100" doesn't play nicely with my 2nd
> ext3 partition (1st is vfat
ecognized mount option "uid=1000" or missing value
EXT3-fs: Unrecognized mount option "gid=100" or missing value
This could take some tweaking to get right.
wehn wrote:
>On 06.07.06 13:41, wehn wrote:
>> I set up autofs for automounting with help of:
>> http
>On 06.07.06 13:41, wehn wrote:
>> I set up autofs for automounting with help of:
>> http://greenfly.net/tips/autofs.html
>>
>> But I can only mount the 1st parition of the first device I insert.
>>Does anyone know what is wrong?
>
>the idea of using
On Thu, Jul 06, 2006 at 02:53:09PM +1000, wehn wrote:
> Tony Heal wrote:
> >Did you try duplicating the line in auto.removable with a second mount
> >point?
> >
>
> Yes. Here's my auto.removable:
>
> cdrom -fstype=iso9660,ro,sync,nodev,nosuid:/dev/cdrom
> floppy -fstype=auto,sync,n
On 06.07.06 13:41, wehn wrote:
> I set up autofs for automounting with help of:
> http://greenfly.net/tips/autofs.html
>
> But I can only mount the 1st parition of the first device I insert. Does
> anyone know what is wrong?
the idea of using autofs for this purpose :)
autofs
Tony Heal wrote:
Did you try duplicating the line in auto.removable with a second mount
point?
Yes. Here's my auto.removable:
cdrom -fstype=iso9660,ro,sync,nodev,nosuid:/dev/cdrom
floppy -fstype=auto,sync,nodev,nosuid :/dev/fd0
sda1 -fstype=auto,sync,rw,uid=1000,
: autofs only mounting one fs at a time.
I set up autofs for automounting with help of:
http://greenfly.net/tips/autofs.html
But I can only mount the 1st parition of the first device I insert. Does
anyone know what is wrong?
If I insert a USB drive, it mounts /dev/sda1 and is accessable from
1 - 100 of 305 matches
Mail list logo
