jupyter notebook (newbie)

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Hi,

I have to:
..
 diff -u  /usr/pkg/lib/python3.7/site-packages/notebook/notebookapp.py.ORIG
/usr/pkg/lib/python3.7/site-packages/notebook/notebookapp.py
--- /usr/pkg/lib/python3.7/site-packages/notebook/notebookapp.py.ORIG
   2020-01-08 17:34:30.985204645 +0000
+++ /usr/pkg/lib/python3.7/site-packages/notebook/notebookapp.py
 2020-01-09 11:47:30.785620942 +0000
@@ -817,7 +817,7 @@
         """
     )

-    min_open_files_limit = Integer(4096, config=True,
+    min_open_files_limit = Integer(3404, config=True,
         help="""
         Gets or sets a lower bound on the open file handles process resource
         limit. This may need to be increased if you run into an
...

In order to get the above running on -current (yes, it is this way
hardcoded in the package). If 3404 is some magic number required, then
perhaps the package should be patched to run under -current (or,
perhaps, the released and beta versions, I haven't tried). sysctl
wouldn't matter, as it is per process, as far as I understand it; also
/etc/login.conf openfile-cur does not make any difference.

BTW I find it strange that 'sysctl -w
proc.curproc.rlimit.descriptors.hard=4096' succeeds, 'sysctl -w
proc.curproc.rlimit.descriptors.soft={x}' fails for any {x}>3404 and
they both do not do anything - the limits are apparently read-only:

[~]; sysctl proc.curproc.rlimit.descriptors
proc.curproc.rlimit.descriptors.soft = 1024
proc.curproc.rlimit.descriptors.hard = 3404
[~];  sysctl -w proc.curproc.rlimit.descriptors.hard=4096
proc.curproc.rlimit.descriptors.hard: 3404 -> 4096
[~];  sysctl -w proc.curproc.rlimit.descriptors.soft=3405
sysctl: proc.curproc.rlimit.descriptors.soft: Invalid argument
[~];  sysctl -w proc.curproc.rlimit.descriptors.soft=3404
proc.curproc.rlimit.descriptors.soft: 1024 -> 3404
[~]; sysctl proc.curproc.rlimit.descriptors
proc.curproc.rlimit.descriptors.soft = 1024
proc.curproc.rlimit.descriptors.hard = 3404

On a different topic; /sbin/sysctl manual '-f' section states that -f
implies -w; a sysctl script containing a get statement only coredumps
in trim_whitespaces (it either should allow the display <e.g. -w
implied if '=' is present>, or perhaps complain about the wrong
syntax):
...
[~]; cat /home/xci/x.sysctl
#!/sbin/sysctl -f
proc
[~]; /home/xci/x.sysctl
proc.curproc.corename = %n.core
Memory fault(coredump)
[~]; gdb /sbin/sysctl sysctl.core
GNU gdb (GDB) 8.3
...
Reading symbols from /sbin/sysctl...
(No debugging symbols found in /sbin/sysctl)
[New process 1]
Core was generated by `sysctl'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000002cc026c0 in trim_whitespace ()
(gdb) bt
#0  0x000000002cc026c0 in trim_whitespace ()
#1  0x000000002cc0394a in proc_limit ()
#2  0x000000002cc05477 in print_tree ()
#3  0x000000002cc05dba in print_tree ()
#4  0x000000002cc05dba in print_tree ()
#5  0x000000002cc05dba in print_tree ()
#6  0x000000002cc05dba in print_tree ()
#7  0x000000002cc06bd8 in parse ()
#8  0x000000002cc07dca in main ()
...


Chavdar

-- 
----