On Fri, Nov 17, 2023 at 7:10 PM Garrett Wollman wrote:
>
> < said:
>
> > Looks like main still has this problem. I exported a ZFS file system from
> > a 15-current system to the same 13.2 client, and it exhibits the problem
> > (EIO from NFSv3). So the problem is most likely in 14.0 as well.
>
>
< said:
> Looks like main still has this problem. I exported a ZFS file system from
> a 15-current system to the same 13.2 client, and it exhibits the problem
> (EIO from NFSv3). So the problem is most likely in 14.0 as well.
Glad someone was able to reproduce. I don't have any systems I can
e
On 17 Nov 2023, at 17:22, Mike Karels wrote:
> On 17 Nov 2023, at 16:35, Garrett Wollman wrote:
>
>> < said:
>>
>>> I have not run into this, so I tried it just now. I had no problem.
>>> The server is 13.2, fully patched, the client is up-to-date -current,
>>> and the mount is v4.
>>
>> On my 13
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
FreeBSD community,
It is with a heavy heart that I have decided to resign my role as the
Release Engineering Team Lead.
Colin Percival will take over this role, and I will act as his Deputy
Lead unless and until he finds a more suitable person to f
On 17 Nov 2023, at 16:35, Garrett Wollman wrote:
> < said:
>
>> I have not run into this, so I tried it just now. I had no problem.
>> The server is 13.2, fully patched, the client is up-to-date -current,
>> and the mount is v4.
>
> On my 13.2 client and 13-stable server, I see:
I set up ZFS on
< Looking at this from the RPC side:
> (PUTFH, GETATTR, LOOKUP(snapshotname), GETFH, GETATTR)
> [NFS4_OK for all ops]
> (PUTFH, GETATTR)
> [NFS4_OK, NFS4_OK]
> (PUTFH, ACCESS(0x3f), GETATTR)
> [NFS4_OK, NFS4_OK, rights = 0x03, NFS4_OK]
>
< said:
> I have not run into this, so I tried it just now. I had no problem.
> The server is 13.2, fully patched, the client is up-to-date -current,
> and the mount is v4.
On my 13.2 client and 13-stable server, I see:
25034 ls CALL
open(0x237d32f9a000,0x120004)
25034 ls NAMI
On 17 Nov 2023, at 15:04, Garrett Wollman wrote:
> Hi, all,
>
> One other regression that we found after upgrading from 12.4 to 13.2
> on our NFS servers is that ZFS snapshots of exported filesystems are
> no longer accessible to NFS clients. The .zfs/snapshot directory is
> readable, and can sta
Hi, all,
One other regression that we found after upgrading from 12.4 to 13.2
on our NFS servers is that ZFS snapshots of exported filesystems are
no longer accessible to NFS clients. The .zfs/snapshot directory is
readable, and can stat(2) the individual snapshot directories, but
attempting to a
On Fri, Nov 17, 2023, 12:55 PM Garrett Wollman
wrote:
> < said:
>
> > Thanks for the clarifications. With respect to changing root's shell,
> > do I run the risk of breaking anything in, say, periodic that would rely
> > on root's shell being one thing or another ?
>
> periodic(8) is a /bin/sh s
< said:
> Thanks for the clarifications. With respect to changing root's shell,
> do I run the risk of breaking anything in, say, periodic that would rely
> on root's shell being one thing or another ?
periodic(8) is a /bin/sh script and does not depend on any particular
user's shell. It exec
On 11/17/2023 2:41 PM, Garrett Wollman wrote:
I would recommend changing root's shell to something that better suits
your needs: either change it back to csh, or install the appropriate
package and set it to bash or zsh, both of which read startup files
for all interactive shells, not just login
< said:
> I am trying to bring my environment along from previous versions where
> csh was the default shell and now trying to get used to sh. In the past
> things like
> sudo su
> would pick up my settings in /root/.cshrc automatically. However, with
> sh I have to do
> sudo su -l root
> I
I've done chsh :)
On Fri, Nov 17, 2023, 12:02 PM Jonathan Adams wrote:
> On Friday, November 17th, 2023 at 1:56 PM, mike tancsa
> wrote:
>
> > Thanks, but I am hoping to be able to just
> >
>
> > sudo su
> >
>
> > on all boxes I manage, RELENG_12 through 14. I know its a minor
> annoyance, but
On Friday, November 17th, 2023 at 1:56 PM, mike tancsa wrote:
> Thanks, but I am hoping to be able to just
>
> sudo su
>
> on all boxes I manage, RELENG_12 through 14. I know its a minor annoyance,
> but I would like to avoid the inconsistent key strokes.
Ah, understood. Been there. ;-)
-J
Anno domini 2023 Fri, 17 Nov 13:56:36 -0500
mike tancsa scripsit:
> On 11/17/2023 1:50 PM, Jonathan Adams wrote:
> > $ sudo su -
>
>
> Thanks, but I am hoping to be able to just
>
> sudo su
>
> on all boxes I manage, RELENG_12 through 14. I know its a minor
> annoyance, but I would like to a
On 11/17/2023 1:50 PM, Jonathan Adams wrote:
$ sudo su -
Thanks, but I am hoping to be able to just
sudo su
on all boxes I manage, RELENG_12 through 14. I know its a minor
annoyance, but I would like to avoid the inconsistent key strokes.
---Mike
On 11/17/2023 1:46 PM, Freddie Cash wrote:
su by itself just switches your username, it doesn't pick up the rest
of the environment settings like a proper login does.
OK, but its doing something. When I ssh into my account, I have setup
things like my prompt to be
PS1="- $? \u@\h:\w \\$ "
On Friday, November 17th, 2023 at 1:40 PM, mike tancsa wrote:
> I am trying to bring my environment along from previous versions where
> csh was the default shell and now trying to get used to sh. In the past
> things like
>
> sudo su
>
> would pick up my settings in /root/.cshrc automaticall
On Fri, Nov 17, 2023 at 10:41 AM mike tancsa wrote:
> I am trying to bring my environment along from previous versions where
> csh was the default shell and now trying to get used to sh. In the past
> things like
>
> sudo su
>
> would pick up my settings in /root/.cshrc automatically. However, wi
I am trying to bring my environment along from previous versions where
csh was the default shell and now trying to get used to sh. In the past
things like
sudo su
would pick up my settings in /root/.cshrc automatically. However, with
sh I have to do
sudo su -l root
Is there a way to config
Glen Barber wrote:
> No. It merely suggests the release is not officially official yet.
Ok. Thanks for the clarification.
Jamie.
Hi Glen,
> I also agree we cannot prevent people from downloading the images,
> installers, whatever before the announcement. That is the lovely race
> condition with which we have to live at the moment.
Yes, and given that, I don't think you did anything wrong.
It seems that the race is the sa
23 matches
Mail list logo
