Re: rc.d problem
Dima Veselov wrote: > On Fri, Jan 18, 2019 at 02:16:31PM +0100, Martin Husemann wrote: >> On Fri, Jan 18, 2019 at 04:07:06PM +0300, Dima Veselov wrote: >> > I have completely no idea why 8.0-STABLE can't take non-integer value. >> Is there a locale issu involved? > > Ahh, magician, how did you got this??? Unbelievable. > > [root@ranir ~]$ export LC_ALL=C > [root@ranir ~]$ sleep 0.05 > [root@ranir ~]$ export LC_ALL=ru_RU.UTF-8 > [root@ranir ~]$ sleep 0.05 > usage: sleep seconds > [root@ranir ~]$ sleep 0,05 > [root@ranir ~]$ > > That means it also work wrong in 8.0. > > So, what shall we do with that now? Maybe its right to get ',' > instead of '.', but I beleive this should not work in commandline. > > I have checked - Linux and FreeBSD sleep do not take ',' with > same locale. Heh, reminds me how printing something from SunOS4 apps used to generate PostScript with locale-specific decimal separator, and PS was very confused by "floating comma" numbers :) -uwe
Re: RISC-V port?
On 18/01/2019 20:38, Chris Hanson wrote: On Jan 17, 2019, at 10:11 AM, Zachary McGrew wrote: The RISC-V port is not complete yet. I have the kernel booting to the point that it wants to mount a root file system, but I am unable to currently build userland and populate a root filesystem. There is ongoing work to import a newer GCC that supports RISC-V code generation, which would allow for this but it's not complete. What about using clang for RISC-V? Hmmm https://www.youtube.com/watch?v=190qlSnCPak https://fosdem.org/2019/schedule/event/riscvllvmclang/ https://fosdem.org/2019/schedule/track/risc_v/ -- Richard
Re: libstdc++.so.7 is missing
On Fri 18 Jan 2019 at 13:00:09 -0600, Robert Nestor wrote: > , because perl-5.28.1 doesn?t build. > It errors out with an internal gcc compiler error using the gcc that > comes with NetBSD 8.0_STABLE. I built perl-5.28.1 on NetBSD/amd64 8.0, as released (so nothing later than that), and for me it built... So maybe there is some difference between those versions that matters here somehow. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- "What good is a Ring of Power \X/ rhialto/at/falu.nl -- if you're unable...to Speak." - Agent Elrond signature.asc Description: PGP signature
Re: RISC-V port?
On Jan 17, 2019, at 10:11 AM, Zachary McGrew wrote: > The RISC-V port is not complete yet. I have the kernel booting to the > point that it wants to mount a root file system, but I am unable to > currently build userland and populate a root filesystem. There is > ongoing work to import a newer GCC that supports RISC-V code generation, > which would allow for this but it's not complete. What about using clang for RISC-V? -- Chris
Re: libstdc++.so.7 is missing
Did a clean checkout of pkgsrc-2018Q4 and tried building a few of the packages, mainly xfce4. If fails, along with about 122 others in my build, because perl-5.28.1 doesn’t build. but perl-5.28.1 is in the binary archives for amd64/8.0_2018Q4 on the server. So it had to build for someone, just doesn’t build from the checked out pkgsrc source. It errors out with an internal gcc compiler error using the gcc that comes with NetBSD 8.0_STABLE. I’m guessing the builds on the server were done with a different version of gcc but that’s not reflected in the package options for perl in the 2018Q4 source.
Re: dhcpcd failure
On Fri, Jan 18, 2019 at 2:09 AM Roy Marples wrote: > > Hi Fred > > On 18/01/2019 06:05, triaxx wrote: > > I experienced a dhcpcd that cannot connect to a Cisco gateway through a > > fresh NetBSD 8.0. I tried dhclient which succeed. > > > > I didn't see relevant diff between MAIN and netbsd-8. > > > > I would like to send a PR but I'm interesting to know what informations > > could be relevant/helping. > > You could try editing /etc/dhcpcd.conf and commenting out duid and using > clientid. If that still fails, try commenting out both. > > If either work, complain to Cisco about their lack of RFC compliance. > Regardless, let me know the outcome please. If it really is a Cisco compliance issue, I'd like to see a wireshark of the failing request and the successful one for my own amusement. This command seems to work on my mac, I'm guessing it will be similar on NetBSD except the interface name: tshark -i en0 -f "udp port 67 or 68" -w dhcp.pcap Andy
Re: rc.d problem
Date:Fri, 18 Jan 2019 14:45:57 +0100 From:Martin Husemann Message-ID: <20190118134557.gf13...@mail.duskware.de> | I think we should set LC_NUMERIC=C in rc.subr or something like that. LC_ALL not LC_NUMERIC, the latter won't override an external setting of LC_ALL. And yes, the sleep should probably be LC_ALL=C /bin/sleep 0.05 which should fix things, without breaking anything else. kre
Re: postfix alternatives on NetBSD / pkgsrc
On Jan 18, 2019 8:16 AM, Mayuresh wrote: > > On Fri, Jan 18, 2019 at 08:03:41AM -0600, Edgar Pettijohn wrote: > > > 554 5.7.1 > > > > Seems like 550 would be a better error code for this situation. > > I was trying to set that (as I noticed gmail didn't complain for a mail > that was bounced "normally" - such as non existent id). > > But struggling to find out an example of how to do it - how do I relate my > reject point with a certain reject code? > > Mayuresh The only way I know is through an access(5) map. But I'm not sure if it can be done with this specific use case. Edgar
Re: postfix alternatives on NetBSD / pkgsrc
On Fri, Jan 18, 2019 at 08:03:41AM -0600, Edgar Pettijohn wrote: > > 554 5.7.1 > > Seems like 550 would be a better error code for this situation. I was trying to set that (as I noticed gmail didn't complain for a mail that was bounced "normally" - such as non existent id). But struggling to find out an example of how to do it - how do I relate my reject point with a certain reject code? Mayuresh
Re: postfix alternatives on NetBSD / pkgsrc
Am 18. Januar 2019 14:49:15 MEZ schrieb Tobias Ulmer : >On Fri, Jan 18, 2019 at 07:50:52AM +0100, Niels Dettenbach (Syndicat IT >& Internet) wrote: >> The security footprint is very good. > >https://www.cvedetails.com/vulnerability-list/vendor_id-10919/product_id-19563/Exim-Exim.html I know the Exim CVEs - we (as many even larger mail service providers worldwide) run EXIM since many years (nearly 20 years now) and had only one real urgent sec flaw to "close" some monthes ago, requiring urgent updates. I remember the "postfix tricks" in the last decade too... The very most of "more dangerous" sounding Exim CVEs describe flaws which require typically special setups and/or all possible features compiled in and/or foreign libraries onto (what a lot of end users with binary distributions typically use, because their distributors compile anything in by default (by docs, this is not the recommened way to install and use Exim) - but no professional mail ISP nor pkgsrc users (as here) does this afaik. So, things are very relative between numbers and the real world...ß) Cheers, niels. -- Niels Dettenbach Syndicat IT & Internet https://www.syndicat.com
Re: postfix alternatives on NetBSD / pkgsrc
On Jan 18, 2019 7:41 AM, Mayuresh wrote: > > On Fri, Jan 18, 2019 at 06:45:06AM -0600, Edgar Pettijohn wrote: > > I think you should post the logs from your postfix test with Gmail > > issue. I bet someone here knows an option to correct it. > > Not much I can see. I think it has more to do with the error code > interpretation by gmail. For other rejects such as mails directed to non > existent users gmail doesn't call the server as misconfigured. > > Jan 18 09:21:15 localhost postfix/smtpd[28050]: connect from > mail-lj1-f177.google.com[209.85.208.177] > Jan 18 09:21:15 localhost postfix/smtpd[28050]: NOQUEUE: reject: RCPT from > mail-lj1-f177.google.com[209.85.208.177]: 554 5.7.1 : > Recipient address rejected: Access denied; from= > to= proto=ESMTP helo= > Jan 18 09:21:16 localhost postfix/smtpd[28050]: disconnect from > mail-lj1-f177.google.com[209.85.208.177] ehlo=1 mail=1 rcpt=0/1 data=0/1 > quit=1 commands=3/5 > > > Gmail bounced to y...@gmail.com says: > > > Message not delivered Your message couldn't be delivered to > x...@myhost.com because the remote server is misconfigured. See technical > details below for more information. > > The response from the remote server was: > > 554 5.7.1 Seems like 550 would be a better error code for this situation. : Recipient address rejected: Access denied > > I have also posted my postfix conf in previous mail. > > Mayuresh
Re: postfix alternatives on NetBSD / pkgsrc
On Fri, Jan 18, 2019 at 02:49:15PM +0100, Tobias Ulmer wrote: > On Fri, Jan 18, 2019 at 07:50:52AM +0100, Niels Dettenbach (Syndicat IT & > Internet) wrote: > > The security footprint is very good. > > https://www.cvedetails.com/vulnerability-list/vendor_id-10919/product_id-19563/Exim-Exim.html I am not an expert in comparing these and I am not taking any side. But let's put both on the table to make a fair comparison: https://www.cvedetails.com/vulnerability-list/vendor_id-8450/product_id-14794/Postfix-Postfix.html Mayuresh
Re: postfix alternatives on NetBSD / pkgsrc
On Fri, Jan 18, 2019 at 07:50:52AM +0100, Niels Dettenbach (Syndicat IT & Internet) wrote: > The security footprint is very good. https://www.cvedetails.com/vulnerability-list/vendor_id-10919/product_id-19563/Exim-Exim.html
Re: rc.d problem
On Fri, Jan 18, 2019 at 04:42:32PM +0300, Dima Veselov wrote: > On Fri, Jan 18, 2019 at 02:16:31PM +0100, Martin Husemann wrote: > > On Fri, Jan 18, 2019 at 04:07:06PM +0300, Dima Veselov wrote: > > > I have completely no idea why 8.0-STABLE can't take non-integer value. > > Is there a locale issu involved? > > Ahh, magician, how did you got this??? Unbelievable. I had a discussion with youri about mate-calculator and the decimal separator earlier today ;-) > [root@ranir ~]$ export LC_ALL=C > [root@ranir ~]$ sleep 0.05 > [root@ranir ~]$ export LC_ALL=ru_RU.UTF-8 > [root@ranir ~]$ sleep 0.05 > usage: sleep seconds > [root@ranir ~]$ sleep 0,05 > [root@ranir ~]$ > > That means it also work wrong in 8.0. I think we should set LC_NUMERIC=C in rc.subr or something like that. Martin
Re: postfix alternatives on NetBSD / pkgsrc
On Fri, Jan 18, 2019 at 06:45:06AM -0600, Edgar Pettijohn wrote: > I think you should post the logs from your postfix test with Gmail > issue. I bet someone here knows an option to correct it. Not much I can see. I think it has more to do with the error code interpretation by gmail. For other rejects such as mails directed to non existent users gmail doesn't call the server as misconfigured. Jan 18 09:21:15 localhost postfix/smtpd[28050]: connect from mail-lj1-f177.google.com[209.85.208.177] Jan 18 09:21:15 localhost postfix/smtpd[28050]: NOQUEUE: reject: RCPT from mail-lj1-f177.google.com[209.85.208.177]: 554 5.7.1 : Recipient address rejected: Access denied; from= to= proto=ESMTP helo= Jan 18 09:21:16 localhost postfix/smtpd[28050]: disconnect from mail-lj1-f177.google.com[209.85.208.177] ehlo=1 mail=1 rcpt=0/1 data=0/1 quit=1 commands=3/5 Gmail bounced to y...@gmail.com says: Message not delivered Your message couldn't be delivered to x...@myhost.com because the remote server is misconfigured. See technical details below for more information. The response from the remote server was: 554 5.7.1 : Recipient address rejected: Access denied I have also posted my postfix conf in previous mail. Mayuresh
Re: rc.d problem
On Fri, Jan 18, 2019 at 02:16:31PM +0100, Martin Husemann wrote: > On Fri, Jan 18, 2019 at 04:07:06PM +0300, Dima Veselov wrote: > > I have completely no idea why 8.0-STABLE can't take non-integer value. > Is there a locale issu involved? Ahh, magician, how did you got this??? Unbelievable. [root@ranir ~]$ export LC_ALL=C [root@ranir ~]$ sleep 0.05 [root@ranir ~]$ export LC_ALL=ru_RU.UTF-8 [root@ranir ~]$ sleep 0.05 usage: sleep seconds [root@ranir ~]$ sleep 0,05 [root@ranir ~]$ That means it also work wrong in 8.0. So, what shall we do with that now? Maybe its right to get ',' instead of '.', but I beleive this should not work in commandline. I have checked - Linux and FreeBSD sleep do not take ',' with same locale. -- Sincerely yours, Dima Veselov Physics R Establishment of Saint-Petersburg University
Re: rc.d problem
On Fri, Jan 18, 2019 at 04:07:06PM +0300, Dima Veselov wrote: > I have completely no idea why 8.0-STABLE can't take non-integer value. Is there a locale issu involved? Martin
dealing with dhcpcd lifetime overflows
Hi, is there an undocumented way to deal with dhcpcd lifetime overflows? So far I have been restarting the network and wpa_supplicant services, and sometimes just the wpa_supplicant service to get a quick fix.
Re: postfix alternatives on NetBSD / pkgsrc
On Jan 18, 2019 2:08 AM, Mayuresh wrote: > > On Fri, Jan 18, 2019 at 07:50:52AM +0100, Niels Dettenbach (Syndicat IT & > Internet) wrote: > > We use EXIM since decades now from small satellite mailer setups to very > > large ISP setups after migrated from sendmail and postfix as they brought > > our hardware down in performance with heavy mail loads. > > > > EXIM is very (!) efficient - especially when build from sources the > > "official" way (what is provided by pkgsrc by build options). This means > > you just compile fucntionality / code into the binary what you really need. > > > Thanks a lot - a first hand account really helps. > > In general searches on comparison between the two, most often claim > postfix to have better performance than exim (some qualify the statement > saying "for large queues" - which does not bother me for my use case, but > in your case you have seen it scaling well as well). > > > The security footprint is very good. > > > > The config is very flexible but of consistent syntax (developed my a > > mathematican - Phillip Hazel) - for me much more transparent then on > > postfix. There are many of good examples and howtos out there which provide > > single config files you could easily adapt and use. But you can split > > config files too if you prefer that. > > By profession I am a in programming languages researchers and have created > many DSLs in my career. I can say in light of whatever little experience > of inventing notations I have, postfix notation does not really sound > intuitive, particularly when the problem domain does not require it to be > that complex. I'll definitely give exim a try on this aspect. > > Mayuresh I prefer opensmtpd. Unfortunately the pkgsrc version is quite old. I like the config it's quite simple. I also like postfix. The only problem with postfix is the overwhelming number of options to research. I think you should post the logs from your postfix test with Gmail issue. I bet someone here knows an option to correct it. Edgar
Re: rc.d problem
On Fri, Jan 18, 2019 at 01:23:12PM +0100, Martin Husemann wrote: > On Fri, Jan 18, 2019 at 03:17:57PM +0300, Dima Veselov wrote: > > > The rc scripts use "sleep 0.05" but not all versions of sleep > > > support non-integral values. > > > > I never replaced original one. The only replacement was done - > > upgrading via build.sh distribution sets. Just checked cvsweb - > > I have recent version of sleep.c > > Where is the rc.d script from? Pkgsrc? This is non-portable, so it > should be fixed in the pkg. No idea why the message did not show up > on earlier versions, maybe one of th sh(1) fixed just made it visible? Yes, but rc.d scripts behave the same way: [root@almaz sleep]$ /etc/rc.d/syslogd restart Stopping syslogd. usage: sleep seconds Starting syslogd. Have no idea why it work that way. Also I am sure this never happened on default installation of 8.0: [root@ranir ~]$ /etc/rc.d/syslogd restart Stopping syslogd. Starting syslogd. -- Sincerely yours, Dima Veselov Physics R Establishment of Saint-Petersburg University
Re: rc.d problem
On Fri, Jan 18, 2019 at 12:25:46PM +, Stephen Borrill wrote: > > > > The rc scripts use "sleep 0.05" but not all versions of sleep > > > > support non-integral values. > > > > > > I never replaced original one. The only replacement was done - > > > upgrading via build.sh distribution sets. Just checked cvsweb - > > > I have recent version of sleep.c > > > > Where is the rc.d script from? Pkgsrc? This is non-portable, so it > > should be fixed in the pkg. No idea why the message did not show up > > on earlier versions, maybe one of th sh(1) fixed just made it visible? > > The sleep is coming form rc.subr, not the rc.d script itself: > > # We want this to be a tight loop for a fast exit > sleep 0.05 > > What does "which sleep" say? Perhaps you've another sleep in an unexpected > location. /bin/sleep only. I've checked /usr/src version which still do not recognize numbers with floating point. -- Sincerely yours, Dima Veselov Physics R Establishment of Saint-Petersburg University
Re: rc.d problem
On Fri, Jan 18, 2019 at 12:25:46PM +, Stephen Borrill wrote: > The sleep is coming form rc.subr, not the rc.d script itself: > > # We want this to be a tight loop for a fast exit > sleep 0.05 Ooops - overlooked that our sleep does handle it. Martin
Re: rc.d problem
On Fri, 18 Jan 2019, Martin Husemann wrote: On Fri, Jan 18, 2019 at 03:17:57PM +0300, Dima Veselov wrote: The rc scripts use "sleep 0.05" but not all versions of sleep support non-integral values. I never replaced original one. The only replacement was done - upgrading via build.sh distribution sets. Just checked cvsweb - I have recent version of sleep.c Where is the rc.d script from? Pkgsrc? This is non-portable, so it should be fixed in the pkg. No idea why the message did not show up on earlier versions, maybe one of th sh(1) fixed just made it visible? The sleep is coming form rc.subr, not the rc.d script itself: # We want this to be a tight loop for a fast exit sleep 0.05 What does "which sleep" say? Perhaps you've another sleep in an unexpected location. -- Stephen
Re: rc.d problem
On Fri, Jan 18, 2019 at 03:17:57PM +0300, Dima Veselov wrote: > > The rc scripts use "sleep 0.05" but not all versions of sleep > > support non-integral values. > > I never replaced original one. The only replacement was done - > upgrading via build.sh distribution sets. Just checked cvsweb - > I have recent version of sleep.c Where is the rc.d script from? Pkgsrc? This is non-portable, so it should be fixed in the pkg. No idea why the message did not show up on earlier versions, maybe one of th sh(1) fixed just made it visible? Martin
Re: rc.d problem
On Fri, Jan 18, 2019 at 06:52:51PM +0700, Robert Elz wrote:
> | Looks like kind a silly problem, but I can't find where it
> | happen.
>
> Do you happen to have some non-standard (ie: not netbsd)
> sleep command installed?
>
> The rc scripts use "sleep 0.05" but not all versions of sleep
> support non-integral values.
I never replaced original one. The only replacement was done -
upgrading via build.sh distribution sets. Just checked cvsweb -
I have recent version of sleep.c
[root@almaz sleep]$ cd /usr/src/bin/sleep/
[root@almaz sleep]$ grep NetBSD Makefile
# $NetBSD: Makefile,v 1.9 1997/08/04 01:13:07 perry Exp $
[root@almaz sleep]$ grep NetBSD sleep.c
/* $NetBSD: sleep.c,v 1.24 2011/08/29 14:51:19 joerg Exp $ */
__RCSID("$NetBSD: sleep.c,v 1.24 2011/08/29 14:51:19 joerg Exp $");
[root@almaz sleep]$ TOOLDIR=/export/build/tools/ make
[root@almaz sleep]$ ./sleep 0.05
usage: sleep seconds
--
Sincerely yours,
Dima Veselov
Physics R Establishment of Saint-Petersburg University
Re: rc.d problem
Date:Fri, 18 Jan 2019 14:00:54 +0300 From:Dima Veselov Message-ID: <20190118110054.GA6665@laura> | Looks like kind a silly problem, but I can't find where it | happen. Do you happen to have some non-standard (ie: not netbsd) sleep command installed? The rc scripts use "sleep 0.05" but not all versions of sleep support non-integral values. kre
Re: rc.d problem
On Fri, Jan 18, 2019 at 11:30:18AM +, Stephen Borrill wrote: > > > > After some 8.0-STABLE upgrades all my NetBSD boxes have problem > > > > with rc.d scripts. They are definitely working, but when script > > > > have to wait for a process it contantly prints that: > > > > > > > > [root@almaz src]$ /etc/rc.d/php_fpm restart > > > > Stopping php_fpm. > > > > usage: sleep seconds > > > > > > Can you try "sh -x /etc/rc.d/php_fpm restart" and log the output? > > Try the following instead: > sh -x /etc/rc.d/php_fpm stop Here it is: [root@almaz src]$ sh -x /etc/rc.d/php_fpm stop + . /etc/rc.subr + ':' 'rc.conf(5)' + ':' 5660 + export RC_PID + nl=' ' + _env_clear_rc_vars=' RC_PID= _rc_pid= _rc_original_stdout_fd= _rc_original_stderr_fd= _rc_postprocessor_fd= ' + _rc_subr_loaded=':' + name=php_fpm + rcvar=php_fpm + command=/usr/pkg/sbin/php-fpm + required_files=/usr/pkg/etc/php-fpm.conf + pidfile=/var/run/php-fpm.pid + sig_reload=USR2 + extra_commands=reload + load_rc_config php_fpm + _command=php_fpm + '[' -z php_fpm ']' + false + . /etc/rc.conf + '[' -r /etc/defaults/rc.conf ']' + . /etc/defaults/rc.conf + /sbin/sysctl -n kern.boothowto 2>/dev/null + '[' 0 '!=' 0 ']' + echo false + command echo false + rc_silent=false + rc_silent_cmd=twiddle + rc_rcorder_flags='' + rc_directories=/etc/rc.d + do_rcshutdown=YES + rcshutdown_rcorder_flags='' + rcshutdown_timeout='' + hostname='' + defaultroute='' + defaultroute6='' + domainname='' + critical_filesystems_local='OPTIONAL:/var' + critical_filesystems_remote='OPTIONAL:/usr' + no_swap=NO + swapoff=YES + ccd=YES + raidframe=YES + cgd=YES + lvm=NO + savecore=YES savecore_flags=-z + savecore_dir=/var/crash + resize_root=NO + per_user_tmp=NO + per_user_tmp_dir=/private/tmp + clear_tmp=YES + update_motd=YES + dmesg=YES dmesg_flags='' + accounting=NO + newsyslog=NO newsyslog_flags='' + quota=YES + ldconfig=YES + sysdb=YES + rndctl=NO rndctl_flags='' + gpio=NO + modules=YES + rtclocaltime=NO + fsck_flags=-p + securelevel='' + ifconfig_wait_dad_flags='-w 15 -W 5' + mdnsd=NO + npf=NO + npfd=NO + ipfilter=NO ipfilter_flags='' + ipnat=NO + ipfs=NO ipfs_flags='' + ipsec=NO + ipmon=NO ipmon_flags=-Dns + pf=NO pf_rules=/etc/pf.conf pf_flags='' + pflogd=NO + ftp_proxy=NO + racoon=NO + auto_ifconfig=YES + net_interfaces='' + flushroutes=YES + dhcpcd=NO + dhcpcd_flags=-qM + dhclient=NO + dhclient_flags='' + ntpdate=NO ntpdate_flags='-b -s' + ppp=YES ppp_peers='' + ip6mode=host + ip6uniquelocal=NO + ifwatchd=NO + ifwatchd_flags='-u /etc/ppp/ip-up -d /etc/ppp/ip-down pppoe0' + altqd=NO altqd_flags='' + inetd=YES inetd_flags=-l + identd=NO identd_flags='-b -l -u nobody' + rpcbind=NO rpcbind_flags=-l + syslogd=YES syslogd_flags=-s + cron=YES + named=NO named_flags='' + timed=NO timed_flags='' + ntpd=NO ntpd_flags='' + postfix=YES + lpd=NO lpd_flags=-s + sshd=NO sshd_flags='' + ssh_keygen_flags='' + ftpd=NO ftpd_flags=-ll + httpd=NO httpd_flags='' + httpd_wwwdir=/var/www + httpd_wwwuser=_httpd + routed=NO routed_flags=-q + gated=NO + mrouted=NO mrouted_flags='' + route6d=NO route6d_flags='' + ldpd=NO + rarpd=NO rarpd_flags=-a + bootparamd=NO bootparamd_flags='' + dhcpd=NO dhcpd_flags=-q + dhcrelay=NO dhcrelay_flags='' + rbootd=NO rbootd_flags='' + mopd=NO mopd_flags=-a + ndbootd=NO ndbootd_flags='-s /tftpboot /tftpboot/bootyy' + rtadvd=NO rtadvd_flags='' + isibootd=NO isibootd_flags='' + xfs=NO xfs_flags='' + xdm=NO xdm_flags='' + fccache=YES + ypbind=NO ypbind_flags='' + ypserv=NO ypserv_flags=-d + yppasswdd=NO yppasswdd_flags='' + mountd=NO mountd_flags='' + nfs_client=NO + nfs_server=NO + nfsd_flags='' + lockd=NO lockd_flags='' + statd=NO statd_flags='' + amd=NO amd_flags='-l syslog -x error,noinfo,nostats' + amd_dir=/amd + kdc=NO kdc_flags=--detach + iscsi_target=NO iscsi_target_flags='' + iscsid=NO + hostapd=NO hostapd_flags='-B /etc/hostapd.conf' + wpa_supplicant=NO wpa_supplicant_flags='' + isdnd=NO isdnd_flags='' + bluetooth=NO + btconfig_devices='' + bthcid=YES bthcid_flags='' + sdpd=YES sdpd_flags='' + rwhod=NO rwhod_flags='-u _rwhod' + devpubd=NO devpubd_flags='' + envsys=NO + apmd=NO apmd_flags='' + powerd=NO powerd_flags='' + screenblank=NO screenblank_flags='' + moused=NO + moused_flags='-p /dev/tty00' + wdogctl=NO + irdaattach=NO + irdaattach_flags=tty00 + wscons=NO wscons_flags='' + wsmoused=NO wsmoused_flags='' + tpctl=NO tpctl_flags='' + mixerctl=NO mixerctl_mixers='' + virecover=YES + veriexec=NO + veriexec_strict=0 + veriexec_verbose=0 + veriexec_flags=-k + random_seed=YES + makemandb=YES + blacklistd=NO + ip6addrctl=NO + ip6addrctl_policy=auto + ip6addrctl_verbose=NO + unbound=NO + unbound_chrootdir=/var/chroot/unbound + nsd=NO + nsd_chrootdir=/var/chroot/nsd + nsd_flags='-t /var/chroot/nsd' + /sbin/sysctl -q machdep.xen + /sbin/sysctl -q hw.acpi.root + powerd=YES + rc_configured=YES + hostname=almaz + sshd=YES + ntpd=YES + cgd=NO + wscons=YES + rwhod=YES + npf=YES + npfd=YES + ipsec=YES + racoon=YES + named_chrootdir=/var/chroot/named/ + named_flags=-4 +
Re: rc.d problem
On Fri, 18 Jan 2019, Dima Veselov wrote: On Fri, Jan 18, 2019 at 12:13:52PM +0100, Martin Husemann wrote: On Fri, Jan 18, 2019 at 02:00:54PM +0300, Dima Veselov wrote: Greetings! After some 8.0-STABLE upgrades all my NetBSD boxes have problem with rc.d scripts. They are definitely working, but when script have to wait for a process it contantly prints that: [root@almaz src]$ /etc/rc.d/php_fpm restart Stopping php_fpm. usage: sleep seconds Can you try "sh -x /etc/rc.d/php_fpm restart" and log the output? No problem. Try the following instead: sh -x /etc/rc.d/php_fpm stop -- Stephen
Re: rc.d problem
On Fri, Jan 18, 2019 at 12:13:52PM +0100, Martin Husemann wrote: > On Fri, Jan 18, 2019 at 02:00:54PM +0300, Dima Veselov wrote: > > Greetings! > > > > After some 8.0-STABLE upgrades all my NetBSD boxes have problem > > with rc.d scripts. They are definitely working, but when script > > have to wait for a process it contantly prints that: > > > > [root@almaz src]$ /etc/rc.d/php_fpm restart > > Stopping php_fpm. > > usage: sleep seconds > > Can you try "sh -x /etc/rc.d/php_fpm restart" and log the output? No problem. [root@almaz src]$ sh -x /etc/rc.d/php_fpm restart + . /etc/rc.subr + ':' 'rc.conf(5)' + ':' 21194 + export RC_PID + nl=' ' + _env_clear_rc_vars=' RC_PID= _rc_pid= _rc_original_stdout_fd= _rc_original_stderr_fd= _rc_postprocessor_fd= ' + _rc_subr_loaded=':' + name=php_fpm + rcvar=php_fpm + command=/usr/pkg/sbin/php-fpm + required_files=/usr/pkg/etc/php-fpm.conf + pidfile=/var/run/php-fpm.pid + sig_reload=USR2 + extra_commands=reload + load_rc_config php_fpm + _command=php_fpm + '[' -z php_fpm ']' + false + . /etc/rc.conf + '[' -r /etc/defaults/rc.conf ']' + . /etc/defaults/rc.conf + /sbin/sysctl -n kern.boothowto 2>/dev/null + '[' 0 '!=' 0 ']' + echo false + command echo false + rc_silent=false + rc_silent_cmd=twiddle + rc_rcorder_flags='' + rc_directories=/etc/rc.d + do_rcshutdown=YES + rcshutdown_rcorder_flags='' + rcshutdown_timeout='' + hostname='' + defaultroute='' + defaultroute6='' + domainname='' + critical_filesystems_local='OPTIONAL:/var' + critical_filesystems_remote='OPTIONAL:/usr' + no_swap=NO + swapoff=YES + ccd=YES + raidframe=YES + cgd=YES + lvm=NO + savecore=YES savecore_flags=-z + savecore_dir=/var/crash + resize_root=NO + per_user_tmp=NO + per_user_tmp_dir=/private/tmp + clear_tmp=YES + update_motd=YES + dmesg=YES dmesg_flags='' + accounting=NO + newsyslog=NO newsyslog_flags='' + quota=YES + ldconfig=YES + sysdb=YES + rndctl=NO rndctl_flags='' + gpio=NO + modules=YES + rtclocaltime=NO + fsck_flags=-p + securelevel='' + ifconfig_wait_dad_flags='-w 15 -W 5' + mdnsd=NO + npf=NO + npfd=NO + ipfilter=NO ipfilter_flags='' + ipnat=NO + ipfs=NO ipfs_flags='' + ipsec=NO + ipmon=NO ipmon_flags=-Dns + pf=NO pf_rules=/etc/pf.conf pf_flags='' + pflogd=NO + ftp_proxy=NO + racoon=NO + auto_ifconfig=YES + net_interfaces='' + flushroutes=YES + dhcpcd=NO + dhcpcd_flags=-qM + dhclient=NO + dhclient_flags='' + ntpdate=NO ntpdate_flags='-b -s' + ppp=YES ppp_peers='' + ip6mode=host + ip6uniquelocal=NO + ifwatchd=NO + ifwatchd_flags='-u /etc/ppp/ip-up -d /etc/ppp/ip-down pppoe0' + altqd=NO altqd_flags='' + inetd=YES inetd_flags=-l + identd=NO identd_flags='-b -l -u nobody' + rpcbind=NO rpcbind_flags=-l + syslogd=YES syslogd_flags=-s + cron=YES + named=NO named_flags='' + timed=NO timed_flags='' + ntpd=NO ntpd_flags='' + postfix=YES + lpd=NO lpd_flags=-s + sshd=NO sshd_flags='' + ssh_keygen_flags='' + ftpd=NO ftpd_flags=-ll + httpd=NO httpd_flags='' + httpd_wwwdir=/var/www + httpd_wwwuser=_httpd + routed=NO routed_flags=-q + gated=NO + mrouted=NO mrouted_flags='' + route6d=NO route6d_flags='' + ldpd=NO + rarpd=NO rarpd_flags=-a + bootparamd=NO bootparamd_flags='' + dhcpd=NO dhcpd_flags=-q + dhcrelay=NO dhcrelay_flags='' + rbootd=NO rbootd_flags='' + mopd=NO mopd_flags=-a + ndbootd=NO ndbootd_flags='-s /tftpboot /tftpboot/bootyy' + rtadvd=NO rtadvd_flags='' + isibootd=NO isibootd_flags='' + xfs=NO xfs_flags='' + xdm=NO xdm_flags='' + fccache=YES + ypbind=NO ypbind_flags='' + ypserv=NO ypserv_flags=-d + yppasswdd=NO yppasswdd_flags='' + mountd=NO mountd_flags='' + nfs_client=NO + nfs_server=NO + nfsd_flags='' + lockd=NO lockd_flags='' + statd=NO statd_flags='' + amd=NO amd_flags='-l syslog -x error,noinfo,nostats' + amd_dir=/amd + kdc=NO kdc_flags=--detach + iscsi_target=NO iscsi_target_flags='' + iscsid=NO + hostapd=NO hostapd_flags='-B /etc/hostapd.conf' + wpa_supplicant=NO wpa_supplicant_flags='' + isdnd=NO isdnd_flags='' + bluetooth=NO + btconfig_devices='' + bthcid=YES bthcid_flags='' + sdpd=YES sdpd_flags='' + rwhod=NO rwhod_flags='-u _rwhod' + devpubd=NO devpubd_flags='' + envsys=NO + apmd=NO apmd_flags='' + powerd=NO powerd_flags='' + screenblank=NO screenblank_flags='' + moused=NO + moused_flags='-p /dev/tty00' + wdogctl=NO + irdaattach=NO + irdaattach_flags=tty00 + wscons=NO wscons_flags='' + wsmoused=NO wsmoused_flags='' + tpctl=NO tpctl_flags='' + mixerctl=NO mixerctl_mixers='' + virecover=YES + veriexec=NO + veriexec_strict=0 + veriexec_verbose=0 + veriexec_flags=-k + random_seed=YES + makemandb=YES + blacklistd=NO + ip6addrctl=NO + ip6addrctl_policy=auto + ip6addrctl_verbose=NO + unbound=NO + unbound_chrootdir=/var/chroot/unbound + nsd=NO + nsd_chrootdir=/var/chroot/nsd + nsd_flags='-t /var/chroot/nsd' + /sbin/sysctl -q machdep.xen + /sbin/sysctl -q hw.acpi.root + powerd=YES + rc_configured=YES + hostname=almaz + sshd=YES + ntpd=YES + cgd=NO + wscons=YES + rwhod=YES + npf=YES + npfd=YES + ipsec=YES + racoon=YES + named_chrootdir=/var/chroot/named/ + named_flags=-4 + named=YES +
Re: rc.d problem
On Fri, Jan 18, 2019 at 02:00:54PM +0300, Dima Veselov wrote: > Greetings! > > After some 8.0-STABLE upgrades all my NetBSD boxes have problem > with rc.d scripts. They are definitely working, but when script > have to wait for a process it contantly prints that: > > [root@almaz src]$ /etc/rc.d/php_fpm restart > Stopping php_fpm. > usage: sleep seconds Can you try "sh -x /etc/rc.d/php_fpm restart" and log the output? Martin
rc.d problem
Greetings! After some 8.0-STABLE upgrades all my NetBSD boxes have problem with rc.d scripts. They are definitely working, but when script have to wait for a process it contantly prints that: [root@almaz src]$ /etc/rc.d/php_fpm restart Stopping php_fpm. usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds usage: sleep seconds Starting php_fpm. Looks like kind a silly problem, but I can't find where it happen. -- Sincerely yours, Dima Veselov Physics R Establishment of Saint-Petersburg University
Re: dhcpcd failure
Hi Fred On 18/01/2019 06:05, triaxx wrote: I experienced a dhcpcd that cannot connect to a Cisco gateway through a fresh NetBSD 8.0. I tried dhclient which succeed. I didn't see relevant diff between MAIN and netbsd-8. I would like to send a PR but I'm interesting to know what informations could be relevant/helping. You could try editing /etc/dhcpcd.conf and commenting out duid and using clientid. If that still fails, try commenting out both. If either work, complain to Cisco about their lack of RFC compliance. Regardless, let me know the outcome please. Roy
Re: libstdc++.so.7 is missing
I'm away from home for a few days and will try to fix my system as soon as possible. Still, I believe that something went wrong with the builds for the Q4 release. This a screenshot over firefox for the Q3 list of packages, https://imgur.com/GV71xgT and here is the same for Q4, https://imgur.com/0VOXYik So it might be that when I removed firefox and installed midori the refered lib was removed as an orphan package, but I can't re-install firefox simply because its not there
Re: postfix alternatives on NetBSD / pkgsrc
On Fri, Jan 18, 2019 at 07:50:52AM +0100, Niels Dettenbach (Syndicat IT & Internet) wrote: > We use EXIM since decades now from small satellite mailer setups to very > large ISP setups after migrated from sendmail and postfix as they brought our > hardware down in performance with heavy mail loads. > > EXIM is very (!) efficient - especially when build from sources the > "official" way (what is provided by pkgsrc by build options). This means you > just compile fucntionality / code into the binary what you really need. Thanks a lot - a first hand account really helps. In general searches on comparison between the two, most often claim postfix to have better performance than exim (some qualify the statement saying "for large queues" - which does not bother me for my use case, but in your case you have seen it scaling well as well). > The security footprint is very good. > > The config is very flexible but of consistent syntax (developed my a > mathematican - Phillip Hazel) - for me much more transparent then on postfix. > There are many of good examples and howtos out there which provide single > config files you could easily adapt and use. But you can split config files > too if you prefer that. By profession I am a in programming languages researchers and have created many DSLs in my career. I can say in light of whatever little experience of inventing notations I have, postfix notation does not really sound intuitive, particularly when the problem domain does not require it to be that complex. I'll definitely give exim a try on this aspect. Mayuresh
