Re: WireGuard for FreeBSD
On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld wrote: > We now have a release, so the full instructions for the packages are: > > 1. wireguard-tools, providing wg(8) and wg-quick(8) > Runtime dependencies: bash, wireguard-go > Buildtime dependencies: gmake, c compiler, libc > Build: gmake -C src/tools WITH_WGQUICK=yes > Install: gmake -C src/tools PREFIX=/usr/local install > URL: https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20180524.tar.xz > > 2. wireguard-go > Runtime dependencies: libc > Buildtime dependencies: gmake, go, dep > Build: gmake > Install: gmake PREFIX=/usr/local install > URL: > https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.20180524.tar.xz > > I believe decke is already working on a port in his repository. Ports are already updated on github. I will do some final checks and expect to commit the wireguard ports to the official tree today. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Pause pkg install messages
Hi The first thing me and probably many other do after install is pkg install xxx yyy zzz from console (meaning no scrollback buffer). With xorg and friends this means hundreds of packets. After install all the pkg messages are display and most of sometimes very valuable information is just scrolled away. Is there an easy way to fix* this by piping the output through less or something to pause for each screen so that the messages just aren't scrolled away? In addition to that it would be nice (if it's not already done) to store this information in a log file somewhere so that one can revisit and see what needs to be manually configured for each installed package. *by fix I mean something that does not put the burden on the user. Cheers /Johannes ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, 24 May 2018 09:08:17 +0100 Johannes Lundberg wrote: > In addition to that it would be nice (if it's not already done) to > store this information in a log file somewhere so that one can > revisit and see what needs to be manually configured for each > installed package. I have this in syslog.conf: !pkg,pkg-static *.* /var/log/pkg.log ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On 24.05.2018 15:08, Johannes Lundberg wrote: > Hi > > The first thing me and probably many other do after install is > pkg install xxx yyy zzz > from console (meaning no scrollback buffer). > > With xorg and friends this means hundreds of packets. After install all the > pkg messages are display and most of sometimes very valuable information is > just scrolled away. > > Is there an easy way to fix* this by piping the output through less or > something to pause for each screen so that the messages just aren't > scrolled away? > > In addition to that it would be nice (if it's not already done) to store > this information in a log file somewhere so that one can revisit and see > what needs to be manually configured for each installed package. > > *by fix I mean something that does not put the burden on the user. Installation/deinstallation of packages logged by default to /var/log/messages. Syscons console has scrollback buffer by default. If vt(4) has not, that's regression after syscons and should be fixed in the vt. Also, one can have, for tcsh: alias pkg 'script -a /var/log/pkg.log pkg-static' So "pkg install xxx yyy zzz" adds fulls output to specified file. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > On Thu, 24 May 2018 09:08:17 +0100 > Johannes Lundberg wrote: > > > In addition to that it would be nice (if it's not already done) to > > store this information in a log file somewhere so that one can > > revisit and see what needs to be manually configured for each > > installed package. > > I have this in syslog.conf: > > !pkg,pkg-static > *.* /var/log/pkg.log > Thanks for the tip. I'll use this. However, someone who knows about this probably know how to manually configure their system already. I want to make sure first timers and newbies don't miss important messages on how to configure the system. Often we get inquires about stuff that is clearly described in the pkg message and bug reports that are a consequence of wrong configuration. How can we make this more clear so that it is not missed? > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
Johannes Lundberg wrote on 2018/05/24 11:03: On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: On Thu, 24 May 2018 09:08:17 +0100 Johannes Lundberg wrote: In addition to that it would be nice (if it's not already done) to store this information in a log file somewhere so that one can revisit and see what needs to be manually configured for each installed package. I have this in syslog.conf: !pkg,pkg-static *.* /var/log/pkg.log I think only changes are logged, not messages: Apr 26 23:50:22 maja pkg: p5-DBI reinstalled: 1.641 -> 1.641 Apr 26 23:50:22 maja pkg: mariadb101-client upgraded: 10.1.31 -> 10.1.32_2 Apr 26 23:50:22 maja pkg: libnghttp2 upgraded: 1.31.0 -> 1.31.1 Thanks for the tip. I'll use this. However, someone who knows about this probably know how to manually configure their system already. I want to make sure first timers and newbies don't miss important messages on how to configure the system. Often we get inquires about stuff that is clearly described in the pkg message and bug reports that are a consequence of wrong configuration. How can we make this more clear so that it is not missed? As Eugene already noted - syscons has scrollback buffer. Did you tried "Scroll Lock" on your keyboard? If you need to re-show message of any installed package, "pkg info -D" (or pkg info --pkg-message) is your friend. Nothing is lost. You can view it anytime. # pkg info -D mariadb101-server mariadb101-server-10.1.33: Always: Remember to run mysql_upgrade (with the optional --datadir= flag) the first time you start the MySQL server after an upgrade from an earlier version. MariaDB respects hier(7) and doesn't check /etc and /etc/mysql for my.cnf. Please move existing my.cnf files from those paths to /usr/local/etc and /usr/local/etc/mysql. This port does NOT include the mytop perl script, this is included in the MariaDB tarball but the most recent version can be found in the databases/mytop port Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On 05/24/18 10:08, Johannes Lundberg wrote: > Hi > > The first thing me and probably many other do after install is > pkg install xxx yyy zzz > from console (meaning no scrollback buffer). FreeBSD console does have a scrollback buffer. just press scroll-lock and use the page up/page down buttons to move around the buffer. By default the buffer isn't very big so it could not suffice if the output is actually very very long. it can be configured using vidcontrol(1). > > With xorg and friends this means hundreds of packets. After install all the > pkg messages are display and most of sometimes very valuable information is > just scrolled away. > > Is there an easy way to fix* this by piping the output through less or > something to pause for each screen so that the messages just aren't > scrolled away? script(1) could save it to a file in realtime and you can read it from another terminal, and leave you a file with all the output. > > In addition to that it would be nice (if it's not already done) to store > this information in a log file somewhere so that one can revisit and see > what needs to be manually configured for each installed package. pkg generates log lines about what it installs updates, which can be found in /var/log/messages with default syslogd configuration, for example: May 24 08:37:55 *** pkg[6058]: thunderbird upgraded: 52.8.0 -> 52.8.0_5 May 24 08:37:55 *** pkg[6058]: p5-DateTime upgraded: 1.48 -> 1.49 May 24 08:37:56 *** pkg[6058]: java-zoneinfo upgraded: 2018.d -> 2018.e May 24 08:38:02 *** pkg[6058]: firefox upgraded: 60.0.1,1 -> 60.0.1_3,1 May 24 08:38:02 *** pkg[6058]: devcpu-data upgraded: 1.16_1 -> 1.16_2 -- Guido Falsi ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, May 24, 2018 at 10:21 AM Miroslav Lachman <000.f...@quip.cz> wrote: > Johannes Lundberg wrote on 2018/05/24 11:03: > > On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > > > >> On Thu, 24 May 2018 09:08:17 +0100 > >> Johannes Lundberg wrote: > >> > >>> In addition to that it would be nice (if it's not already done) to > >>> store this information in a log file somewhere so that one can > >>> revisit and see what needs to be manually configured for each > >>> installed package. > >> > >> I have this in syslog.conf: > >> > >> !pkg,pkg-static > >> *.* /var/log/pkg.log > > I think only changes are logged, not messages: > > Apr 26 23:50:22 maja pkg: p5-DBI reinstalled: 1.641 -> 1.641 > Apr 26 23:50:22 maja pkg: mariadb101-client upgraded: 10.1.31 -> 10.1.32_2 > Apr 26 23:50:22 maja pkg: libnghttp2 upgraded: 1.31.0 -> 1.31.1 > > > Thanks for the tip. I'll use this. > > However, someone who knows about this probably know how to manually > > configure their system already. > > > > I want to make sure first timers and newbies don't miss important > messages > > on how to configure the system. > > > > Often we get inquires about stuff that is clearly described in the pkg > > message and bug reports that are a consequence of wrong configuration. > > How can we make this more clear so that it is not missed? > > As Eugene already noted - syscons has scrollback buffer. Did you tried > "Scroll Lock" on your keyboard? > > If you need to re-show message of any installed package, "pkg info -D" > (or pkg info --pkg-message) is your friend. Nothing is lost. You can > view it anytime. > If you're in virtualbox on a laptop, you seldom have scroll lock unless you map it manually (which is not easy to know how to do). And, yes you can review the messages later but how do you know which of the 100's of package had important messages for you? Often when I install 100's of package I walk away from the computer and when I come back all the messages except the very last one or two have scrolled by. I think we should have a pager that says something like "please carefully read through these messages", halt the output and let's you scroll one page or pkg at the time. Even better, a Y/N question asking the user if they want configuration to be done for them where it makes sense (but that's a bigger project). > > > # pkg info -D mariadb101-server > mariadb101-server-10.1.33: > Always: > > > Remember to run mysql_upgrade (with the optional --datadir= flag) > the first time you start the MySQL server after an upgrade from an > earlier version. > > MariaDB respects hier(7) and doesn't check /etc and /etc/mysql for > my.cnf. Please move existing my.cnf files from those paths to > /usr/local/etc and /usr/local/etc/mysql. > > This port does NOT include the mytop perl script, this is included in > the MariaDB tarball but the most recent version can be found in the > databases/mytop port > > > > Miroslav Lachman > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Logstash failing to process messages
I have seen the same issue. In my case however, I had about OOM caused by parsing long grok patterns. I didn't have these in 5.3 either so I suspect it's a memory leak somewhere. I have since upgraded everything to 6.x and am waiting to see if the same issue persists. Regards, Benny Goemans On 23-05-2018 17:23, Kernel Panic wrote: Hello, I'll just list the versions before I start: FreeBSD 11.1 Logstash 6.23 Elasticsearch 5.6.8 Kibana 5.6.8 The issue I'm having is that after a few days Logstash will stop processing any messages; I'm using the same config file that I used with Logstash 5.3.0 which worked without issue and was rock-solid. There's nothing in the Logstash log file apart from messages about a field in my Cisco logs being the wrong type and therefore failing to index, however this has always been the case. I have tried enabling the 'dead letter' feature in Logstash to process these Cisco logs but that just makes Logstash even more unstable. The Logstash service doesn't actually crash, it just stops processing messages and fails to respond to the restart command so I end up having to reboot the server. I should say though that Logstash continues to respond the the monitor API commands. I have tried updating all Logstash plugins however that has not fixed the issue. As I said, I never had any problems with Logstash 5.3.0 but the latest version (and version 5.6.8) just seem to become unstable after a few days. Any help is greatly appreciated. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: WireGuard for FreeBSD
On 24.05.18 09:15, Bernhard Fröhlich wrote: On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld wrote: We now have a release, so the full instructions for the packages are: 1. wireguard-tools, providing wg(8) and wg-quick(8) Runtime dependencies: bash, wireguard-go Buildtime dependencies: gmake, c compiler, libc Build: gmake -C src/tools WITH_WGQUICK=yes Install: gmake -C src/tools PREFIX=/usr/local install URL: https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20180524.tar.xz 2. wireguard-go Runtime dependencies: libc Buildtime dependencies: gmake, go, dep Build: gmake Install: gmake PREFIX=/usr/local install URL: https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.20180524.tar.xz I believe decke is already working on a port in his repository. Ports are already updated on github. I will do some final checks and expect to commit the wireguard ports to the official tree today. Did I understand correctly that both these ports are userspace implementations and have a similar per packet overhead to OpenVPN and fastd? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: WireGuard for FreeBSD
On Thu, May 24, 2018 at 12:43 PM, Jan Bramkamp wrote: > Did I understand correctly that both these ports are userspace > implementations and have a similar per packet overhead to OpenVPN and fastd? Indeed they're userspace ports. Maybe down the line this will be ported to the FreeBSD kernel like we have on Linux. However, performance wise, even the userspace implementation seems to have better performance than OpenVPN in my testing. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On 05/24/18 03:08, Johannes Lundberg wrote: Hi The first thing me and probably many other do after install is pkg install xxx yyy zzz from console (meaning no scrollback buffer). With xorg and friends this means hundreds of packets. After install all the pkg messages are display and most of sometimes very valuable information is just scrolled away. Is there an easy way to fix* this by piping the output through less or something to pause for each screen so that the messages just aren't scrolled away? In addition to that it would be nice (if it's not already done) to store this information in a log file somewhere so that one can revisit and see what needs to be manually configured for each installed package. *by fix I mean something that does not put the burden on the user. I use screen to record the console session. Cheers /Johannes ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Paul Keusemann pkeu...@gmail.com 4266 Joppa Court (952) 894-7805 Savage, MN 55378 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Logstash failing to process messages
Thanks for getting back to me, yes I suspect it has something to do with my filters though I've no idea which one it could be as I'm filtering on beats and syslog inputs. As a work around I've just added a cron command to restart Logstash every morning at 01:00, though obviously that means I'm losing non-beat events whilst it restarts. Please let me know if upgrading to the latest versions helps you, if it doesn't then perhaps a PR needs to be filed. On 24 May 2018 at 11:25, Benny Goemans wrote: > I have seen the same issue. In my case however, I had about OOM caused by > parsing long grok patterns. I didn't have these in 5.3 either so I suspect > it's a memory leak somewhere. > I have since upgraded everything to 6.x and am waiting to see if the same > issue persists. > > Regards, > Benny Goemans > > On 23-05-2018 17:23, Kernel Panic wrote: > >> Hello, I'll just list the versions before I start: >> >> FreeBSD 11.1 >> >> Logstash 6.23 >> Elasticsearch 5.6.8 >> Kibana 5.6.8 >> >> The issue I'm having is that after a few days Logstash will stop >> processing >> any messages; I'm using the same config file that I used with Logstash >> 5.3.0 which worked without issue and was rock-solid. There's nothing in >> the >> Logstash log file apart from messages about a field in my Cisco logs being >> the wrong type and therefore failing to index, however this has always >> been >> the case. I have tried enabling the 'dead letter' feature in Logstash to >> process these Cisco logs but that just makes Logstash even more unstable. >> >> The Logstash service doesn't actually crash, it just stops processing >> messages and fails to respond to the restart command so I end up having to >> reboot the server. I should say though that Logstash continues to respond >> the the monitor API commands. >> >> I have tried updating all Logstash plugins however that has not fixed the >> issue. >> >> As I said, I never had any problems with Logstash 5.3.0 but the latest >> version (and version 5.6.8) just seem to become unstable after a few days. >> >> Any help is greatly appreciated. >> ___ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" >> > > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On 2018-05-24 11:21, Miroslav Lachman wrote: > Johannes Lundberg wrote on 2018/05/24 11:03: >> On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: >> >>> On Thu, 24 May 2018 09:08:17 +0100 >>> Johannes Lundberg wrote: >>> In addition to that it would be nice (if it's not already done) to store this information in a log file somewhere so that one can revisit and see what needs to be manually configured for each installed package. >>> >>> I have this in syslog.conf: >>> >>> !pkg,pkg-static >>> *.* /var/log/pkg.log > > I think only changes are logged, not messages: > > Apr 26 23:50:22 maja pkg: p5-DBI reinstalled: 1.641 -> 1.641 > Apr 26 23:50:22 maja pkg: mariadb101-client upgraded: 10.1.31 -> 10.1.32_2 > Apr 26 23:50:22 maja pkg: libnghttp2 upgraded: 1.31.0 -> 1.31.1 > >> Thanks for the tip. I'll use this. >> However, someone who knows about this probably know how to manually >> configure their system already. >> >> I want to make sure first timers and newbies don't miss important messages >> on how to configure the system. >> >> Often we get inquires about stuff that is clearly described in the pkg >> message and bug reports that are a consequence of wrong configuration. >> How can we make this more clear so that it is not missed? > > As Eugene already noted - syscons has scrollback buffer. Did you tried > "Scroll Lock" on your keyboard? > > If you need to re-show message of any installed package, "pkg info -D" (or > pkg info --pkg-message) is your friend. Nothing is lost. You can view it > anytime. > For mass updating you can try the script utility, on FreeBSD there is an additional '-q' parameter. $ script -q /tmp/MyScriptLog pkg $ col -xb < /tmp/MyScriptLog > /tmp/MyScriptLog.readable On other platforms: $ script /tmp/MyScriptLog $ pkg $ exit (exits only the script util) $ col -xb < /tmp/MyScriptLog > /tmp/MyScriptLog.readable Now all outputs are covered in the log (stdout and stderr) -- br. olli ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: WireGuard for FreeBSD
On Thu, 24 May 2018 09:15:28 +0200 "Bernhard Fröhlich" said On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld wrote: > We now have a release, so the full instructions for the packages are: > > 1. wireguard-tools, providing wg(8) and wg-quick(8) > Runtime dependencies: bash, wireguard-go > Buildtime dependencies: gmake, c compiler, libc > Build: gmake -C src/tools WITH_WGQUICK=yes > Install: gmake -C src/tools PREFIX=/usr/local install > URL: https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20180524.tar.xz > > 2. wireguard-go > Runtime dependencies: libc > Buildtime dependencies: gmake, go, dep > Build: gmake > Install: gmake PREFIX=/usr/local install > URL: > https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.20180524.tar.xz > > I believe decke is already working on a port in his repository. Ports are already updated on github. I will do some final checks and expect to commit the wireguard ports to the official tree today. I should have no trouble introducing Wireguard to the ports system today. While I could have submitted it sooner. As the Maintainer of ~130 ports. It is not entirely unusual to have pr(1)'s to deal with. Especially with the introduction (updrade) of clang/llvm in $BASE to v.5, and now v.6. Thanks for your understanding. --Chris -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, 24 May 2018 15:39:54 +0700 "Eugene Grosbein" said On 24.05.2018 15:08, Johannes Lundberg wrote: > Hi > > The first thing me and probably many other do after install is > pkg install xxx yyy zzz > from console (meaning no scrollback buffer). > > With xorg and friends this means hundreds of packets. After install all the > pkg messages are display and most of sometimes very valuable information is > just scrolled away. > > Is there an easy way to fix* this by piping the output through less or > something to pause for each screen so that the messages just aren't > scrolled away? > > In addition to that it would be nice (if it's not already done) to store > this information in a log file somewhere so that one can revisit and see > what needs to be manually configured for each installed package. > > *by fix I mean something that does not put the burden on the user. Installation/deinstallation of packages logged by default to /var/log/messages. Syscons console has scrollback buffer by default. If vt(4) has not, that's regression after syscons and should be fixed in the vt. Also, one can have, for tcsh: alias pkg 'script -a /var/log/pkg.log pkg-static' So "pkg install xxx yyy zzz" adds fulls output to specified file. +1 I simply fire $ script ~/pkg-install-session build, or pkg install $ exit Then grep(1) the results for desired info. It also allows me to discover any (serious) warnings that may have been emitted. HTH --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, 24 May 2018 10:03:47 +0100 "Johannes Lundberg" said On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > On Thu, 24 May 2018 09:08:17 +0100 > Johannes Lundberg wrote: > > > In addition to that it would be nice (if it's not already done) to > > store this information in a log file somewhere so that one can > > revisit and see what needs to be manually configured for each > > installed package. > > I have this in syslog.conf: > > !pkg,pkg-static > *.* /var/log/pkg.log > Thanks for the tip. I'll use this. However, someone who knows about this probably know how to manually configure their system already. I want to make sure first timers and newbies don't miss important messages on how to configure the system. Often we get inquires about stuff that is clearly described in the pkg message and bug reports that are a consequence of wrong configuration. How can we make this more clear so that it is not missed? ports-mgmt/portmaster used (probably still does) to concatenate the list of (port emitted) messages, and dump them to the console/screen when the build/install session completed. Perhaps pkg(8) could incorporate this, as well? --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, May 24, 2018 at 07:00:02AM -0700, Chris H wrote: > On Thu, 24 May 2018 10:03:47 +0100 "Johannes Lundberg" > said > > > On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > > > > > On Thu, 24 May 2018 09:08:17 +0100 > > > Johannes Lundberg wrote: > > > > > > > In addition to that it would be nice (if it's not already done) to > > > > store this information in a log file somewhere so that one can > > > > revisit and see what needs to be manually configured for each > > > > installed package. > > > > > > I have this in syslog.conf: > > > > > > !pkg,pkg-static > > > *.* /var/log/pkg.log > > > > > > > Thanks for the tip. I'll use this. > > However, someone who knows about this probably know how to manually > > configure their system already. > > > > I want to make sure first timers and newbies don't miss important messages > > on how to configure the system. > > > > Often we get inquires about stuff that is clearly described in the pkg > > message and bug reports that are a consequence of wrong configuration. > > How can we make this more clear so that it is not missed? > ports-mgmt/portmaster used (probably still does) to concatenate the list > of (port emitted) messages, and dump them to the console/screen when the > build/install session completed. > Perhaps pkg(8) could incorporate this, as well? Have you already used pkg(8) ? Bapt signature.asc Description: PGP signature
Re: Pause pkg install messages
On Thu, May 24, 2018 at 2:57 PM Chris H wrote: > On Thu, 24 May 2018 10:03:47 +0100 "Johannes Lundberg" > said > > > On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > > > > > On Thu, 24 May 2018 09:08:17 +0100 > > > Johannes Lundberg wrote: > > > > > > > In addition to that it would be nice (if it's not already done) to > > > > store this information in a log file somewhere so that one can > > > > revisit and see what needs to be manually configured for each > > > > installed package. > > > > > > I have this in syslog.conf: > > > > > > !pkg,pkg-static > > > *.* /var/log/pkg.log > > > > > > > Thanks for the tip. I'll use this. > > However, someone who knows about this probably know how to manually > > configure their system already. > > > > I want to make sure first timers and newbies don't miss important > messages > > on how to configure the system. > > > > Often we get inquires about stuff that is clearly described in the pkg > > message and bug reports that are a consequence of wrong configuration. > > How can we make this more clear so that it is not missed? > ports-mgmt/portmaster used (probably still does) to concatenate the list > of (port emitted) messages, and dump them to the console/screen when the > build/install session completed. > Perhaps pkg(8) could incorporate this, as well? > It does. The problem is there's no paging so all information is scrolled away unless you're on standby with scroll-lock which many computers don't have today... > > --Chris > > > > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, 24 May 2018 15:02:10 +0100 "Johannes Lundberg" said On Thu, May 24, 2018 at 2:57 PM Chris H wrote: > On Thu, 24 May 2018 10:03:47 +0100 "Johannes Lundberg" > said > > > On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > > > > > On Thu, 24 May 2018 09:08:17 +0100 > > > Johannes Lundberg wrote: > > > > > > > In addition to that it would be nice (if it's not already done) to > > > > store this information in a log file somewhere so that one can > > > > revisit and see what needs to be manually configured for each > > > > installed package. > > > > > > I have this in syslog.conf: > > > > > > !pkg,pkg-static > > > *.* /var/log/pkg.log > > > > > > > Thanks for the tip. I'll use this. > > However, someone who knows about this probably know how to manually > > configure their system already. > > > > I want to make sure first timers and newbies don't miss important > messages > > on how to configure the system. > > > > Often we get inquires about stuff that is clearly described in the pkg > > message and bug reports that are a consequence of wrong configuration. > > How can we make this more clear so that it is not missed? > ports-mgmt/portmaster used (probably still does) to concatenate the list > of (port emitted) messages, and dump them to the console/screen when the > build/install session completed. > Perhaps pkg(8) could incorporate this, as well? > It does. The problem is there's no paging so all information is scrolled away unless you're on standby with scroll-lock which many computers don't have today... Have you tried less(1) or more(1) ? eg; $ cat ~/output-log | less or, more simply $ less < ./output-log HTH --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, May 24, 2018 at 3:25 PM Chris H wrote: > On Thu, 24 May 2018 15:02:10 +0100 "Johannes Lundberg" > said > > > On Thu, May 24, 2018 at 2:57 PM Chris H wrote: > > > > > On Thu, 24 May 2018 10:03:47 +0100 "Johannes Lundberg" < > johal...@gmail.com> > > > said > > > > > > > On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > > > > > > > > > On Thu, 24 May 2018 09:08:17 +0100 > > > > > Johannes Lundberg wrote: > > > > > > > > > > > In addition to that it would be nice (if it's not already done) > to > > > > > > store this information in a log file somewhere so that one can > > > > > > revisit and see what needs to be manually configured for each > > > > > > installed package. > > > > > > > > > > I have this in syslog.conf: > > > > > > > > > > !pkg,pkg-static > > > > > *.* /var/log/pkg.log > > > > > > > > > > > > > Thanks for the tip. I'll use this. > > > > However, someone who knows about this probably know how to manually > > > > configure their system already. > > > > > > > > I want to make sure first timers and newbies don't miss important > > > messages > > > > on how to configure the system. > > > > > > > > Often we get inquires about stuff that is clearly described in the > pkg > > > > message and bug reports that are a consequence of wrong > configuration. > > > > How can we make this more clear so that it is not missed? > > > ports-mgmt/portmaster used (probably still does) to concatenate the > list > > > of (port emitted) messages, and dump them to the console/screen when > the > > > build/install session completed. > > > Perhaps pkg(8) could incorporate this, as well? > > > > > > > It does. The problem is there's no paging so all information is scrolled > > away unless you're on standby with scroll-lock which many computers don't > > have today... > Have you tried less(1) or more(1) ? > eg; > > $ cat ~/output-log | less > > or, more simply > > $ less < ./output-log > > HTH > You're totally missing the point. The problem is, first timers are missing important information on how to configure the system when they install the packages for the first time. Many don't know in advance they have to pipe the output to a log file which they later can view with a pager. > > --Chris > > > > > > > > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, 24 May 2018 15:39:39 +0100 "Johannes Lundberg" said On Thu, May 24, 2018 at 3:25 PM Chris H wrote: > On Thu, 24 May 2018 15:02:10 +0100 "Johannes Lundberg" > said > > > On Thu, May 24, 2018 at 2:57 PM Chris H wrote: > > > > > On Thu, 24 May 2018 10:03:47 +0100 "Johannes Lundberg" < > johal...@gmail.com> > > > said > > > > > > > On Thu, May 24, 2018 at 9:27 AM Bob Eager wrote: > > > > > > > > > On Thu, 24 May 2018 09:08:17 +0100 > > > > > Johannes Lundberg wrote: > > > > > > > > > > > In addition to that it would be nice (if it's not already done) > to > > > > > > store this information in a log file somewhere so that one can > > > > > > revisit and see what needs to be manually configured for each > > > > > > installed package. > > > > > > > > > > I have this in syslog.conf: > > > > > > > > > > !pkg,pkg-static > > > > > *.* /var/log/pkg.log > > > > > > > > > > > > > Thanks for the tip. I'll use this. > > > > However, someone who knows about this probably know how to manually > > > > configure their system already. > > > > > > > > I want to make sure first timers and newbies don't miss important > > > messages > > > > on how to configure the system. > > > > > > > > Often we get inquires about stuff that is clearly described in the > pkg > > > > message and bug reports that are a consequence of wrong > configuration. > > > > How can we make this more clear so that it is not missed? > > > ports-mgmt/portmaster used (probably still does) to concatenate the > list > > > of (port emitted) messages, and dump them to the console/screen when > the > > > build/install session completed. > > > Perhaps pkg(8) could incorporate this, as well? > > > > > > > It does. The problem is there's no paging so all information is scrolled > > away unless you're on standby with scroll-lock which many computers don't > > have today... > Have you tried less(1) or more(1) ? > eg; > > $ cat ~/output-log | less > > or, more simply > > $ less < ./output-log > > HTH > You're totally missing the point. Not entirely. :-) I'm suggesting that there *are* solutions, and that 1) either (pkg) present them at the end of a session or 2) these be documented/mentioned in the FreeBSD/pkg documentation (for first timers) FWIW given that (t)csh is the default shell && that PAGER is already defined in ~/.cshrc as more(1) (which is less). "paging" a document/file should already understood. :-) So the indication that one should use (type)script(1) before starting a build/install session (if one is concerned about details) is probably the real issue here. Which would be a good candidate for the FreeBSD/pkg docs IMHO. --Chris The problem is, first timers are missing important information on how to configure the system when they install the packages for the first time. Many don't know in advance they have to pipe the output to a log file which they later can view with a pager. > > --Chris > > > > > > > > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On 05/24/2018 02:46, Johannes Lundberg wrote: If you need to re-show message of any installed package, "pkg info -D" (or pkg info --pkg-message) is your friend. Nothing is lost. You can view it anytime. If you're in virtualbox on a laptop, you seldom have scroll lock unless you map it manually (which is not easy to know how to do). And, yes you can review the messages later but how do you know which of the 100's of package had important messages for you? Often when I install 100's of package I walk away from the computer and when I come back all the messages except the very last one or two have scrolled by. I think we should have a pager that says something like "please carefully read through these messages", halt the output and let's you scroll one page or pkg at the time. Even better, a Y/N question asking the user if they want configuration to be done for them where it makes sense (but that's a bigger project). I think having pkg output something along the lines of "missed important messages or want to view them again, run pkg info -D at any time. here's the list of pkgs we just installed:" would be a good improvement. it would encourage people to get more comfortable with the pkg tool itself while not changing the default behaviour that experienced admins/users have gotten used to. -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Commiter needed
Hello. Those tiny requests are sitting there forever: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227094 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227750 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191526 Thanks in advance. -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Pause pkg install messages
On Thu, 24 May 2018, Pete Wright wrote: On 05/24/2018 02:46, Johannes Lundberg wrote: If you need to re-show message of any installed package, "pkg info -D" (or pkg info --pkg-message) is your friend. Nothing is lost. You can view it anytime. If you're in virtualbox on a laptop, you seldom have scroll lock unless you map it manually (which is not easy to know how to do). And, yes you can review the messages later but how do you know which of the 100's of package had important messages for you? Often when I install 100's of package I walk away from the computer and when I come back all the messages except the very last one or two have scrolled by. I think we should have a pager that says something like "please carefully read through these messages", halt the output and let's you scroll one page or pkg at the time. Even better, a Y/N question asking the user if they want configuration to be done for them where it makes sense (but that's a bigger project). I think having pkg output something along the lines of "missed important messages or want to view them again, run pkg info -D at any time. here's the list of pkgs we just installed:" would be a good improvement. it would encourage people to get more comfortable with the pkg tool itself while not changing the default behaviour that experienced admins/users have gotten used to. All FreeBSD systems by default come set up with the expectation that you (the admin) are going to receive mail from cron and periodic. I'd opt to also email this, on by default, but turn-offable. FWIW, I believe this is also what Debian does. Best, -Dan -- "It would be bad." -Egon Spengler, "Ghostbusters" Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC FB: fb.com/DanielMahoneyIV LI: linkedin.com/in/gushi Site: http://www.gushi.org --- ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: WireGuard for FreeBSD
On Thu, 24 May 2018 19:39:22 +0200 "Jason A. Donenfeld" said Hi Chris, On Thu, May 24, 2018 at 3:38 PM, Chris H wrote: > I should have no trouble introducing Wireguard to the ports system today. I'm not a native fluent speaker of FreeBSDese, but my understanding is: a) Bernhard committed the two new packages to ports today. b) If you update ports with portsnap, you can build them locally. c) If you run `pkg install wireguard`, it fails because the build servers haven't gotten to them and won't for several days. Does your statement about "introducing WireGuard to the ports system" mean that you intend to rectify (c) immediately, so we don't have to wait several days for the build snapshot scripts to tick in cron? Or is it mostly just related to not realizing (a)? Sigh... It was my understanding that when I stepped up to adopt WireGuard, and your ack to that. That *I* would be adding the port. I wasn't able to produce the port that same, or next day, as I am already Maintainer for nearly 150 ports. I have no trouble with that list, except that clang/llvm v5, and shortly after v6 became the default versions in $BASE. Which introduced a few pr(1)'s I needed to deal with. Now all the time I have spent researching, and staging to build the port have been laid to waste. Apparently you rescinded, and gave it to Bernhard. This project doesn't feel like a good match to me. No hard feelings, Bernhard. Have fun with the port. All the best. --Chris Jason ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Commiter needed
Hi! > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227750 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191526 Done. Thank you for the reminder and your patience. The lua one really slipped through the cracks 8-( -- p...@opsec.eu+49 171 31013722 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Commiter needed
24.05.18 22:14, Kurt Jaeger пише: Hi! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227750 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191526 Done. Thank you for the reminder and your patience. The lua one really slipped through the cracks 8-( Thank you! -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Lightning removed from ThunderBird?
Andrea Venturoli writes: > Has this anything to do with the (imminent?) switch to version 60? Bundled Lightning appears to work in 60 but better try yourself. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228477 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
