[gentoo-user] mpv: no sound anymore...?

[tuxic]

Hi,

either by one of the last updates or by me while un-pulseaudio-fy
firefox (and removing pulseaudio afterwards) mpv is no longer willing
to play any sound.


Some informations:

[I] media-video/mpv
 Available versions:  0.18.0-r1 0.25.0-r2 (~)0.26.0 (~)0.27.0-r1 
[M](~)0.28.0 ** {+X +alsa aqua archive bluray cdda +cli coreaudio cplugins 
cuda doc drm dvb dvd +egl +enca encode gbm +iconv jack javascript jpeg lcms 
+libass libav libcaca libguess libmpv (+)lua luajit openal +opengl oss 
pulseaudio raspberry-pi rubberband samba sdl selinux test tools (+)uchardet v4l 
vaapi vdpau vf-dlopen wayland xinerama +xscreensaver +xv zlib zsh-completion 
CPU_FLAGS_X86="sse4_1" PYTHON_TARGETS="python2_7 python3_4 python3_5 python3_6"}
 Installed versions:  0.27.0-r1(06:53:23 AM 01/04/2018)(X alsa archive cdda 
cli cplugins cuda doc drm dvb dvd egl encode iconv jack jpeg libass lua luajit 
opengl tools uchardet v4l vdpau xv zlib zsh-completion -aqua -bluray -coreaudio 
-gbm -javascript -lcms -libav -libcaca -libmpv -openal -oss -pulseaudio 
-raspberry-pi -rubberband -samba -sdl -selinux -test -vaapi -wayland 
PYTHON_TARGETS="python2_7 python3_5 python3_6 -python3_4")
 Homepage:https://mpv.io/
 Description: Media player based on MPlayer and mplayer2


Output on the console while playing a video:
mpv the_best_GPU_for_Blender-720p.mp4
Playing: the_best_GPU_for_Blender-720p.mp4
 (+) Video --vid=1 (*) (h264 1280x720 29.970fps)
 (+) Audio --aid=1 --alang=und (*) (aac 2ch 44100Hz)
ALSA lib 
/var/tmp/portage/media-libs/alsa-lib-1.1.5/work/alsa-lib-1.1.5/src/pcm/pcm_dmix.c:1099:(snd_pcm_dmix_open)
 unable to open slave
[ao/alsa] Playback open error: Device or resource busy
[ao] Failed to initialize audio driver 'alsa'
Could not open/initialize audio device -> no sound.
Audio: no audio
VO: [opengl] 1280x720 yuv420p
V: 00:00:01 / 00:12:38 (0%)


Exiting... (Quit)


Or with jack:

(replaced my username by 'user')

ps -ef | grep jack 
user  4299 1  0 02:47 ?00:01:34 jackd -t5000 -dalsa -dhw:0 -r48000 
-p1024 -n2 -H -M -Xseq
user 24837 24766  0 08:05 pts/300:00:00 grep -E --color jack

id   
uid=1001(user) gid=100(users) 
groups=100(users),10(wheel),12(mail),14(uucp),18(audio),19(cdrom),27(video),35(games),80(cdrw),85(usb),103(docker),237(wireshark),244(vboxusers),245(vlock),246(realtime)

[I] media-sound/jack-audio-connection-kit
 Available versions:  0.121.3-r1 (~)0.124.1-r1 (~)0.125.0 {alsa altivec 
coreaudio cpudetection debug doc examples oss pam ABI_MIPS="n32 n64 o32" 
ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" CPU_FLAGS_X86="3dnow mmx 
sse"}
 Installed versions:  0.125.0(07:33:45 AM 12/05/2017)(alsa pam -altivec 
-coreaudio -debug -doc -examples -oss ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 
-64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" CPU_FLAGS_X86="3dnow sse")
 Homepage:http://www.jackaudio.org
 Description: A low-latency audio server

(using zsh):
l /dev/**/*jack*
srwxr-xr-x 1 user users  0 2018-01-20 02:47 
/dev/shm/jack-1001/default/jack_0
srwxr-xr-x 1 user users  0 2018-01-20 02:47 
/dev/shm/jack-1001/default/jack_ack_0
prw-r--r-- 1 user users  0 2018-01-20 08:07 
/dev/shm/jack-1001/default/jack-ack-fifo-4299-0
prw-r--r-- 1 user users  0 2018-01-20 08:07 
/dev/shm/jack-1001/default/jack-ack-fifo-4299-1
prw-r--r-- 1 user users  0 2018-01-20 02:47 
/dev/shm/jack-1001/default/jack-ack-fifo-4299-2
prw-r--r-- 1 user users  0 2018-01-20 02:49 
/dev/shm/jack-1001/default/jack-ack-fifo-4299-3

/dev/shm/jack-1001:
total 0

mpv --audio-device=jack the_best_GPU_for_Blender-720p.mp4 
Playing: the_best_GPU_for_Blender-720p.mp4
 (+) Video --vid=1 (*) (h264 1280x720 29.970fps)
 (+) Audio --aid=1 --alang=und (*) (aac 2ch 44100Hz)
ALSA lib 
/var/tmp/portage/media-libs/alsa-lib-1.1.5/work/alsa-lib-1.1.5/src/pcm/pcm_dmix.c:1099:(snd_pcm_dmix_open)
 unable to open slave
[ao/alsa] Playback open error: Device or resource busy
[ao] Failed to initialize audio driver 'alsa'
Could not open/initialize audio device -> no sound.
Audio: no audio
VO: [opengl] 1280x720 yuv420p
V: 00:00:01 / 00:12:38 (0%)

(why it is accessing alsa here???)


Using for example zynaddsubfx (softsynth) via qjackctrl/jack I can
play sound.
Mpv does not show up in qjackctrl

The situation does not change if doing anything of the above as root.

Mplayer plays sound...but fails to play the video instead.

Currently I dont know what the problem here.

If anyone has any idea...heartly welcome... :)

Cheers
Meino

[gentoo-user] Re: dev-qt/qtdeclarative fails to build

[Nikos Chantziaras]

On 20/01/18 00:10, Christoph Böhmwalder wrote:

Hey everyone,

I tried building qtdeclarative-5.9.3 today, but the linker failed:

$ cat build.log
--- >8 ---
g++-6.4.0 -Wl,-O1 -Wl,--as-needed -Wl,--enable-new-dtags -shared -o 
libparticlesplugin.so .obj/plugin.o
-L/var/tmp/portage/dev-qt/qtdeclarative-5.9.3/work/qtdeclarative-opensource-src-5.9.3/lib
 -lQt5QuickParti
cles -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lGL -lpthread
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
 multiple definition of
  `__bss_start'


Is this for the profile upgrade? I had this too, because for some weird 
reason, emerge wants to rebuild qtdeclarative and qtgui before it 
rebuilds qtcore. So it tried to link the new PIC-enabled qtdeclarative 
against the old non-PIC qtcore. The result was this exact build error.


If you indeed ran into this due to the @world rebuild that's required by 
the profile update, you can ignore it and resume the @world rebuild with 
--skipfirst. Or use --keep-going to skip over all build failures, and 
then rebuild failed packages manually at the end.

Re: [gentoo-user] Libreoffice-5.4.2.2 fails to start

[thelma]

On 01/19/2018 05:25 PM, the...@sys-concept.com wrote:
[snip]
> 
> The strange part is that on the same box I created a new "user" and
> Libreoffice works just fine.
> But it will not work when I log in.
> 
> I've deleted the folder setting. /home/joseph/.config/libreoffice/
> and copied the same folder from new user directory back to my directory.
> Libreofice still will not start.
> 
> Joseph

Additional information.
When I try to start soffice help I'm getting this error

soffice --help
X11 connection rejected because of wrong authentication.

(process:24269): dconf-CRITICAL **: unable to create file 
'/var/run/user/1000/dconf/user': Permission denied.  dconf will not work 
properly.
LibreOffice 5.4.2.2.0 40m0(Build:2)

This error does not show up when I run it as new user that I just created.

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-20, Grant Taylor  wrote:
> On 01/19/2018 04:58 PM, Grant Edwards wrote:
>
>> That would require seperate outbound transports that are selected based 
>> on how the mail was read: smtp vs. /usr/bin/sendmail (the real one).
>
> Okay
>
>> I get the impression from exim and postfix docs that outbound routing 
>> based on input method aren't possible (I may be wrong about that).
>
> Depending on what exactly you're needing, I might be able to think of a 
> way to do this with Sendmail.  -  This may be one of the exceedingly 
> rare times that Sendmail's splitting MTA and MSA roles may actually be 
> beneficial (other than for the security reasons).

[...]

> Am I regurgitating this properly?
>
> 1) You want incoming SMTP connections to go out via your custom mailer 
>script.
>
> 2) You want messages originated locally and piped into $commandTBD to 
>go out via SMTP.

Yes -- the two are completely unrelated and unconnected.

> Would I be correct in assuming that the path and / or name of the 
> sendmail like script that interfaces with the Exchange server could 
> change if necessary? I.e. you could name it
> /usr/local/bin/sendmail_to_exchange_gateway if you needed to.

Yes.  It's not actually located at /usr/bin/sendmail, and doesn't need
to be.

> Question:  What name are your scripts currently calling to interface 
> with msmtp?  -  Can that name change if necessary?

Yes they can be changed.  Most of the things that invoke msmtp invoke
it as /usr/bin/msmtp.  A few invoke it as /usr/bin/sendmail.

> I'm trying to juggle the various pieces as I understand them to see if 
> everything can work together.

Don't waste any time on it -- I think the current SMTP server combined
with stunnel is going to work.

> Note:  I'm not trying to push Sendmail.  -  I know I'm strange in my 
> predilection for it.  -  I'm simply trying to solve the problem (as I 
> understand it) with the tools that I know.
>
>> Well I have several msmtp "accounts" set up and run multiple mutt 
>> configurations that use those different accounts for outbound mail.
>
> The different accounts outbound may complicate things.  Are those 
> accounts configured as part of msmtp?  Or are they configured in the 
> things using msmtp?

Both.  msmtp has a config file that defines the accounts, and things
that invoke msmtp directly (e.g. mutt) use a command-line option to
specify an account. There is a default account that's used if the
command line option isn't present (which would be the case for apps
that invoke msmtp as '/usr/bin/sendmail').  Now that I think about it,
I think a configuration that chooses outbound routes for locally
generated email based on from address could work.  Several of those
accounts/routes actually go to the same SMTP server but authenticate
with different username/password combinations.

In mutt's case, I also believe I could switch from msmtp to mutt's
"new" built-in SMTP client code.

Another option would be to set up a container in which to run the
"relay" MTA (sendmail/exim/postfix) that's doing SMTP -->
sendmail-like-script. This is probably the cleanest way to do it.

But, that's all moot if the stunnel solution works.

-- 
Grant

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Ian Zimmerman]

On 2018-01-19 23:58, Grant Edwards wrote:

> That would require seperate outbound transports that are selected
> based on how the mail was read: smtp vs. /usr/bin/sendmail (the real
> one).  I get the impression from exim and postfix docs that outbound
> routing based on input method aren't possible (I may be wrong about
> that).

In the case of exim, you're definitely very wrong about it.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 05:30 PM, Grant Taylor wrote:
I'm trying to juggle the various pieces as I understand them to see if 
everything can work together.


I have a fleeting thought that /might/ work.  I want to write it down 
before I loose it.


1)  Configure Sendmail's MTA to not have any listening daemon ports.  - 
This means that all interface to the MTA will be via the 
/path/to/sendmail binary.

2)  Configure Sendmail's MSA to listen on TCP port 25.
3)  Configure Sendmail's MSA to smart host (without encryption) through 
your existing SMTP to Exchange gateway.


I /think/ this addresses most parts.

SMTP from ??? connects to the MSA which connects to the Exchange Gateway 
which connects to Exchange via something other than SMTP.  -  I think 
that tracks.


Email from the local machine uses the /usr/sbin/sendmail interface which 
speaks SMTP to the world or a smart host.


I think that does work.  Granted, there are some IPs and or ports to 
juggle to make sure that Sendmail's MSA and your SMTP to Exchange 
gateway don't conflict.  But I think that should be possible to handle.


I don't know if the other common MTAs can do anything like this or not. 
I would hope that they can.


I will also say that it is possible to get Sendmail to do some really 
complex things.  It may be possible to get a single sendmail daemon to 
do everything.  But I think that is going to be more complicated, 
possibly needlessly so if the above recommendation works.


I need to know more details about the different accounts and how they 
interact with msmtp (which I have zero experience with) to know if they 
will play nicely with the above configuration.


The only niggling feeling I have is about 127.0.0.1:25.  Is anything at 
all using that?  I've run across a lot of programs that assume the local 
MTA is listening there.  -  If something is, then it's likely a matter 
of juggling IP(s) and port(s) that various things are listening on.




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 04:58 PM, Grant Edwards wrote:
That would require seperate outbound transports that are selected based 
on how the mail was read: smtp vs. /usr/bin/sendmail (the real one).


Okay

I get the impression from exim and postfix docs that outbound routing 
based on input method aren't possible (I may be wrong about that).


Depending on what exactly you're needing, I might be able to think of a 
way to do this with Sendmail.  -  This may be one of the exceedingly 
rare times that Sendmail's splitting MTA and MSA roles may actually be 
beneficial (other than for the security reasons).


I'm going to need to ponder this.

Unless it's possible to run two separate instances -- one to relay SMTP 
--> my_custom_sendmail_utility and one to hanlde outbound mail generated 
locally standard_usr_bin_sendmail --> SMTP.


That's certainly possible to do with Sendmail.  Or at least it used to 
be.  Granted, it's annoying ... to make sure that the various queues are 
separated.


I'm trying to think through this to see if there is a way to leverage 
the existing separation between the MTA (which has the features for your 
listening SMTP daemon) and the MSA (which I think prefers to talk SMTP 
to a smart host, usually the local MTA).


Am I regurgitating this properly?

1)  You want incoming SMTP connections to go out via your custom mailer 
script.
2)  You want messages originated locally and piped into $commandTBD to 
go out via SMTP.


Would I be correct in assuming that the path and / or name of the 
sendmail like script that interfaces with the Exchange server could 
change if necessary?  I.e. you could name it 
/usr/local/bin/sendmail_to_exchange_gateway if you needed to.


Question:  What name are your scripts currently calling to interface 
with msmtp?  -  Can that name change if necessary?


I'm trying to juggle the various pieces as I understand them to see if 
everything can work together.


Note:  I'm not trying to push Sendmail.  -  I know I'm strange in my 
predilection for it.  -  I'm simply trying to solve the problem (as I 
understand it) with the tools that I know.


Well I have several msmtp "accounts" set up and run multiple mutt 
configurations that use those different accounts for outbound mail.


The different accounts outbound may complicate things.  Are those 
accounts configured as part of msmtp?  Or are they configured in the 
things using msmtp?




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [gentoo-user] Libreoffice-5.4.2.2 fails to start

[thelma]

Thelma
On 01/17/2018 04:06 PM, the...@sys-concept.com wrote:
> emerge -pqv app-office/libreoffice
> [ebuild   R   ] app-office/libreoffice-5.4.2.2  USE="bluetooth branding cups 
> dbus gnome gtk java mysql (-coinmp) -collada -debug -eds (-firebird) -gltf 
> -googledrive -gstreamer -gtk3 -jemalloc -kde -libressl -odk -pdfimport 
> -postgres -quickstarter {-test} -vlc" LIBREOFFICE_EXTENSIONS="-nlpsolver 
> -scripting-beanshell -scripting-javascript -wiki-publisher" 
> PYTHON_SINGLE_TARGET="python3_5 -python2_7 -python3_4 -python3_6" 
> PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6"
> 
> 
> Post wgetpaste link of libreoffice build log
> What does it do?  When I try: 
> wgetpaste 
> /var/log/portage/app-office\:libreoffice-5.4.2.2\:20180116-202656.log
> 
> There is no output. This file is very large.
> 
> When I run:
> strace -o libreoffice.txt -f soffice libreoffice 
> The output "time out on":
> 
> ...
> 2238  connect(3, {sa_family=AF_UNIX, 
> sun_path="/tmp/OSL_PIPE_1000_SingleOfficeIPC_db1e7eee18c324ec912d5118a2d21af"},
>  110 
> 2250  <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
> 2250  futex(0x7f77a3827840, FUTEX_WAKE_PRIVATE, 1) = 0
> 2250  futex(0x7f77a3827ad0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 
> 0, {tv_sec=1516203792, tv_nsec=525188000}, 0x) = -1 ETIMEDOUT 
> (Connection timed out)
> 
> Joseph
> 
[snip]

The strange part is that on the same box I created a new "user" and
Libreoffice works just fine.
But it will not work when I log in.

I've deleted the folder setting. /home/joseph/.config/libreoffice/
and copied the same folder from new user directory back to my directory.
Libreofice still will not start.

Joseph

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Grant Taylor  wrote:
> On 01/19/2018 04:04 PM, Grant Edwards wrote:
>> One of the hassles with those is that portage won't allow me to install 
>> any of them because they conflict with msmtp, which is what I use for 
>> sending normal e-mail.
>
> I would expect that you can use any of those in place of msmtp to send 
> email too.

That would require seperate outbound transports that are selected
based on how the mail was read: smtp vs. /usr/bin/sendmail (the real
one).  I get the impression from exim and postfix docs that outbound
routing based on input method aren't possible (I may be wrong about
that).

Unless it's possible to run two separate instances -- one to relay
SMTP --> my_custom_sendmail_utility and one to hanlde outbound mail
generated locally standard_usr_bin_sendmail --> SMTP.

> Or are you doing something that is msmtp specific?

Well I have several msmtp "accounts" set up and run multiple mutt
configurations that use those different accounts for outbound mail.

-- 
Grant

Re: [gentoo-user] dev-qt/qtdeclarative fails to build

[Christoph Böhmwalder]

On Sat, Jan 20, 2018 at 12:28:49AM +0100, David Haller wrote:
> revdep-rebuild -vp --library 'libstdc++.so.6' -- --exclude gcc

Oof, I just ran this anyways and a lot of packages popped up.  Guess
I'll rebuild some stuff over the night and see if that fixes it :)

Thanks for your help so far!

--
Regards,
Christoph

Re: [gentoo-user] dev-qt/qtdeclarative fails to build

[Christoph Böhmwalder]

On Sat, Jan 20, 2018 at 12:28:49AM +0100, David Haller wrote:
> Hello,
> 
> On Fri, 19 Jan 2018, Christoph Böhmwalder wrote:
> >I tried building qtdeclarative-5.9.3 today, but the linker failed:
> >
> >$ cat build.log
> >g++-6.4.0 -Wl,-O1 -Wl,--as-needed -Wl,--enable-new-dtags -shared -o 
> >libparticlesplugin.so .obj/plugin.o
> >-L/var/tmp/portage/dev-qt/qtdeclarative-5.9.3/work/qtdeclarative-opensource-src-5.9.3/lib
> > -lQt5QuickParti
> >cles -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lGL -lpthread
> >/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
> > multiple definition of
> > `__bss_start'
> [..]
> 
> From the build log it seems you have compiled Qt5Gui (etc.) with
> g++-7.2.0, and now try to use g++-6.4.0. I don't think that works.
Ah yeah, I forgot to turn that off.  I have an env file that switches to
gcc-6.4.0 for use with old standalone packages that don't support 7.2.0
yet (I really don't use it anymore nowadays though).

> Try again using 7.2.0 (unless you want to recompile qt with 6.4.0
> again).
Anyways, this leads to the exact same error, so I'm inclined to think it
has nothing to do with gcc versions.  I was however concerned about Qt versions
clashing (4 vs 5?).

In fact, I just double-checked qtchooser, and this is the output:

$ qtchooser -l
4
5
default
qt4-i686-pc-linux-gnu
qt4-x86_64-pc-linux-gnu
qt4
qt5-x86_64-pc-linux-gnu
qt5

Does this mean Qt4 is prioritized over Qt5?  That would be a problem in
this case, right?

--
Regards,
Christoph

Re: [gentoo-user] dev-qt/qtdeclarative fails to build

[David Haller]

Hello,

On Fri, 19 Jan 2018, Christoph Böhmwalder wrote:
>I tried building qtdeclarative-5.9.3 today, but the linker failed:
>
>$ cat build.log
>g++-6.4.0 -Wl,-O1 -Wl,--as-needed -Wl,--enable-new-dtags -shared -o 
>libparticlesplugin.so .obj/plugin.o
>-L/var/tmp/portage/dev-qt/qtdeclarative-5.9.3/work/qtdeclarative-opensource-src-5.9.3/lib
> -lQt5QuickParti
>cles -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lGL -lpthread
>/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
> multiple definition of
> `__bss_start'
[..]

From the build log it seems you have compiled Qt5Gui (etc.) with
g++-7.2.0, and now try to use g++-6.4.0. I don't think that works.

Try again using 7.2.0 (unless you want to recompile qt with 6.4.0
again).

There's a wiki page on updating gcc:
https://wiki.gentoo.org/wiki/Upgrading_GCC

Have a look at the output of

revdep-rebuild -vp --library 'libstdc++.so.6' -- --exclude gcc

(with either 6.4.0 or 7.2.0 selected), that should give you an idea
what you forgot to recompile.

HTH,
-dnh

-- 
My favourite electro-junk store acquired that [Microsoft Operations]
Point of Sale POS more than a year ago.  They still write up the
receipts by hand.  The computer the POS runs on is mostly used for
web browsing.- Brian

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 04:04 PM, Grant Edwards wrote:
One of the hassles with those is that portage won't allow me to install 
any of them because they conflict with msmtp, which is what I use for 
sending normal e-mail.


I would expect that you can use any of those in place of msmtp to send 
email too.


Or are you doing something that is msmtp specific?



--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Ian Zimmerman  wrote:
> On 2018-01-19 20:19, Grant Edwards wrote:
>
>>  Can exim transfer mail to an Exchange server that doesn't expose an
>>  SMTP server?
>> >>>
>> >>> Errr, no. exim does SMTP.
>> >>>
>> >>> If the above is what you need, any orthodox mail server would need
>> >>> to hand the mail over to something that *can* deliver to Exchange.
>> >> 
>> >> Yes, and that something is my existing command-line MTA utility
>> >> that has the same usage as /usr/bin/sendmail.
>
> FWIW, you can plug in your existing script into exim as a custom
> "transport", in the exim terminology.  In fact that is what I used to do
> for years, to stuff outgoing mail into sendmail on a system where I had
> a shell account.  But if I understand the problem now (a well sized if,
> LOL) that doesn't by itself help you because the existing script is
> broken; replacing the script is the main part of the problem.  Right?

The existing /usr/bin/sendmail (that's not it's actual path) script
works fine.  It's the SSL support in the SMTP server that invokes the
/usr/bin/sendmail script that's broken.  I've modified that server to
run an instance of stunnel and use plain SMTP (sans SSL).  It looks
like that's probably going to work.  There's a custom SSL server
because at some point in the past it had to do some odd things with
headers and the envelope from field (it also implements some special
logging).  Then at some later point in the past, the requirement for
those odd things went away.  At some other point in history, the SSL
support in that server got broken.  The actual failure is intermittent
(it depends on message size and network timing), so it's taken a while
to track it down and decide what to do about it.

For now, I'm going with the custom server and stunnel.  If there are
problems with that, I'll try one of sendmail/postfix/exim.  [One of
the hassles with those is that portage won't allow me to install any
of them because they conflict with msmtp, which is what I use for
sending normal e-mail.]

-- 
Grant Edwards   grant.b.edwardsYow! Life is a POPULARITY
  at   CONTEST!  I'm REFRESHINGLY
  gmail.comCANDID!!

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 03:24 PM, Ian Zimmerman wrote:
But if I understand the problem now (a well sized if, LOL) that doesn't 
by itself help you because the existing script is broken; replacing the 
script is the main part of the problem.  Right?


Grant E.'s existing script purportedly functions just fine for 
non-encrypted SMTP connections.  The problem is with encrypted SMTP 
connections.  Further the problem is in the SMTP side, not the actual 
mailer / transport side.


Sendmail / exim / postfix / etc should all be able to provide the 
unencrypted and encrypted SMTP side with very little problem at all.




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Ian Zimmerman]

On 2018-01-19 20:19, Grant Edwards wrote:

>  Can exim transfer mail to an Exchange server that doesn't expose an
>  SMTP server?
> >>>
> >>> Errr, no. exim does SMTP.
> >>>
> >>> If the above is what you need, any orthodox mail server would need
> >>> to hand the mail over to something that *can* deliver to Exchange.
> >> 
> >> Yes, and that something is my existing command-line MTA utility
> >> that has the same usage as /usr/bin/sendmail.

FWIW, you can plug in your existing script into exim as a custom
"transport", in the exim terminology.  In fact that is what I used to do
for years, to stuff outgoing mail into sendmail on a system where I had
a shell account.  But if I understand the problem now (a well sized if,
LOL) that doesn't by itself help you because the existing script is
broken; replacing the script is the main part of the problem.  Right?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

[gentoo-user] dev-qt/qtdeclarative fails to build

[Christoph Böhmwalder]

Hey everyone,

I tried building qtdeclarative-5.9.3 today, but the linker failed:

$ cat build.log
--- >8 ---
g++-6.4.0 -Wl,-O1 -Wl,--as-needed -Wl,--enable-new-dtags -shared -o 
libparticlesplugin.so .obj/plugin.o
-L/var/tmp/portage/dev-qt/qtdeclarative-5.9.3/work/qtdeclarative-opensource-src-5.9.3/lib
 -lQt5QuickParti
cles -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lGL -lpthread
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
 multiple definition of
 `__bss_start'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
 multiple definition of
 `_edata'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
 multiple definition of
 `_end'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Network.so:(*IND*+0x0):
 multiple definitio
n of `_edata'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Network.so:(*IND*+0x0):
 multiple definitio
n of `__bss_start'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Network.so:(*IND*+0x0):
 multiple definitio
n of `_end'
collect2: error: ld returned 1 exit status

$ emerge -pqv '=dev-qt/qtdeclarative-5.9.3::gentoo'
[ebuild  N] dev-qt/qtdeclarative-5.9.3  USE="jit widgets xml -debug 
(-gles2) -localstorage {-test}"


emerge --info output and build.log are attached.

Any ideas? Thanks!

--
Regards,
Christoph


build.log.gz
Description: Binary data
Portage 2.3.19 (python 3.5.4-final-0, default/linux/amd64/17.0/desktop, 
gcc-7.2.0, glibc-2.26-r5, 4.15.0-rc5+ x86_64)
=
 System Settings
=
System uname: 
Linux-4.15.0-rc5+-x86_64-Intel-R-_Core-TM-_i7-3667U_CPU_@_2.00GHz-with-gentoo-2.4.1
KiB Mem: 7864116 total,   2005240 free
KiB Swap:  0 total, 0 free
Timestamp of repository gentoo: Fri, 19 Jan 2018 21:00:01 +
Head commit of repository gentoo: d43b05743e0f5e3a6c6236c445e5f88c959f8c3c
sh bash 4.4_p12-r1
ld GNU ld (Gentoo 2.29.1 p3) 2.29.1
ccache version 3.3.4 [disabled]
app-shells/bash:  4.4_p12-r1::gentoo
dev-java/java-config: 2.2.0-r3::gentoo
dev-lang/perl:5.26.1-r1::gentoo
dev-lang/python:  2.7.14-r1::gentoo, 3.5.4-r1::gentoo, 3.6.4::gentoo
dev-util/ccache:  3.3.4-r1::gentoo
dev-util/cmake:   3.10.2::gentoo
dev-util/pkgconfig:   0.29.2::gentoo
sys-apps/baselayout:  2.4.1-r2::gentoo
sys-apps/openrc:  0.34.11::gentoo
sys-apps/sandbox: 2.12::gentoo
sys-devel/autoconf:   2.13::gentoo, 2.69-r4::gentoo
sys-devel/automake:   1.15.1-r1::gentoo
sys-devel/binutils:   2.29.1-r1::gentoo
sys-devel/gcc:6.4.0-r1::gentoo, 7.2.0-r1::gentoo
sys-devel/gcc-config: 1.9.1::gentoo
sys-devel/libtool:2.4.6-r4::gentoo
sys-devel/make:   4.2.1-r1::gentoo
sys-kernel/linux-headers: 4.14::gentoo (virtual/os-headers)
sys-libs/glibc:   2.26-r5::gentoo
Repositories:

gentoo
location: /usr/portage
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
sync-rsync-extra-opts: 

crossdev
location: /usr/local/portage-crossdev
masters: gentoo
priority: 10

ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d 
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild 
/etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d 
/etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks 
ebuild-locks fixlafiles merge-sync multilib-strict news parallel-fetch 
preserve-libs protect-owned sandbox sfperms splitdebug strict 
unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv 
usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://gentoo.mirror.web4u.cz/;
LANG="de_DE.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times 
--omit-dir-times --compress --force --whole-file --delete --stats 
--human-readable --timeout=180 --exclude=/distfiles --exclude=/local 
--exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2 cairo cdda 
cdr cli consolekit crypt cups cxx dbus dri dts dvd dvdr emboss encode exif fam 
firefox flac fortran gdbm gif glamor gpm gtk iconv ipv6 jpeg lcms libnotify mad 
mng modules mp3 mp4 mpeg multilib ncurses nptl ogg opengl openmp pam pango pcre 
pdf png policykit ppds 

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 01:29 PM, Grant Edwards wrote:

Aargh.  smtpd.  Typos like that certinaly don't help the confusion.


*chuckle*  -  Mistakes happen.  -  Context answered the question more 
than 90%.



I'm going to try stunnel in front of the existing solution first.

If that doesn't work, I'll try sendmail/postfix/exim.  It looks like 
they'll all do what I want (modulo the no-queue desire).


I think that it's extremely likely that you can configure the MTAs to 
not queue messages.  -  Inquire in MTA specific support groups.


(I expect that someone else would have chimed in to this thread if they 
knew.)


Thanks again (and apologies) to everbody who tried to figure out what 
it was I was asking...


:-)



--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Grant Taylor  wrote:
> On 01/19/2018 12:48 PM, Grant Edwards wrote:
>> Yep, and it looks like the Postfix equivalent is a custom pipe transport. 
>> Once you know what phrases to google for, it's a lot easier.
>
> *nod*
>
> I figured that you would be able to find something.
>
> Hence why I mentioned the terms.  ;-)

[...]

>> I wrote the server I'm using now, but it uses somebody else's snmpd 
>> module, and that's where the SSL breakage is.  I've filed a bug, and I've 
>> been doing some reading toward attempting a fix, but it looks like it 
>> might be a bit hairy: it involves Python's asyncore/asynchat framework 
>> (and process pools).  What's missing is handling for ssl "want read" 
>> and "want write" exceptions.
>
> "snmpd" or "smtpd"?

Aargh.  smtpd.  Typos like that certinaly don't help the confusion.

> You lost me at Python.  (I know it's a personal prejudice.  But I
> think I'm allowed to have it as long as I acknowledge them as such.)

I'm going to try stunnel in front of the existing solution first.

If that doesn't work, I'll try sendmail/postfix/exim.  It looks like
they'll all do what I want (modulo the no-queue desire). FWIW, the
google phrase for exim is "exim pipe transport":

  
https://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_pipe_transport.html

Thanks again (and apologies) to everbody who tried to figure out what
it was I was asking...

-- 
Grant Edwards   grant.b.edwardsYow! They collapsed
  at   ... like nuns in the
  gmail.comstreet ... they had no
   teen appeal!

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Alan McKinnon  wrote:
> On 19/01/2018 22:03, Grant Edwards wrote:
>> On 2018-01-19, Alan McKinnon  wrote:
>>> On 19/01/2018 21:54, Grant Edwards wrote:
>>>
 Can exim transfer mail to an Exchange server that doesn't expose an
 SMTP server?
>>>
>>> Errr, no. exim does SMTP.
>>>
>>> If the above is what you need, any orthodox mail server would need to
>>> hand the mail over to something that *can* deliver to Exchange.
>> 
>> Yes, and that something is my existing command-line MTA utility that
>> has the same usage as /usr/bin/sendmail.
>
> Got it now.

I obviously did a bad job describing the problem, since I seemed to
have confused just about everybody.  I erred in leaving out what I
thought were irrelevant details.

-- 
Grant Edwards   grant.b.edwardsYow! Boy, am I glad it's
  at   only 1971...
  gmail.com

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Grant Taylor  wrote:
> On 01/19/2018 12:48 PM, Alan McKinnon wrote:
>> I'm also wondering why you need 2 bits. Earlier in the thread you 
>> mentioned that you send perhaps a few messages a week and never more 
>> than one connection at a time.
>
> Grant E. has indicated elsewhere in the thread that his
> /usr/bin/sendmail script is speaking something custom to the
> destination mail server.
>
> Read:  /usr/bin/sendmail script is NOT speaking SMTP.

Yes.  I should have been more clear about that. 

> Do you know what protocol(s) that Grant E.'s /usr/bin/sendmail script is 
> speaking?  Do you know if ssmtp (et al) support it?

It involves doing things remotely using the ssh-2 protocol.

> I feel like Grant E. has not revealed enough information to know if
> other things can speak what ever custom communications is possible
> between the SMTP server and the destination mail server.  He has
> only revealed enough to know that it is custom, and that his
> /usr/bin/sendmail interface script must be used.

Yes, I have assumed that normal MTAs like sendmail and postfix do not
implement the ssh protocol and can't be made to do what my
/usr/bin/sendmail script does.

> I don't think there is enough information to know that ssmtp / postfix / 
> exim / sendmail / et al are capable of speaking the protocols that Grant 
> E. needs or wants.

I am confident they do not, but I'm not going to go into details on
how the ssh-protocol-based delivery works.

-- 
Grant Edwards   grant.b.edwardsYow! This PIZZA symbolizes
  at   my COMPLETE EMOTIONAL
  gmail.comRECOVERY!!

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 12:48 PM, Grant Edwards wrote:
Yep, and it looks like the Postfix equivalent is a custom pipe transport. 
Once you know what phrases to google for, it's a lot easier.


*nod*

I figured that you would be able to find something.

Hence why I mentioned the terms.  ;-)

I could live with queueing/retrying as long as the eventual failures 
generated messages that are sent back to the sender.  Those failure 
messages would need to be sent via a normal SMTP smarthost/relayhost 
(with AUTH) and not via the custom mailer.


I would expect that it is possible to fulfill those requirements.

Yes, I've been thinking about that.  I think I'll try that first -- 
if my understanding of the failure mode is correct, it should work.


The simpler solution is usually nicer.

I wrote the server I'm using now, but it uses somebody else's snmpd 
module, and that's where the SSL breakage is.  I've filed a bug, and I've 
been doing some reading toward attempting a fix, but it looks like it 
might be a bit hairy: it involves Python's asyncore/asynchat framework 
(and process pools).  What's missing is handling for ssl "want read" 
and "want write" exceptions.


"snmpd" or "smtpd"?

You lost me at Python.  (I know it's a personal prejudice.  But I think 
I'm allowed to have it as long as I acknowledge them as such.)




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Alan McKinnon]

On 19/01/2018 22:03, Grant Edwards wrote:
> On 2018-01-19, Alan McKinnon  wrote:
>> On 19/01/2018 21:54, Grant Edwards wrote:
>>> On 2018-01-19, Ian Zimmerman  wrote:
 On 2018-01-19 18:49, Grant Edwards wrote:

>> Just like the others writing in this thread, I am wondering why you
>> need 2 pieces here.  Why won't e.g. exim do both sides of this for
>> you?  It certainly has all the functionality.
>
> I don't see how you can say that when you don't know the method that
> my command-line MTA uses to transfer mail on down the path towards
> delivery.

 I can say it because I have some experience with exim, and I know it can
 do pretty much anything.  If its configuration language isn't Turing
 complete, it is quite damn close to it.  And the same can be said of
 sendmail, though I know much less about it know.
>>>
>>> Can exim transfer mail to an Exchange server that doesn't expose an
>>> SMTP server?
>>
>> Errr, no. exim does SMTP.
>>
>> If the above is what you need, any orthodox mail server would need to
>> hand the mail over to something that *can* deliver to Exchange.
> 
> Yes, and that something is my existing command-line MTA utility that
> has the same usage as /usr/bin/sendmail.
> 

Got it now.

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Alan McKinnon]

On 19/01/2018 22:01, Grant Edwards wrote:
> On 2018-01-19, Alan McKinnon  wrote:
>> On 19/01/2018 21:43, Ian Zimmerman wrote:
>>> On 2018-01-19 18:49, Grant Edwards wrote:
>>>
> Just like the others writing in this thread, I am wondering why you
> need 2 pieces here.  Why won't e.g. exim do both sides of this for
> you?  It certainly has all the functionality.

 I don't see how you can say that when you don't know the method that
 my command-line MTA uses to transfer mail on down the path towards
 delivery.
>>>
>>> I can say it because I have some experience with exim, and I know it can
>>> do pretty much anything.  If its configuration language isn't Turing
>>> complete, it is quite damn close to it.  And the same can be said of
>>> sendmail, though I know much less about it know.
>>
>> I'm also wondering why you need 2 bits. Earlier in the thread you
>> mentioned that you send perhaps a few messages a week and never more
>> than one connection at a time.
>>
>> Why do you need anything more complex than ssmtp?
> 
> I'm not just _sending_ mail.  I'm relaying mail that's being sent by
> another host.  I need an SMTP server that supports AUTH and SSL.

OK

> 
>> where are the messages coming from?  localhost?  the lan? somewhere
>> on the internet?
> 
> SMTP clients (on the Internet).  I thought that was sort of implied by
> the requirement for an SMTP server (with AUTH and SSL).

Well, sort of implied. The door was still open for all manner of other
interpretations. Eg, you have 10 staff but only 2 may send mail, so
authorize them by username and password - ssl, no internet. There are
many other possibles

> 
>> Grant, you should explain your requirements in detail.
> 
> I thought I did.
> 
> My requirement is to provide an SMTP server (with AUTH and SSL) that
> accepts mail and relays it by invoking a command-line utility that has
> the same usage as /usr/bin/sendmail.

Is it correct to assume this sendmail-like utility is the broken one
that does the next step as you want it, presumably delivering to Exchange?

Configure the delivery options in MTA you set up to pipe the mail to
this sendmail-like app. All MTAs can do that and they usually explain
how to at length in their docs

-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Alan McKinnon  wrote:
> On 19/01/2018 21:54, Grant Edwards wrote:
>> On 2018-01-19, Ian Zimmerman  wrote:
>>> On 2018-01-19 18:49, Grant Edwards wrote:
>>>
> Just like the others writing in this thread, I am wondering why you
> need 2 pieces here.  Why won't e.g. exim do both sides of this for
> you?  It certainly has all the functionality.

 I don't see how you can say that when you don't know the method that
 my command-line MTA uses to transfer mail on down the path towards
 delivery.
>>>
>>> I can say it because I have some experience with exim, and I know it can
>>> do pretty much anything.  If its configuration language isn't Turing
>>> complete, it is quite damn close to it.  And the same can be said of
>>> sendmail, though I know much less about it know.
>> 
>> Can exim transfer mail to an Exchange server that doesn't expose an
>> SMTP server?
>
> Errr, no. exim does SMTP.
>
> If the above is what you need, any orthodox mail server would need to
> hand the mail over to something that *can* deliver to Exchange.

Yes, and that something is my existing command-line MTA utility that
has the same usage as /usr/bin/sendmail.

-- 
Grant Edwards   grant.b.edwardsYow! HELLO KITTY gang
  at   terrorizes town, family
  gmail.comSTICKERED to death!

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 12:48 PM, Alan McKinnon wrote:
I'm also wondering why you need 2 bits. Earlier in the thread you 
mentioned that you send perhaps a few messages a week and never more 
than one connection at a time.


Grant E. has indicated elsewhere in the thread that his 
/usr/bin/sendmail script is speaking something custom to the destination 
mail server.


Read:  /usr/bin/sendmail script is NOT speaking SMTP.

Why do you need anything more complex than ssmtp?  where are the messages 
coming from? localhost? the lan? somewhere on the internet?


Do you know what protocol(s) that Grant E.'s /usr/bin/sendmail script is 
speaking?  Do you know if ssmtp (et al) support it?


I feel like Grant E. has not revealed enough information to know if 
other things can speak what ever custom communications is possible 
between the SMTP server and the destination mail server.  He has only 
revealed enough to know that it is custom, and that his 
/usr/bin/sendmail interface script must be used.


Grant, you should explain your requirements in detail, and not describe 
what you currently have (broken, as you say). Otherwise I'm going to 
give you boilerplate advice:


Arguably Grant E. has described his requirements.  -  That being said, 
questioning the motivation behind the requirements is worth exploring 
far enough to see if it's pertinent.


Grant E. has also, revealed that the broken bit is more the lack of 
functional encryption support, not lack of overall functionality.  Thus 
I feel like "currently have (broken, as you say)" is inaccurate.


Use ssmtp, unless the mail isn't coming from localhost and you need simple 
(use postfix); otherwise if your setup is tricky use exim.


I don't think there is enough information to know that ssmtp / postfix / 
exim / sendmail / et al are capable of speaking the protocols that Grant 
E. needs or wants.




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Alan McKinnon  wrote:
> On 19/01/2018 21:43, Ian Zimmerman wrote:
>> On 2018-01-19 18:49, Grant Edwards wrote:
>> 
 Just like the others writing in this thread, I am wondering why you
 need 2 pieces here.  Why won't e.g. exim do both sides of this for
 you?  It certainly has all the functionality.
>>>
>>> I don't see how you can say that when you don't know the method that
>>> my command-line MTA uses to transfer mail on down the path towards
>>> delivery.
>> 
>> I can say it because I have some experience with exim, and I know it can
>> do pretty much anything.  If its configuration language isn't Turing
>> complete, it is quite damn close to it.  And the same can be said of
>> sendmail, though I know much less about it know.
>
> I'm also wondering why you need 2 bits. Earlier in the thread you
> mentioned that you send perhaps a few messages a week and never more
> than one connection at a time.
>
> Why do you need anything more complex than ssmtp?

I'm not just _sending_ mail.  I'm relaying mail that's being sent by
another host.  I need an SMTP server that supports AUTH and SSL.

> where are the messages coming from?  localhost?  the lan? somewhere
> on the internet?

SMTP clients (on the Internet).  I thought that was sort of implied by
the requirement for an SMTP server (with AUTH and SSL).

> Grant, you should explain your requirements in detail.

I thought I did.

My requirement is to provide an SMTP server (with AUTH and SSL) that
accepts mail and relays it by invoking a command-line utility that has
the same usage as /usr/bin/sendmail.

-- 
Grant Edwards   grant.b.edwardsYow! I'm a nuclear
  at   submarine under the
  gmail.compolar ice cap and I need
   a Kleenex!

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Ian Zimmerman  wrote:
> On 2018-01-19 18:49, Grant Edwards wrote:
>
>> > Just like the others writing in this thread, I am wondering why you
>> > need 2 pieces here.  Why won't e.g. exim do both sides of this for
>> > you?  It certainly has all the functionality.
>> 
>> I don't see how you can say that when you don't know the method that
>> my command-line MTA uses to transfer mail on down the path towards
>> delivery.
>
> I can say it because I have some experience with exim, and I know it can
> do pretty much anything.  If its configuration language isn't Turing
> complete, it is quite damn close to it.  And the same can be said of
> sendmail, though I know much less about it know.

Can exim transfer mail to an Exchange server that doesn't expose an
SMTP server?

-- 
Grant Edwards   grant.b.edwardsYow! It's the RINSE CYCLE!!
  at   They've ALL IGNORED the
  gmail.comRINSE CYCLE!!

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Alan McKinnon]

On 19/01/2018 21:43, Ian Zimmerman wrote:
> On 2018-01-19 18:49, Grant Edwards wrote:
> 
>>> Just like the others writing in this thread, I am wondering why you
>>> need 2 pieces here.  Why won't e.g. exim do both sides of this for
>>> you?  It certainly has all the functionality.
>>
>> I don't see how you can say that when you don't know the method that
>> my command-line MTA uses to transfer mail on down the path towards
>> delivery.
> 
> I can say it because I have some experience with exim, and I know it can
> do pretty much anything.  If its configuration language isn't Turing
> complete, it is quite damn close to it.  And the same can be said of
> sendmail, though I know much less about it know.
> 

I'm also wondering why you need 2 bits. Earlier in the thread you
mentioned that you send perhaps a few messages a week and never more
than one connection at a time.

Why do you need anything more complex than ssmtp?
where are the messages coming from? localhost? the lan? somewhere on the
internet?

Grant, you should explain your requirements in detail, and not describe
what you currently have (broken, as you say). Otherwise I'm going to
give you boilerplate advice:

Use ssmtp, unless the mail isn't coming from localhost and you need
simple (use postfix); otherwise if your setup is tricky use exim.

-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Grant Taylor  wrote:
> On 01/19/2018 11:38 AM, Grant Edwards wrote:
>
>> I have a /usr/bin/sendmail emulator that transfers mail to an MTA
>> that will then worry about delivery.  I need an SMTP server that
>> will relay incoming mail by using that existing command-line
>> utility.
> …
>> I need something that accepts mail via SMTP (with SSL and AUTH
>> support), and then relays each received message by invoking a
>> command line utilty that has the same API as /usr/bin/sendmail.
>
> You want (what Sendmail calls) a custom mailer.

Yep, and it looks like the Postfix equivalent is a custom pipe
transport.  Once you know what phrases to google for, it's a lot
easier. :)

>> I would very much prefer that there is no queueing: the smtp server
>> should not acknowlege acceptance of the message until the smtp
>> server has invoked /usr/bin/sendmail and it has returned success.
>
> That's possible.  But it does add some additional constraints.  It
> also means that traditional MTAs likely won't operate the way that
> you want this to.

I could live with queueing/retrying as long as the eventual failures
generated messages that are sent back to the sender.  Those failure
messages would need to be sent via a normal SMTP smarthost/relayhost
(with AUTH) and not via the custom mailer.

> Have you tried putting ssltunnel (or the likes) in front of your
> existing SMTP server to see if it (they) can handle STARTTLS for
> you?  - Is it possible to augment your existing solution without
> needing to replace it?

Yes, I've been thinking about that.  I think I'll try that first -- if
my understanding of the failure mode is correct, it should work.

> Also, this sounds use case specific enough that I would consider
> going back to the person maintaining the scrip SMTP server that
> you're currently using and try to fix it.

I wrote the server I'm using now, but it uses somebody else's snmpd
module, and that's where the SSL breakage is.  I've filed a bug, and
I've been doing some reading toward attempting a fix, but it looks
like it might be a bit hairy: it involves Python's asyncore/asynchat
framework (and process pools).  What's missing is handling for ssl
"want read" and "want write" exceptions.

-- 
Grant Edwards   grant.b.edwardsYow! FEELINGS are cascading
  at   over me!!!
  gmail.com

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Ian Zimmerman]

On 2018-01-19 18:49, Grant Edwards wrote:

> > Just like the others writing in this thread, I am wondering why you
> > need 2 pieces here.  Why won't e.g. exim do both sides of this for
> > you?  It certainly has all the functionality.
> 
> I don't see how you can say that when you don't know the method that
> my command-line MTA uses to transfer mail on down the path towards
> delivery.

I can say it because I have some experience with exim, and I know it can
do pretty much anything.  If its configuration language isn't Turing
complete, it is quite damn close to it.  And the same can be said of
sendmail, though I know much less about it know.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 11:59 AM, Grant Edwards wrote:
I meant the sematics and sytax of the command line options and the data 
accepted on stdin and produced on stdout.  I probably should have said 
"usage" rather than API.  Since I always use that utility from a Python 
or Bash program, in my head that's its API.


I figured that's what you mean.  I agree that's effectively what it has 
become.


I think I've read too many "the command line is not an API" blog 
articles recently.



Exactly.


;-)


Thanks.


You're welcome.


I was sort of afraid that sendmail was going to be the answer.


Not necessarily.

I expect that any modern MTA can be configured to behave the same way.

The last time I ran sendmail was on a Sun-3/60 machine, and I never did 
quite understand how to configure it...


Wow.  I bet that was pre-m4 configuration days.  -  I've been running 
Sendmail (by choice) for ~18 years and have always used m4 to configure 
it.  -  From what I've heard, the pre-m4 days were a LOT more difficult.


I expect that what you're wanting to do can be done in less than an 
hour.  Maybe even less than half an hour.


Let me know if you want pointers from a Sendmail vet that's built 
(re)built a Gentoo server with Sendmail, functioning as a backup MX w/ 
filtering, in the last month.  (I converted from CentOS 6.x to Gentoo - 
17.0 profile.)




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Grant Taylor  wrote:

> So you don't need to accept mail via /usr/sbin/sendmail (et al).

Correct.

> Or rather, that's what you want email to leave the relay through.

Correct.

>> I want to relay each of those messages by invoking a command-line
>> utility that has the same "API" as /usr/bin/sendmail.  That utility
>> injects the mail into another machine's MTA.
>
> Okay.
>
> Aside: I don't know that I would consider that to be an API, but I
> do see why you consider it as such.

I meant the sematics and sytax of the command line options and the
data accepted on stdin and produced on stdout.  I probably should have
said "usage" rather than API.  Since I always use that utility from a
Python or Bash program, in my head that's its API.

>> In this case, the /usr/bin/sendmail utility transfers the message
>> to a different machine's MTA using mechanisms that are beyond the
>> scope of my question.
>
> Okay.
>
> So it sounds to me like you want a gateway of sorts that speaks SMTP
> (as a server to clients) on one side and  method> (that acts as a client to other servers) on the other side.
> Is that accurate?

Exactly.

> In Sendmail parlance, what you want is a custom mailer.  Said custom
> mailer would then interface with your custom /usr/bin/sendmail
> (emulation wrapper).
>
> Finally, configure Sendmail to use said custom mailer as the method
> to communicate with the smart host.

Thanks.

I was sort of afraid that sendmail was going to be the answer. :)

The last time I ran sendmail was on a Sun-3/60 machine, and I never
did quite understand how to configure it...

-- 
Grant Edwards   grant.b.edwardsYow! Loni Anderson's hair
  at   should be LEGALIZED!!
  gmail.com

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 11:38 AM, Grant Edwards wrote:
I have a /usr/bin/sendmail emulator that transfers mail to an MTA that 
will then worry about delivery.  I need an SMTP server that will relay 
incoming mail by using that existing command-line utility.


…

I need something that accepts mail via SMTP (with SSL and AUTH support), 
and then relays each received message by invoking a command line utilty 
that has the same API as /usr/bin/sendmail.


You want (what Sendmail calls) a custom mailer.


There is no local delivery and no acceptance of mail other than via SMTP.


That's probably mostly immaterial.  Aside from the fact that you would 
not add those features if you were write a custom SMTP gateway.  Most 
MTAs will have that, but it can be ignored.


I would very much prefer that there is no queueing: the smtp server 
should not acknowlege acceptance of the message until the smtp server 
has invoked /usr/bin/sendmail and it has returned success.


That's possible.  But it does add some additional constraints.  It also 
means that traditional MTAs likely won't operate the way that you want 
this to.


Have you tried putting ssltunnel (or the likes) in front of your 
existing SMTP server to see if it (they) can handle STARTTLS for you?  - 
 Is it possible to augment your existing solution without needing to 
replace it?


Also, this sounds use case specific enough that I would consider going 
back to the person maintaining the scrip SMTP server that you're 
currently using and try to fix it.




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Ian Zimmerman  wrote:
> On 2018-01-19 18:03, Grant Edwards wrote:
>
>> It needs to accept messages as an SMTP server (using SSL and AUTH on a
>> non-standard port) from a single user and single source and then relay
>> them by passing them to a command-line MTA (e.g. /usr/bin/sendmail
>> replacement provided by msmtp).
>
> Just like the others writing in this thread, I am wondering why you need
> 2 pieces here.  Why won't e.g. exim do both sides of this for you?
> It certainly has all the functionality.

I don't see how you can say that when you don't know the method that
my command-line MTA uses to transfer mail on down the path towards
delivery.

-- 
Grant Edwards   grant.b.edwardsYow! I was born in a
  at   Hostess Cupcake factory
  gmail.combefore the sexual
   revolution!

Re: [gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 11:31 AM, Grant Edwards wrote:

I want to accept incoming email via SMTP (my computer is an SMTP server).


Okay.

So you don't need to accept mail via /usr/sbin/sendmail (et al).

Or rather, that's what you want email to leave the relay through.

I want to relay each of those messages by invoking a command-line utility 
that has the same "API" as /usr/bin/sendmail.  That utility injects the 
mail into another machine's MTA.


Okay.

Aside:  I don't know that I would consider that to be an API, but I do 
see why you consider it as such.


In this case, the /usr/bin/sendmail utility transfers the message to a 
different machine's MTA using mechanisms that are beyond the scope of 
my question.


Okay.

There is no local delivery.  It is a relay that accepts mail via SMTP and 
transfers it to a different MTA.  The usual way to do this is to accept 
mail as an SMTP server and then relay it to the next MTA by acting as 
an SMTP client (e.g. via postfix's 'relayhost' setting).


Instead of transfering mail to the next MTA by acting as an SMTP client, 
I want to transfer it by invoking a command-line utility like sendmail 
or msmtp.


So it sounds to me like you want a gateway of sorts that speaks SMTP (as 
a server to clients) on one side and  (that 
acts as a client to other servers) on the other side.  Is that accurate?


In Sendmail parlance, what you want is a custom mailer.  Said custom 
mailer would then interface with your custom /usr/bin/sendmail 
(emulation wrapper).


Finally, configure Sendmail to use said custom mailer as the method to 
communicate with the smart host.




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Ian Zimmerman]

On 2018-01-19 18:03, Grant Edwards wrote:

> It needs to accept messages as an SMTP server (using SSL and AUTH on a
> non-standard port) from a single user and single source and then relay
> them by passing them to a command-line MTA (e.g. /usr/bin/sendmail
> replacement provided by msmtp).

Just like the others writing in this thread, I am wondering why you need
2 pieces here.  Why won't e.g. exim do both sides of this for you?  It
certainly has all the functionality.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Grant Taylor  wrote:

> I haven't done enough with the above (alternate) MTAs to be able to
> speak to them.  But my understanding is that they come with a
> /path/to/sendmail wrapper script (or binary) that emulates part of
> what the sendmail binary did.  At least the portions there of that
> clients use to submit email the way that you're talking.

I have a /usr/bin/sendmail emulator that transfers mail to an MTA that
will then worry about delivery.  I need an SMTP server that will relay
incoming mail by using that existing command-line utility.

>> I'm currently using something I wrote in Python, but the SSL
>> support in the 3rd party SMTP module is broken and I don't relish
>> trying to fix it.
>
> Do you actually need a local MTA (daemon)?  Or do you just need
> something smart enough to accept messages from standard in and pass
> them out via a smart host?

I need something that accepts mail via SMTP (with SSL and AUTH
support), and then relays each received message by invoking a command
line utilty that has the same API as /usr/bin/sendmail.

There is no local delivery and no acceptance of mail other than via
SMTP.  

I would very much prefer that there is no queueing: the smtp server
should not acknowlege acceptance of the message until the smtp server
has invoked /usr/bin/sendmail and it has returned success.

-- 
Grant Edwards   grant.b.edwardsYow! I've read SEVEN
  at   MILLION books!!
  gmail.com

[gentoo-user] Re: Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

On 2018-01-19, Ralph Seichter  wrote:
> On 19.01.18 19:03, Grant Edwards wrote:
>
>> I need to setup an SMTP relay server.
>>
>> It needs to accept messages as an SMTP server (using SSL and AUTH on a
>> non-standard port) from a single user and single source and then relay
>> them by passing them to a command-line MTA (e.g. /usr/bin/sendmail
>> replacement provided by msmtp).
>
> Based on your description you seem to have things backward.

I want to accept incoming email via SMTP (my computer is an SMTP server).

I want to relay each of those messages by invoking a command-line
utility that has the same "API" as /usr/bin/sendmail.  That utility
injects the mail into another machine's MTA.

> Sendmail is used to inject mail into an MTA on the local machine,
> and the MTA can then use SMTP to transfer said mail to another
> server.

In this case, the /usr/bin/sendmail utility transfers the message to a
different machine's MTA using mechanisms that are beyond the scope of
my question.

> If the final recipient (i.e. mailbox) is on the same server the mail is
> generated on, the MTA can use a local transport mechanism to store mail
> instead of passing it on via SMTP.

There is no local delivery.  It is a relay that accepts mail via SMTP
and transfers it to a different MTA.  The usual way to do this is to
accept mail as an SMTP server and then relay it to the next MTA by
acting as an SMTP client (e.g. via postfix's 'relayhost' setting).

Instead of transfering mail to the next MTA by acting as an SMTP
client, I want to transfer it by invoking a command-line utility like
sendmail or msmtp.
 
> I suggest you clarify your goal, and ask on the Postfix mailing list
> (or Exim, etc.) for more information.

Will do.

-- 
Grant Edwards   grant.b.edwardsYow! Everywhere I look I
  at   see NEGATIVITY and ASPHALT
  gmail.com...

Re: [gentoo-user] Simple SMTP to cmd-line MTA relay?

[Grant Taylor]

On 01/19/2018 11:03 AM, Grant Edwards wrote:

I need to setup an SMTP relay server.


Okay.

It needs to accept messages as an SMTP server (using SSL and AUTH on a 
non-standard port) from a single user and single source and then relay 
them by passing them to a command-line MTA (e.g. /usr/bin/sendmail 
replacement provided by msmtp).


I'm not completely clear on what you're wanting.  But it sounds like you 
want to be able to send email by passing the output of  into 
the input of /usr/sbin/sendmail (or the likes).  Is th


It only needs to handle a few messages per week, and doesn't need to 
handle more than one connection at a time.


IMHO the number of message is mostly immaterial.


 exim?
 postfix?
 emailrelay?


My personal MTA of choice is sendmail.

What I can't figure out for the above is how you configure them to send 
the mail using a command line MTA like /usr/bin/sendmail or /usr/bin/msmtp 
instead of initiating a network connection to an SMTP server.


I haven't done enough with the above (alternate) MTAs to be able to 
speak to them.  But my understanding is that they come with a 
/path/to/sendmail wrapper script (or binary) that emulates part of what 
the sendmail binary did.  At least the portions there of that clients 
use to submit email the way that you're talking.


I'm currently using something I wrote in Python, but the SSL support in 
the 3rd party SMTP module is broken and I don't relish trying to fix it.


Do you actually need a local MTA (daemon)?  Or do you just need 
something smart enough to accept messages from standard in and pass them 
out via a smart host?


IMHO this is trivial to do with Sendmail, and how I would do it.  If you 
want to go that route, let me know and I'm happy to help.




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [gentoo-user] Simple SMTP to cmd-line MTA relay?

[Ralph Seichter]

On 19.01.18 19:03, Grant Edwards wrote:

> I need to setup an SMTP relay server.
>
> It needs to accept messages as an SMTP server (using SSL and AUTH on a
> non-standard port) from a single user and single source and then relay
> them by passing them to a command-line MTA (e.g. /usr/bin/sendmail
> replacement provided by msmtp).

Based on your description you seem to have things backward. Sendmail is
used to inject mail into an MTA on the local machine, and the MTA can
then use SMTP to transfer said mail to another server.

If the final recipient (i.e. mailbox) is on the same server the mail is
generated on, the MTA can use a local transport mechanism to store mail
instead of passing it on via SMTP.

I suggest you clarify your goal, and ask on the Postfix mailing list
(or Exim, etc.) for more information.

-Ralph

[gentoo-user] Simple SMTP to cmd-line MTA relay?

[Grant Edwards]

I need to setup an SMTP relay server.

It needs to accept messages as an SMTP server (using SSL and AUTH on a
non-standard port) from a single user and single source and then relay
them by passing them to a command-line MTA (e.g. /usr/bin/sendmail
replacement provided by msmtp).

It only needs to handle a few messages per week, and doesn't need to
handle more than one connection at a time.

 exim?
 postfix?   
 emailrelay?

What I can't figure out for the above is how you configure them to
send the mail using a command line MTA like /usr/bin/sendmail or
/usr/bin/msmtp instead of initiating a network connection to an SMTP
server.

I'm currently using something I wrote in Python, but the SSL support
in the 3rd party SMTP module is broken and I don't relish trying to
fix it.

-- 
Grant Edwards   grant.b.edwardsYow! S!!  I hear SIX
  at   TATTOOED TRUCK-DRIVERS
  gmail.comtossing ENGINE BLOCKS into
   empty OIL DRUMS ...

Re: [gentoo-user] www-client/chromium-63.0.3239.132

[Rich Freeman]

On Fri, Jan 19, 2018 at 12:04 PM, Mick  wrote:
>
> On my old i7 laptop it eats up all 4G of RAM and 4G of swap before it conks
> out.  So, I dropped the jobs to 3 and --load-average to 2, added a swapfile to
> increase disk space and it now builds in around 13 hours.
>
> I have not used jumbo-build, but perhaps I should?

Well, you can certainly try, but since jumbo-build increases memory
use, I suspect you might not be able to get it to complete at all even
with -j1.  If it did build there is a good chance it would complete
faster, even using fewer cores.

I'm not sure how exactly jumbo-build combines source files.  Hopefully
it does it in a way that is consistent each time, so that ccache has
some chance of getting hits between builds.  That would actually be an
advantage to compiling with many smaller units - you might get more
cache hits.  That is, assuming there aren't header changes in new
releases that invalidate large number of cache entries.

-- 
Rich

Re: [gentoo-user] www-client/chromium-63.0.3239.132

[Mick]

On Friday, 19 January 2018 13:29:51 GMT Rich Freeman wrote:
> On Fri, Jan 19, 2018 at 12:26 AM, victor romanchuk  
wrote:
> >  local:jumbo-build:www-client/chromium: Combine source files to speed up
> >  build process.> 
> > setting that significantly speeds up emerge time (tried it twice; the
> > second attempt had the flag set)
> > 
> > $ qlop -gHv -d `date +%Y-%m-%d` chromium
> > chromium-63.0.3239.132: Fri Jan 19 03:15:43 2018: 1 hour, 47 minutes, 28
> > seconds chromium-63.0.3239.132: Fri Jan 19 06:11:06 2018: 1 hour, 16
> > minutes, 14 seconds chromium: 2 times
> 
> There is a CPU-memory tradeoff here.  Combining source files reduces
> duplication of #include directives which greatly cuts down on the
> number of lines of code going into the compiler, but the individual
> files being compiled are larger.
> 
> I have a 12 SMT-core Ryzen 5-1600, and 16GB of RAM.  I can't even
> build chromium on a tmpfs because the RAM+space requirements have
> grown, so I build on an SSD.  Even without the tmpfs I have to reduce
> make to -j11 or it will OOM during a build WITHOUT the jumbo-build
> flag.  So, I'm already hitting RAM limitations on build time.
> 
> That said, I've experimented with some build times and I found that I
> can build chromium faster with -j8 using jumbo-build (the max # jobs I
> can run reliably without OOM) than I can build it with -j11 without
> using the new feature.  I'll also note that to do this I have to make
> sure nothing else is compiling at the same time, and sometimes I end
> up stopping a container that runs mono for good measure.
> 
> I do use ccache in general with chromium but I did my benchmarking without
> it.
> 
> I suggest experimenting with jumbo-build, and consider reducing
> parallel jobs if you run into OOM, but depending on your system you
> might find it not worth the trouble.
> 
> One thing I haven't experimented with is reducing -j even further and
> then moving back to a tmpfs.  I could easily see a tmpfs for building
> outperforming jumbo-build even if I end up at -j4 or less.  Then
> again, the SSD probably isn't as bad a drag as a spinning disk would
> be.
> 
> I was chatting with somebody (I think on reddit) who mentioned
> jumbo-build worked fine on a threadripper with 64GB of RAM (that would
> be -j32 I suppose).  I bet that with even a few more GB of RAM I could
> probably max out my 12 SMT cores.
> 
> I can't wait to see how chromium-64 behaves.  The RAM requirements
> have been steadily going up.  I have an older system with only 4GB RAM
> and it struggles to even build chromium at all.

On my old i7 laptop it eats up all 4G of RAM and 4G of swap before it conks 
out.  So, I dropped the jobs to 3 and --load-average to 2, added a swapfile to 
increase disk space and it now builds in around 13 hours.

I have not used jumbo-build, but perhaps I should?
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: USB3 external storage HD's

[Wols Lists]

On 18/01/18 21:22, mad.scientist.at.la...@tutanota.com wrote:
>  if you're going with external drives use laptop drives, or build a JBOD
> with good cooling.  in any case, monitor drive temperatures, in my
> experiance anything above 100F is asking for a short life, bellow or at
> 100F drives new and old are happy for over a decade which seems like a
> long time, but most of us have data on older machines with older drives
> somewhere in the house and most don't back that up or back it up often
> enough.  also note that most usb adapters don't even allow smart access,
> so the only way to see if the drive's hot is to feel the enclosure which
> is not terribly accurate or usefull.  it's also really nice to be able
> to run smart diagnostics and have the os monitor the smart status which
> most versions of linux will do, don't know about winblows, haven't run
> that since xp.

https://www.crowdsupply.com/gnubee/personal-cloud-2

There's an article about this on LWN, which is where I picked this up,
but unfortunately it's currently subscribers-only and I'm not a
subscriber, so I can't post a link to that.

Cheers,
Wol

Re: [gentoo-user] Re: USB3 external storage HD's

[Rich Freeman]

On Fri, Jan 19, 2018 at 8:49 AM,   wrote:
> On 01/19/2018 02:30 AM, Peter Humphrey wrote:
>> On Thursday, 18 January 2018 18:45:41 GMT Nikos Chantziaras wrote:
>>> On 18/01/18 20:33, the...@sys-concept.com wrote:
 Do those External Storage work with Linux (USB3)?
 I don't want to install any ventor-software, I just want one that plugs
 and play.

 Any recommendations?
>>>
>>> My USB 3 stick works fine, at its full advertised speed (190MB/s read,
>>> 100MB/s write.) So an HD should work fine though. There's no third-party
>>> drivers needed.
>>
>> I've been using two bog-standard USB-3 Seagate expansion drives for a couple
>> of years. They're for whole-system backups of my Gentoo boxes, so they
>> aren't exactly heavily stressed. I haven't measured their speeds, but
>> they're much faster than the USB-2 drives I had before them.
>
> Maybe SSD would perform better, but they are not cheap.
>

Usually you want larger-scale external storage for things like
backup/archival, and those don't demand low latency.  A spinning disk
has just as much sequential transfer speed as an SSD, and that is
probably what you're using it for.

I personally use 3.5" hard drives for external storage with a USB3
"enclosure" (more like a port multiplier - the disks just stick out of
it).  USB3 can keep up with the data rates on 1-2 hard drives, and
these kinds of enclosures are dirt cheap anyway.  I find it useful for
things like archives, wiping drives, and also swapping drives (I can
swap a RAID drive with one in the enclosure easily without taking the
box apart, and then I can swap the physical drive location at my
convenience to free up the enclosure).  For archival I tend to use old
drives that I've otherwise outgrown and I just put them in RAID pairs.
Occasionally I dust them off and scrub them.  This is all just
personal data that often is in multiple places (encrypted S3, etc), so
I don't mind being casual.  Tapes would be a more rigorous solution
but at my scale the hardware is just way too expensive to justify.

-- 
Rich

Re: [gentoo-user] Re: USB3 external storage HD's

[thelma]

On 01/19/2018 02:30 AM, Peter Humphrey wrote:
> On Thursday, 18 January 2018 18:45:41 GMT Nikos Chantziaras wrote:
>> On 18/01/18 20:33, the...@sys-concept.com wrote:
>>> Do those External Storage work with Linux (USB3)?
>>> I don't want to install any ventor-software, I just want one that plugs
>>> and play.
>>>
>>> Any recommendations?
>>
>> My USB 3 stick works fine, at its full advertised speed (190MB/s read,
>> 100MB/s write.) So an HD should work fine though. There's no third-party
>> drivers needed.
> 
> I've been using two bog-standard USB-3 Seagate expansion drives for a couple 
> of years. They're for whole-system backups of my Gentoo boxes, so they 
> aren't exactly heavily stressed. I haven't measured their speeds, but 
> they're much faster than the USB-2 drives I had before them.

Maybe SSD would perform better, but they are not cheap.

Re: [gentoo-user] www-client/chromium-63.0.3239.132

[Rich Freeman]

On Fri, Jan 19, 2018 at 12:26 AM, victor romanchuk  wrote:
>  local:jumbo-build:www-client/chromium: Combine source files to speed up 
> build process.
>
> setting that significantly speeds up emerge time (tried it twice; the second 
> attempt had the flag set)
>
> $ qlop -gHv -d `date +%Y-%m-%d` chromium
> chromium-63.0.3239.132: Fri Jan 19 03:15:43 2018: 1 hour, 47 minutes, 28 
> seconds
> chromium-63.0.3239.132: Fri Jan 19 06:11:06 2018: 1 hour, 16 minutes, 14 
> seconds
> chromium: 2 times
>

There is a CPU-memory tradeoff here.  Combining source files reduces
duplication of #include directives which greatly cuts down on the
number of lines of code going into the compiler, but the individual
files being compiled are larger.

I have a 12 SMT-core Ryzen 5-1600, and 16GB of RAM.  I can't even
build chromium on a tmpfs because the RAM+space requirements have
grown, so I build on an SSD.  Even without the tmpfs I have to reduce
make to -j11 or it will OOM during a build WITHOUT the jumbo-build
flag.  So, I'm already hitting RAM limitations on build time.

That said, I've experimented with some build times and I found that I
can build chromium faster with -j8 using jumbo-build (the max # jobs I
can run reliably without OOM) than I can build it with -j11 without
using the new feature.  I'll also note that to do this I have to make
sure nothing else is compiling at the same time, and sometimes I end
up stopping a container that runs mono for good measure.

I do use ccache in general with chromium but I did my benchmarking without it.

I suggest experimenting with jumbo-build, and consider reducing
parallel jobs if you run into OOM, but depending on your system you
might find it not worth the trouble.

One thing I haven't experimented with is reducing -j even further and
then moving back to a tmpfs.  I could easily see a tmpfs for building
outperforming jumbo-build even if I end up at -j4 or less.  Then
again, the SSD probably isn't as bad a drag as a spinning disk would
be.

I was chatting with somebody (I think on reddit) who mentioned
jumbo-build worked fine on a threadripper with 64GB of RAM (that would
be -j32 I suppose).  I bet that with even a few more GB of RAM I could
probably max out my 12 SMT cores.

I can't wait to see how chromium-64 behaves.  The RAM requirements
have been steadily going up.  I have an older system with only 4GB RAM
and it struggles to even build chromium at all.

-- 
Rich

Re: [gentoo-user] Re: USB3 external storage HD's

[Peter Humphrey]

On Thursday, 18 January 2018 18:45:41 GMT Nikos Chantziaras wrote:
> On 18/01/18 20:33, the...@sys-concept.com wrote:
> > Do those External Storage work with Linux (USB3)?
> > I don't want to install any ventor-software, I just want one that plugs
> > and play.
> > 
> > Any recommendations?
> 
> My USB 3 stick works fine, at its full advertised speed (190MB/s read,
> 100MB/s write.) So an HD should work fine though. There's no third-party
> drivers needed.

I've been using two bog-standard USB-3 Seagate expansion drives for a couple 
of years. They're for whole-system backups of my Gentoo boxes, so they 
aren't exactly heavily stressed. I haven't measured their speeds, but 
they're much faster than the USB-2 drives I had before them.

-- 
Regards,
Peter.