On 22/07/2023 3:31 am, Till Wegmüller wrote:
On 21.07.23 02:22, Carl Brewer wrote:
Given the apparent reluctance to maintain this mailing list (despite
the benefits - open, it's an automagic archive, it's enough of a
barrier to entry to stop modern spammers but everyone has email) etc etc
It's a CIFS mount. Hard doesn't take, it always mounts as soft.
Michelle.
On Fri, 2023-07-21 at 21:37 +0200, Udo Grabowski (IMK) wrote:
> On 21/07/2023 20:55, Michelle wrote:
> > In case it helps, this is what's reported by mount...
> >
> > //192.168.0.2/jaguar on /mnt/jaguar type cifs
> >
On 21/07/2023 20:55, Michelle wrote:
In case it helps, this is what's reported by mount...
//192.168.0.2/jaguar on /mnt/jaguar type cifs
(rw,relatime,vers=3.0,cache=none,username=michelle,.. > ..,soft,...
There's your problem: NEVER EVER mount anything
SOFT, but always HARD ! SOFT means YOU
Hi Till,
Sorry ... to start from the beginning...
When I buy a Blu Ray or DVD, I digitise them because many of my devices
don't actually have drives these days.
They are, "dumped," to a large network share on one of my OI servers.
In order to sort them, I have to play them and then rename them
Considering that SMB comes from Windows, this might be intentional.
-Till
On 21.07.23 20:51, Michelle wrote:
Hi Till,
Unfortunately it didn't work.
I tested by running a video and then attempting to rename it while it
was running.
Previously it worked on ver 1.0 but even with cache=none and
Hi Till,
Unfortunately it didn't work.
I tested by running a video and then attempting to rename it while it
was running.
Previously it worked on ver 1.0 but even with cache=none and ver=3.0 it
failed to rename with the resource temporarily unavailable.
I'll read up on the cache variable and
In case it helps, this is what's reported by mount...
//192.168.0.2/jaguar on /mnt/jaguar type cifs
(rw,relatime,vers=3.0,cache=none,username=michelle,uid=0,noforceuid,gid
=0,noforcegid,addr=192.168.0.2,file_mode=0777,dir_mode=0777,soft,nounix
Hi Till,
Thanks very much. I'll give that a try.
Michelle.
On Fri, 2023-07-21 at 19:37 +0200, Till Wegmüller wrote:
> Hey Michelle
>
> The Internet tells me this might be related to linuxes client
> caching.
> Try cache=none if you are having locking problems. And experiment a
> bit
> with
Hey Michelle
The Internet tells me this might be related to linuxes client caching.
Try cache=none if you are having locking problems. And experiment a bit
with the cache variable.
-Till
On 21.07.23 13:41, Michelle wrote:
Can't work out why I'm getting this, which is causing problems
On 21.07.23 02:22, Carl Brewer wrote:
Given the apparent reluctance to maintain this mailing list (despite the
benefits - open, it's an automagic archive, it's enough of a barrier to
entry to stop modern spammers but everyone has email) etc etc
What -should- we be using to report issues &
On 20.07.23 21:15, James Madgwick wrote:
So it is not possible to have a new domain to host the mailman site
pages (say lists.openindiana.org)?
Nope, I tried I would need to hack the database and I have to hack that
admin account first Mailman basically binds the list to the domain.
Can't work out why I'm getting this, which is causing problems
accessing/renaming/moving files, more specifically if they're in use by
another process, which used to be no problem under vers=1.0
...but obviously I'm not going to shift back to vers=1.0. I did try
connecting at 2.0 and also leaving
12 matches
Mail list logo
