From nobody Sat Jul 16 00:18:06 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ll8383zydz4X20l for ; Sat, 16 Jul 2022 00:18:44 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oa1-x2d.google.com (mail-oa1-x2d.google.com [IPv6:2001:4860:4864:20::2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ll8376hCPz3Mww; Sat, 16 Jul 2022 00:18:43 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-10c8e8d973eso9732726fac.5; Fri, 15 Jul 2022 17:18:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=U4JFrkrVHvp8aYamENGgl5bqVUJUysiGglA8u7rz5uQ=; b=F2UQakeHZw487LTs1uqEr6MvJVIBj2aH4D6whweqEYYFN1hEoU+DjK2V9T1lRraIWz nsTMYruY+cJTa8x0AVCPRb6rEUcaCPDn7AEIR9ddpUv2okkL3kiofaFLGcAfWWHFGr8n eKp1VdeqQuQmPa2RCURoO8F9jwZNNT2pZcdYTPPr/RpqcFyx/DANsJc/puiXquykJUF/ FgWUXBKQFdut1XDF+nbrpjGP4Z24p19ez84r0GZnba5MOIUju9rFA/GXDjkMcMjRDiX6 8iu7u0m75Por6ss53CCs4cSbcmaFjpmuobVJbKky6EudE4TvlFKCeIiHhFcOvmBabBuk quKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=U4JFrkrVHvp8aYamENGgl5bqVUJUysiGglA8u7rz5uQ=; b=5DApkdU3JQEB97Mmf9V+wETiExl2nTk2FwADoD96zY7DKauJxBTemqjguw683bTFPN 4l9qgirMFnj5s2ESS1ebfJrKrabko6P/U2J7DXK0o/zMtL2NYrDuJOJujnsFEvHj6+tM dxRGGRQ8nZlAEyr2YKLvH8bCsVz7pIQEqdI3FJGMd5kHAvuVxrItyGQ89+ucR2Byhk9C Afnwl9hJS+HzQVICa02zZ32GIkF/CnxnZaLBrqO07h0yqS2AOmIi8uFLhOMUnvSdifh1 9AP+LHCC7KGXWiAudI/9JBlEPkGq7As/LsH7dVhBC3de3ATOLn0QVoTG2GATUj2UyblV ENrw== X-Gm-Message-State: AJIora8fiH3j5wwT3qvvH0skIMU8qggn+Iri50h+SXWsS4jzL9gFG9iG iQe2YUXg9VS2AVtlod9m7wQdirlKgBm5OcCzzNOcOku9WsRyOQ== X-Google-Smtp-Source: AGRyM1vWRjI7oNaCAuW/+7+rNcsM2E/uT4LqDwPzpdSrbZzbTYxyBtLhRUnOItqwTQQ8inktCXyKF4Ylqk3KHABggXQ= X-Received: by 2002:a05:6870:b254:b0:ec:6ca4:c89f with SMTP id b20-20020a056870b25400b000ec6ca4c89fmr11967926oam.272.1657930722990; Fri, 15 Jul 2022 17:18:42 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <32dc6f5b56a749f9b8e26330f9f2e8e0@lerctr.org> <51ef4fe0c8c5bbe251d3e75084847a6e@lerctr.org> In-Reply-To: From: Mehmet Erol Sanliturk Date: Sat, 16 Jul 2022 03:18:06 +0300 Message-ID: Subject: Re: limits.conf/stacksize doesn't seem to work? To: Mark Johnston Cc: Larry Rosenman , Freebsd current Content-Type: multipart/alternative; boundary="000000000000ce5f9305e3e1137c" X-Rspamd-Queue-Id: 4Ll8376hCPz3Mww X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=F2UQakeH; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of m.e.sanliturk@gmail.com designates 2001:4860:4864:20::2d as permitted sender) smtp.mailfrom=m.e.sanliturk@gmail.com X-Spamd-Result: default: False [-1.23 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.92)[-0.923]; NEURAL_SPAM_SHORT(0.69)[0.693]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2001:4860:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2001:4860:4864:20::2d:from]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TAGGED_FROM(0.00)[]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-current]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --000000000000ce5f9305e3e1137c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jul 16, 2022 at 1:32 AM Mark Johnston wrote: > On Fri, Jul 15, 2022 at 05:26:09PM -0500, Larry Rosenman wrote: > > On 07/15/2022 5:24 pm, Mark Johnston wrote: > > > On Fri, Jul 15, 2022 at 05:21:27PM -0500, Larry Rosenman wrote: > > >> On 07/15/2022 5:18 pm, Mark Johnston wrote: > > >> > On Fri, Jul 15, 2022 at 05:04:18PM -0500, Larry Rosenman wrote: > > >> >> I'm using the following kernel config: > > >> >> [...] > > >> >> and the following login.conf: > > >> >> [...] > > >> >> bacula_dir:\ > > >> >> :stacksize-max=3D68719476736:\ > > >> >> :stacksize-cur=3D68719476736:\ > > >> >> :tc=3Ddaemon: > > >> >> [...] > > >> >> I've updated my (ler) password entry to reference bacula_dir: > > >> >> ler::1001:1001:bacula_dir:0:0:Larry > > >> >> Rosenman:/home/ler:/usr/local/bin/zsh > > >> >> > > >> >> > > >> >> when I ssh in, the stacklimit is still: > > >> >> =E2=9D=AF ulimit -H -s > > >> >> 2097152 > > >> > > > >> > What is the value of the kern.maxssiz sysctl on this system? > > >> > > > >> >> ler in =F0=9F=8C=90 borg in sys/amd64/conf=F0=9F=94=92 on =EE=82= =A0 > ler/freebsd-main-changes:main on > > >> >> =E2=98=81=EF=B8=8F (us-east-1) > > >> >> =E2=9D=AF ulimit -S -s > > >> >> 2097152 > > >> >> > > >> >> ler in =F0=9F=8C=90 borg in sys/amd64/conf=F0=9F=94=92 on =EE=82= =A0 > ler/freebsd-main-changes:main on > > >> >> =E2=98=81=EF=B8=8F (us-east-1) > > >> >> =E2=9D=AF > > >> >> > > >> >> Where does this number come from? What am I missing here? > > >> > > > >> > The stack limit cannot be set to an arbitrarily large number. It > will > > >> > silently be clamped to maxssiz. > > >> > > >> =E2=9D=AF sysctl kern.maxssiz > > >> kern.maxssiz: 2147483648 > > > > > > Then what you're seeing is expected. The kernel is clamping the stac= k > > > segment limit to 2GB. > > > > I assume this is the default for MAXSSIZ? and if I change that in the > > kernel config, it will > > allow bigger? Where is this default defined? > > The default value is platform dependent. On amd64 it's 512MB, so I'm > not sure where your value is coming from. ------------------------------------------------------- > It's defined in a header. > You can set it in the kernel configuration, or as a tunable or sysctl. > > ------------------------------------------------------- My opinion is that , there is some one ( or more ) constant(s) defined elsewhere , because setting MAXSSIZ is NOT WORKING when it is larger than the "unknown" default value ... With my best wishes for all , Mehmet Erol Sanliturk --000000000000ce5f9305e3e1137c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Jul 16, 2022= at 1:32 AM Mark Johnston <markj@fr= eebsd.org> wrote:
On Fri, Jul 15, 2022 at 05:26:09PM -0500, Larry Rosenman wrote:<= br> > On 07/15/2022 5:24 pm, Mark Johnston wrote:
> > On Fri, Jul 15, 2022 at 05:21:27PM -0500, Larry Rosenman wrote: > >> On 07/15/2022 5:18 pm, Mark Johnston wrote:
> >> > On Fri, Jul 15, 2022 at 05:04:18PM -0500, Larry Rosenman= wrote:
> >> >> I'm using the following kernel config:
> >> >> [...]
> >> >> and the following login.conf:
> >> >> [...]
> >> >> bacula_dir:\
> >> >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:stacksize-max=3D68= 719476736:\
> >> >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:stacksize-cur=3D68= 719476736:\
> >> >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:tc=3Ddaemon:
> >> >> [...]
> >> >> I've updated my (ler) password entry to referenc= e bacula_dir:
> >> >> ler:<elided>:1001:1001:bacula_dir:0:0:Larry > >> >> Rosenman:/home/ler:/usr/local/bin/zsh
> >> >>
> >> >>
> >> >> when I ssh in, the stacklimit is still:
> >> >> =E2=9D=AF ulimit -H -s
> >> >> 2097152
> >> >
> >> > What is the value of the kern.maxssiz sysctl on this sys= tem?
> >> >
> >> >> ler in =F0=9F=8C=90 borg in sys/amd64/conf=F0=9F=94= =92 on =EE=82=A0 ler/freebsd-main-changes:main on
> >> >> =E2=98=81=EF=B8=8F=C2=A0 (us-east-1)
> >> >> =E2=9D=AF ulimit -S -s
> >> >> 2097152
> >> >>
> >> >> ler in =F0=9F=8C=90 borg in sys/amd64/conf=F0=9F=94= =92 on =EE=82=A0 ler/freebsd-main-changes:main on
> >> >> =E2=98=81=EF=B8=8F=C2=A0 (us-east-1)
> >> >> =E2=9D=AF
> >> >>
> >> >> Where does this number come from?=C2=A0 What am I mi= ssing here?
> >> >
> >> > The stack limit cannot be set to an arbitrarily large nu= mber.=C2=A0 It will
> >> > silently be clamped to maxssiz.
> >>
> >> =E2=9D=AF sysctl kern.maxssiz
> >> kern.maxssiz: 2147483648
> >
> > Then what you're seeing is expected.=C2=A0 The kernel is clam= ping the stack
> > segment limit to 2GB.
>
> I assume this is the default for MAXSSIZ?=C2=A0 and if I change that i= n the
> kernel config, it will
> allow bigger?=C2=A0 Where is this default defined?

The default value is platform dependent.=C2=A0 On amd64 it's 512MB, so = I'm
not sure where your value is coming from.=C2=A0

=

---------------------------------------------= ----------

=C2=A0
It's defined in a header.
You can set it in the kernel configuration, or as a tunable or sysctl.


-----------------------= --------------------------------


<= div style=3D"font-family:tahoma,sans-serif;font-size:large" class=3D"gmail_= default">My opinion is that , there is some one ( or more ) constant(s)
defined elsewhere , because

setting=C2=A0 MAXSSIZ=C2=A0 is=C2=A0 NOT WORKING when it is lar= ger than

the "unknown" default= value ...


With my b= est wishes for all ,

Mehmet Erol Sanlitu= rk






=C2=A0
--000000000000ce5f9305e3e1137c--