Re: package upgrade strategy
Date:Thu, 28 Sep 2017 22:20:50 +0200 (CEST) From:r0ller Message-ID: | but I hoped that there's a way to avoid compiling relatively big programs | (like seamonkey) in a case when I just want to check something out [...] There is - you can keep using the binary packages, for everything that still exists in pkgsrc (and for which binary packages are available). You just need to use the sources for midori (or any other package that has been deleted) because there are no new binary packages being produced for that. For everything else you just do binary package upgrades, then when everything is in place (which will have resulted in midori having been deleted) you just compile your copy of that (using the old pkgsrc directory for it) from sources. As long as it continues to build, that should be easy enough. Of course, over time, that gets less and less likely, unless you are upgrading it yourself. If you want to protect it so you have a binary that will work like it does now, regardless of anything else that happens, you should be able to make that work, by setting up an entirely separate /usr/pkg tree (ie: storing it someplace else) - get a version of pkgsrc that includes midori (an older one than current) change the PKG_DBDIR and LOCALBASE / PREFIX, and build just midori from source with those settings (which will also build all of its dependencies, since in that tree, nothing will exist yet). Once that's done, simply leave that tree alone forever, and never touch it again. It will remain completely independent of anything that is normally done with pkgsrc, not influencing it at all. In the regular /usr/pkg you just keep doing binary pkg_add pkg_delete ... as desired to install and delete packages you want to test. kre ps: "kids" is perfectly OK to use at least for this native English speaker.
Re: smbd (samba) opens too many files (fstat)
Christos Zoulas schrieb: In article <516d48e1-48d6-794d-b491-c7a66ddd2...@teccmail.de>, Andreas Beck wrote: Hello, one of my samba-servers opens too many files until notification "Too many open files) from the system. fstat | grep smbd |wc -l 1704 after 2h. Is there a way, to reduce open files in samba, or must I set more descriptors? I think, 1704 open files, while copying 5GB small files, does not look good. Regards, Andreas fstat: ... root smbd 538 816* internet stream tcp root smbd 538 817* internet stream tcp root smbd 538 818* internet stream tcp root smbd 538 819* internet stream tcp root smbd 538 820* internet stream tcp root smbd 538 821* internet stream tcp root smbd 538 822* internet stream tcp root smbd 538 823* internet stream tcp root smbd 538 824* internet stream tcp root smbd 538 825* internet stream tcp root smbd 538 826* internet stream tcp root smbd 538 827* internet stream tcp root smbd 538 828* internet stream tcp root smbd 538 829* internet stream tcp root smbd 538 830* internet stream tcp root smbd 538 831* internet stream tcp root smbd 538 832* internet stream tcp root smbd 538 833* internet stream tcp root smbd 538 834* internet stream tcp root smbd 538 835* internet stream tcp root smbd 538 836* internet stream tcp root smbd 538 837* internet stream tcp root smbd 538 838* internet stream tcp root smbd 538 839* internet stream tcp root smbd 538 840* internet stream tcp root smbd 538 841* internet stream tcp root smbd 538 842* internet stream tcp root smbd 538 843* internet stream tcp root smbd 538 844* internet stream tcp root smbd 538 845* internet stream tcp root smbd 538 846* internet stream tcp root smbd 538 847* internet stream tcp root smbd 538 848* internet stream tcp root smbd 538 849* internet stream tcp from smb.conf(5) max open files (G) This parameter limits the maximum number of open files that one smbd(8) file serving process may have open for a client at any one time. The This parameter can be set very high (16404) as Samba uses only one bit per unopened file. Setting this parameter lower than 16404 will cause Samba to complain and set this value back to the minimum of 16404, as Windows 7 depends on this number of open file handles being available. The limit of the number of open files is usually set by the UNIX per-process file descriptor limit rather than this parameter so you should never need to touch this parameter. Default: max open files = 16404 christos Thanks!
Re: smbd (samba) opens too many files (fstat)
This problem exists also only on one server, why I could not clarify so far and have also built the latest package, without success. When I restart smbd, then fstat (open files) is okay again. Regards, Andreas Andreas Beck schrieb: Hello, one of my samba-servers opens too many files until notification "Too many open files) from the system. fstat | grep smbd |wc -l 1704 after 2h. Is there a way, to reduce open files in samba, or must I set more descriptors? I think, 1704 open files, while copying 5GB small files, does not look good. Regards, Andreas fstat: ... root smbd 538 816* internet stream tcp root smbd 538 817* internet stream tcp root smbd 538 818* internet stream tcp root smbd 538 819* internet stream tcp root smbd 538 820* internet stream tcp root smbd 538 821* internet stream tcp root smbd 538 822* internet stream tcp root smbd 538 823* internet stream tcp root smbd 538 824* internet stream tcp root smbd 538 825* internet stream tcp root smbd 538 826* internet stream tcp root smbd 538 827* internet stream tcp root smbd 538 828* internet stream tcp root smbd 538 829* internet stream tcp root smbd 538 830* internet stream tcp root smbd 538 831* internet stream tcp root smbd 538 832* internet stream tcp root smbd 538 833* internet stream tcp root smbd 538 834* internet stream tcp root smbd 538 835* internet stream tcp root smbd 538 836* internet stream tcp root smbd 538 837* internet stream tcp root smbd 538 838* internet stream tcp root smbd 538 839* internet stream tcp root smbd 538 840* internet stream tcp root smbd 538 841* internet stream tcp root smbd 538 842* internet stream tcp root smbd 538 843* internet stream tcp root smbd 538 844* internet stream tcp root smbd 538 845* internet stream tcp root smbd 538 846* internet stream tcp root smbd 538 847* internet stream tcp root smbd 538 848* internet stream tcp root smbd 538 849* internet stream tcp ...
Re: smbd (samba) opens too many files (fstat)
In article <516d48e1-48d6-794d-b491-c7a66ddd2...@teccmail.de>, Andreas Beck wrote: >Hello, > >one of my samba-servers opens too many files until notification "Too >many open files) from the system. > >fstat | grep smbd |wc -l >1704 > >after 2h. > >Is there a way, to reduce open files in samba, or must I set more >descriptors? >I think, 1704 open files, while copying 5GB small files, does not look good. > >Regards, >Andreas > >fstat: >... >root smbd 538 816* internet stream tcp >root smbd 538 817* internet stream tcp >root smbd 538 818* internet stream tcp >root smbd 538 819* internet stream tcp >root smbd 538 820* internet stream tcp >root smbd 538 821* internet stream tcp >root smbd 538 822* internet stream tcp >root smbd 538 823* internet stream tcp >root smbd 538 824* internet stream tcp >root smbd 538 825* internet stream tcp >root smbd 538 826* internet stream tcp >root smbd 538 827* internet stream tcp >root smbd 538 828* internet stream tcp >root smbd 538 829* internet stream tcp >root smbd 538 830* internet stream tcp >root smbd 538 831* internet stream tcp >root smbd 538 832* internet stream tcp >root smbd 538 833* internet stream tcp >root smbd 538 834* internet stream tcp >root smbd 538 835* internet stream tcp >root smbd 538 836* internet stream tcp >root smbd 538 837* internet stream tcp >root smbd 538 838* internet stream tcp >root smbd 538 839* internet stream tcp >root smbd 538 840* internet stream tcp >root smbd 538 841* internet stream tcp >root smbd 538 842* internet stream tcp >root smbd 538 843* internet stream tcp >root smbd 538 844* internet stream tcp >root smbd 538 845* internet stream tcp >root smbd 538 846* internet stream tcp >root smbd 538 847* internet stream tcp >root smbd 538 848* internet stream tcp >root smbd 538 849* internet stream tcp from smb.conf(5) max open files (G) This parameter limits the maximum number of open files that one smbd(8) file serving process may have open for a client at any one time. The This parameter can be set very high (16404) as Samba uses only one bit per unopened file. Setting this parameter lower than 16404 will cause Samba to complain and set this value back to the minimum of 16404, as Windows 7 depends on this number of open file handles being available. The limit of the number of open files is usually set by the UNIX per-process file descriptor limit rather than this parameter so you should never need to touch this parameter. Default: max open files = 16404 christos
smbd (samba) opens too many files (fstat)
Hello, one of my samba-servers opens too many files until notification "Too many open files) from the system. fstat | grep smbd |wc -l 1704 after 2h. Is there a way, to reduce open files in samba, or must I set more descriptors? I think, 1704 open files, while copying 5GB small files, does not look good. Regards, Andreas fstat: ... root smbd 538 816* internet stream tcp root smbd 538 817* internet stream tcp root smbd 538 818* internet stream tcp root smbd 538 819* internet stream tcp root smbd 538 820* internet stream tcp root smbd 538 821* internet stream tcp root smbd 538 822* internet stream tcp root smbd 538 823* internet stream tcp root smbd 538 824* internet stream tcp root smbd 538 825* internet stream tcp root smbd 538 826* internet stream tcp root smbd 538 827* internet stream tcp root smbd 538 828* internet stream tcp root smbd 538 829* internet stream tcp root smbd 538 830* internet stream tcp root smbd 538 831* internet stream tcp root smbd 538 832* internet stream tcp root smbd 538 833* internet stream tcp root smbd 538 834* internet stream tcp root smbd 538 835* internet stream tcp root smbd 538 836* internet stream tcp root smbd 538 837* internet stream tcp root smbd 538 838* internet stream tcp root smbd 538 839* internet stream tcp root smbd 538 840* internet stream tcp root smbd 538 841* internet stream tcp root smbd 538 842* internet stream tcp root smbd 538 843* internet stream tcp root smbd 538 844* internet stream tcp root smbd 538 845* internet stream tcp root smbd 538 846* internet stream tcp root smbd 538 847* internet stream tcp root smbd 538 848* internet stream tcp root smbd 538 849* internet stream tcp ...
Re: proc.curproc.rlimit.descriptors.hard/soft can not be increased
On Fri, 29 Sep 2017, Andreas Beck wrote: Okay, ive done the job by editing /etc/login.conf. Andreas Beck schrieb: Hello, ive a Problem with 8.0_BETA and increasing proc.curproc.rlimit.descriptors.hard and proc.curproc.rlimit.descriptors.soft When I do "sysctl -w" or in /etc/sysctl.conf the values cant be increased. Increasing of kern.maxfiles is possible. Your problem is that curproc is the current process (the PID of sysctl -w command which is, of course, transitory). Editing login.conf is the correct fix (or you can add it to the relevant /etc/rc.conf.d file as the launched process will inherit it from its parent). -- Stephen
Re: proc.curproc.rlimit.descriptors.hard/soft can not be increased
Okay, ive done the job by editing /etc/login.conf. Andreas Beck schrieb: Hello, ive a Problem with 8.0_BETA and increasing proc.curproc.rlimit.descriptors.hard and proc.curproc.rlimit.descriptors.soft When I do "sysctl -w" or in /etc/sysctl.conf the values cant be increased. Increasing of kern.maxfiles is possible. Best Regards, Andreas
proc.curproc.rlimit.descriptors.hard/soft can not be increased
Hello, ive a Problem with 8.0_BETA and increasing proc.curproc.rlimit.descriptors.hard and proc.curproc.rlimit.descriptors.soft When I do "sysctl -w" or in /etc/sysctl.conf the values cant be increased. Increasing of kern.maxfiles is possible. Best Regards, Andreas
Re: package upgrade strategy
Hi All,
Thanks for all your answers (Alistair, Brad, Jeff, Jeremy)! They all seem to
point in one direction i.e. to use pkgsrc with which I don't have any problem.
I'm kind of used to it but I hoped that there's a way to avoid compiling
relatively big programs (like seamonkey) in a case when I just want to check
something out and get rid of it if it does not fit the bill. The scenario is
something like that I have a 10 years old desktop for our kids (some say this
word is negative for native English speakers, I'm not one of them so please,
forgive) to play online flash games, watch youtube videos, etc. with 3gb ram,
intel core2 conroe cpu with 1 core+igp and a conroe asrock board which all
serves pretty well at their age for this purpose -at least with NetBSD;) Midori
did fit the bill for everything they wanted till they bumped into codecombat
which doesn't work. So I wanted to quickly check out another browser and this
is exactly when I don't have time to compile anything:) As mentioned, by
checking out the earlier 7.0 Q1 repo helped with seamonkey and codecombat runs
fine in that but in such cases compiling each browser till I find the right one
is not an option. I mean, before seamonkey I also checked out epiphany and
firefox, which have the same bug as midori in that online game. Finding out
that seamonkey fits the bill took roughly 15 mins, but compiling three browsers
would have taken a lot more than that. Don't get me wrong, in general I agree
with all your suggestions, I just hoped that there's still a way to keep
different versions of pkgs in parallel.
Best regards,
r0ller
Eredeti levél
Feladó: Alistair Crooks < a...@pkgsrc.org (Link -> mailto:a...@pkgsrc.org) >
Dátum: 2017 szeptember 28 18:20:31
Tárgy: Re: package upgrade strategy
Címzett: Jeff_W < j...@sdf.org (Link -> mailto:j...@sdf.org) >
On 28 September 2017 at 08:40, Jeff_W wrote:
> % cd /pkgsrc/foo/pkg-A
> % sudo make clean && sudo make replace
>
> If the above breaks pkg-C:
>
> % cd /pkgsrc/foo/pkg-C
> % sudo make clean && sudo make clean-depends && sudo make update
Orthogonal to this discussion - pkgsrc was modified to use
just-in-time su in the early 2000s, and avoids interesting issues like
fetching sources as root. You are definitely encouraged to use it.
If you'd prefer to use sudo, rather than su, put this in your etc/mk.conf:
.if exists(${LOCALBASE}/bin/sudo)
SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
.endif
Best,
Alistair
Re: nss compile error
Riccardo Mottola writes: > Hi, > Hello Riccardo! > I am upgrading packages on my 7.1 x86 machine and nss fails to update with: > > [...] > verified/hacl_curve25519_64.c: In function 'Hacl_Bignum_Fmul_fmul_': > verified/hacl_curve25519_64.c:241:5: error: 'for' loop initial > declarations are only allowed in C99 mode > for (uintmax_t _i = 0; _i < (uint32_t)5; ++_i) > ^ > verified/hacl_curve25519_64.c:241:5: note: use option -std=c99 or > -std=gnu99 to compile your code > > anyone else? Just a compiler misdetection/configuration in the makefiles? > [...] I haven't seen it but I guess that adding: USE_LANGUAGES= c99 ...will hopefully help! (you can add in before the `USE_TOOLS+= ...' line in pkgsrc/devel/nss/Makefile) Please let us known if that fixes the issue! Thanks!
