On 2020-01-15 11:05, Strahil Nikolov wrote:
> On January 13, 2020 5:40:06 AM GMT+02:00, Nick Holland
> wrote:
>>On 2020-01-12 15:39, Antoine Jacoutot wrote:
>>> Sounds like something is keeping your fs busy. Could be gio-kqueue,
>>do you have glib2 installed?
>>
>>That would be my first guess, to
On January 13, 2020 5:40:06 AM GMT+02:00, Nick Holland
wrote:
>On 2020-01-12 15:39, Antoine Jacoutot wrote:
>> Sounds like something is keeping your fs busy. Could be gio-kqueue,
>do you have glib2 installed?
>
>That would be my first guess, too -- it's not unmounting because it
>shouldn't. But
On 2020-01-12 15:39, Antoine Jacoutot wrote:
> Sounds like something is keeping your fs busy. Could be gio-kqueue, do you
> have glib2 installed?
That would be my first guess, too -- it's not unmounting because it
shouldn't. But ... this is a VERY single purpose machine (backups
via rsync --link
Sounds like something is keeping your fs busy. Could be gio-kqueue, do you have
glib2 installed?
—
Antoine
> On 13 Jan 2020, at 06:01, Nick Holland wrote:
>
> Hiya.
>
> I'd like to use amd(8) to automatically mount and dismount local file
> systems. The file systems in question are big, lo
Hiya.
I'd like to use amd(8) to automatically mount and dismount local file
systems. The file systems in question are big, lots of complicated
links, lots of files, and take a while to fsck if the power goes out
unexpectedly, and are used relatively rarely (maybe an hour a day).
Sounds like a per
automatically mounts filesystems.
>
> The way I read that bug report is that mount_nfs(8) defaults to NFSv3
> while the automount daemon amd(8) for some reason defaults to NFSv2.
> There is also a patch. There is nothing amd64 architecture specific in
> that message.
I really don&
On Sat 20/06/2015 14:25, Alessandro DE LAURENZIS wrote:
>> Dear misc@ readers,
>>
>> I actually use amd for a long time, but I never realized this until I
>> started to share large files...
>>
>[...]
>> but nothing changes. Of course, NFSv2 works properly only for files
>> smaller than 2GB, so th
On Sat 20/06/2015 14:25, Alessandro DE LAURENZIS wrote:
> Dear misc@ readers,
>
> I actually use amd for a long time, but I never realized this until I
> started to share large files...
>
[...]
> but nothing changes. Of course, NFSv2 works properly only for files
> smaller than 2GB, so this is be
Dear misc@ readers,
I actually use amd for a long time, but I never realized this until I
started to share large files...
First things first, my amd configuration is neither fancy nor complex:
just22@poseidon:[~]> cat /etc/rc.conf.local
[...]
# BSM automounter
portmap_flags=""
On Sun 27/04, Kirill Bychkov wrote:
> On Sun, April 27, 2014 22:32, Alessandro DE LAURENZIS wrote:
> Hi.
> This is mentioned in /etc/rc.conf:
> amd_flags=NO# for normal use: "" and see amd_master below
>
Hi Kirill,
Thanks for your feedback. 5.4-Rel here, and:
just22@poseidon:[~]> eg
On Sun, April 27, 2014 22:32, Alessandro DE LAURENZIS wrote:
> Folks,
>
> I'm trying to configure the amd service in order to auto-mount a NFS
> directory. I noticed that adding the following line in
> /etc/rc.conf.local:
>
> amd_flags="-a /tmp/amd_mnt -l syslog -x all /nfs nfs.map"
>
> the service
Folks,
I'm trying to configure the amd service in order to auto-mount a NFS
directory. I noticed that adding the following line in
/etc/rc.conf.local:
amd_flags="-a /tmp/amd_mnt -l syslog -x all /nfs nfs.map"
the service fails to start, not being probably able to apply the
specified options to t
On Fri, 10 Sep 2010 22:41:43 +0200 "Bret S. Lambert"
wrote:
>
> On Fri, Sep 10, 2010 at 10:37:50PM +0200, Jean-Francois wrote:
> > Hello,
> >
> > Do you have an idea where to look for an auto mounter in openbsd ?
> > I installed gnome as a server for a friend and would like that his
> > fat32 usb
hi
you can try hotplugd (8)
On 22:37 Fri 10 Sep , Jean-Francois wrote:
> Hello,
>
> Do you have an idea where to look for an auto mounter in openbsd ? I
> installed
> gnome as a server for a friend and would like that his fat32 usb disks are
> auto mounted ...
>
> It might be useful to auto
On Fri, Sep 10, 2010 at 10:37:50PM +0200, Jean-Francois wrote:
> Hello,
>
> Do you have an idea where to look for an auto mounter in openbsd ? I
> installed
> gnome as a server for a friend and would like that his fat32 usb disks are
> auto mounted ...
>
> It might be useful to auto mount also
Hello,
Do you have an idea where to look for an auto mounter in openbsd ? I installed
gnome as a server for a friend and would like that his fat32 usb disks are
auto mounted ...
It might be useful to auto mount also other kind of file systems.
And for esata, is it possible to mount without reb
On Tuesday 13 January 2009 12:24:32 Julian Leyh wrote:
> Rudi Ludwig schrieb:
> > I have put that at the end of my .profile and it works for remote
> > login (ssh).
> > But the KDE konsole and xterm still resist and display the
> > physical location at start-up instead of $HOME (~).
> > I did logo
Rudi Ludwig schrieb:
I have put that at the end of my .profile and it works for remote login
(ssh).
But the KDE konsole and xterm still resist and display the physical
location at start-up instead of $HOME (~).
I did logout of the X session and login again, just to make sure.
Are you using a l
an interesting discussion of this very problem:
http://plan9.bell-labs.com/sys/doc/lexnames.html
On Jan 12, 2009, at 2:44 PM, Philip Guenther wrote:
On Mon, Jan 12, 2009 at 2:35 PM, Rudi Ludwig wrote:
On Monday 12 January 2009 20:38:03 Philip Guenther wrote:
When the shell is starte
On Mon, Jan 12, 2009 at 2:35 PM, Rudi Ludwig wrote:
> On Monday 12 January 2009 20:38:03 Philip Guenther wrote:
>> When the shell is started by konsole, or xterm, or login, it's
>> working directory has already been set to $HOME. At that point, it
>> can only see the physical path (sans symlinks)
On Monday 12 January 2009 20:38:03 Philip Guenther wrote:
> When the shell is started by konsole, or xterm, or login, it's
> working directory has already been set to $HOME. At that point, it
> can only see the physical path (sans symlinks). If you want it to
> see the logical path, then you nee
On Mon, Jan 12, 2009 at 10:49 AM, Rudi Ludwig wrote:
...
> Opening a new Konsole in KDE and trying some commands:
> ibook:/usr/home/rudi$ /bin/pwd
> /usr/home/rudi
> ibook:/usr/home/rudi$ cd
> ibook:~$ /bin/pwd
> /usr/home/rudi
> ibook:~$ echo $HOME
> /home/rudi
> ibook:~$ echo $PWD
> /home/rudi
>
> reads:ibook:/usr/home/rudi$
> >
> > ..Argh, of course
> > " despite $HOME being ..."
> >
> > you might have guessed.
>
> I don't know anything of automounter, but if /home/username is
> provided as a symlink to /usr/home/username,
On Monday 12 January 2009 17:41:09 mhe...@gmail.com wrote:
> > within an xsession or when login in remotely via ssh the initial
> > path
> >
> > is always: /usr/home/ despite $PATH being /home/
> >
> > That is, xterm initially reads: ibook:/usr/home/rudi$
> >
> > instead of just: ibook:~$
> >
> >
On Jan 11, 2009 12:44pm, Rudi Ludwig wrote:
> Hello,
>
>
>
> for flexibility I have configured my computer (OpenBSD 4.4; macppc)
>
> with the home directory being auto mounted.
>
>
>
> that is /etc/amd/amd.home reads:
>
> #
>
> * type:=link;fs:=/usr/home;sublink:=${key}
>
>
>
> This works as desir
espite $HOME being ..."
>
> you might have guessed.
I don't know anything of automounter, but if /home/username is provided
as a symlink to /usr/home/username, then that behaviour is expected:
entering a symlinked directory changes the path to the expanded form of
the symlink.
Pr
On Sunday 11 January 2009 12:44:31 Rudi Ludwig wrote:
> i ... despite $PATH being
> /home/ That is, xterm initially
> reads:ibook:/usr/home/rudi$
..Argh, of course
" despite $HOME being ..."
you might have guessed.
Rudi
Hello,
for flexibility I have configured my computer (OpenBSD 4.4; macppc)
with the home directory being auto mounted.
that is /etc/amd/amd.home reads:
#
* type:=link;fs:=/usr/home;sublink:=${key}
This works as desired. The programs use /home/ as
they should, the real data locates in /usr
28 matches
Mail list logo
