[GTALUG] systemd: prctl: add PR_{SET, GET}_CHILD_SUBREAPER was Re: Did I buy the wrong network card? (RTL8812AE)

[Russell]

On Wed, May 17, 2017 at 9:44 PM, Russell <rreiter91 at gmail.com> wrote:
I'm top posting this information in the general interest, as I didn't truly get full persistence with the instructions I posted previously.

Still not persistent but xsane works as colord profile now reports
Metadata:      OwnerCmdline=/usr/lib/colord/colord-sane

I just have to wake the service when I want to scan. This didn't work previously  until I fixed the ntp problem.

<snip the middle>

saned at 0.service
# Added by Russ for systemd requirements May 10, 2017

[Unit]
Description=Scanner Service
Requires=saned.socket

[Service]
ExecStart=/usr/sbin/saned
User=saned
Group=saned
StandardInput=null
StandardOutput=syslog
StandardError=syslog
Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255

> Device ID:     sane-Canon PIXMA MG2500 Series
> Metadata:      OwnerCmdline=
>
> Possible bug?
> https://mail.gnome.org/archives/gnome-color-manager-list/2011-December/msg00003.html
>
> Well on Ubuntu there is this.
>
> avahi_simple_poll_prepare
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286
>
> I've never heard Lennart Potterling speak, but right now I hear him in my head, in the voice of the Bandito from High Sierra, as he's saying ... POSIX we don't need no stinking POSIX.
>
<snip>

>> However, today cron.daily executed ntpdate correctly.
>>
>> root at HECTOR:~# systemctl status ntp.service
>> ● ntp.service - LSB: Start NTP daemon
>>    Loaded: loaded (/etc/init.d/ntp)
>>    Active: active (running) since Sun 2017-05-14 09:31:35 EDT; 22h ago
>>    CGroup: /system.slice/ntp.service
>>            └─22736 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 120:127
>>
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebec18a6d3aa1e7d84aab16225e87fd25170ec2b
>>
>> I've added this to my .bashrc as the authors of systemd recommend for further core troubleshooting.
>>
>> alias psc='ps xawf -eo pid,user,cgroup,args'
>>
>> On Sun, May 14, 2017 at 4:14 PM, Russell Reiter <rreiter91 at gmail.com> wrote:
>>> On Sat, May 13, 2017 at 1:55 PM, Stewart C. Russell via talk
>>> <talk at gtalug.org> wrote:
>>>> On 2017-05-13 12:24 PM, Russell wrote:
>>>>>
>>>>> This might be an ILP (Instruction Level Parallelisim) feature of systemd
>>>>> init.
>>>>>
>>>>> Take a look at how systemd deals with IVP routing tables using
>>>>> network.target here.
>>>>>
>>>>> https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
>>>>
>>>> Thanks, but I'm getting network, then it's periodically cutting out.
>>>> This seems to be more waiting for systemd to say "No, really, we've got
>>>> a network available" to services, rather than the network giving out. We
>>>> get to answer a lot of questions about systemd and network on the
>>>> Raspberry Pi forum, mostly about @reboot cron jobs not finding the
>>>> network.
>>>
>>> For now, perhaps you could help me out? Are you getting this following
>>> usbhid endpoint error?
>>>
>>> usbhid 1-2:1.0: couldn't find an input interrupt endpoint
>>>
>>> Also sorry I wasn't clear in my earlier post. The page link I provided was
>>> to the page NetworkTarget. network.target itself only indicates that the
>>> network management stack is up after it has been reached, It was the stuff
>>> below the "Cut the crap! How do I make network.target work for me", that I
>>> was referring to.
>>>
>>> The reason I ask is that, here on my stock Debian, I seem to have some
>>> confusion as an endpoint buffer, which firstly needs an endpoint descriptor,
>>> doesn't get one. If a service doesn't return NAK or STALL, the result seems
>>> to be a missing link beat.
>>>
>>> Once a core system acquires the target, you should be able to track that
>>> target by its Endpoint device description tables, in theory anyway.
>>>
>>> However, when something tries to shove a big endian bit into a little endian
>>> bucket, stuff is bound to spill over and mux something up.
>>>
>>> So far, I was able to sort out my own printer/scanner and a non-persistent
>>> scanner, by defining /lib/systemd/system
>>> - saned at .service
>>> -saned.socket
>>>
>>> Right now for a NTP issue I'm studying
>>> - After=network-online.target
>>> -Wants=network-online.target
>>>
>>> I dont have network dropping issue but some people who are dropping networks
>>> after the initial poll might have luck with.

>>>
>>> systemctl enable ifup-wait-all-auto.service
>>>
>>> Below is a quote from another link which also contains the suggested
>>> contents of ifup-wait-all-auto.service.
>>>
>>> https://unix.stackexchange.com/questions/209832/debian-systemd-network-online-target-not-working/217768#217768
>>>
>>> "Throw that beauty in /etc/systemd/system/ifup-wait-all-auto.service,
>>> install it with sudo systemctl enable ifup-wait-all-auto.service, and then
>>> actually have the network-online.target references in your systemd unit
>>> definitions work properly."
>>>
>>>
>>>>
>>>> Thanks, though. I suspect I'll have to make do with a very basic USB
>>>> wifi adapter (I bought Far Too Many for Raspberry Pis) until Scott's
>>>> suggested mPCIe adapter arrives.
>>>>
>>>> cheers,
>>>> Stewart
>>>>
>>>> ---
>>>> Talk Mailing List
>>>> talk at gtalug.org
>>>> https://gtalug.org/mailman/listinfo/talk
>>
>> --
>> Russell
>> Sent by K-9 Mail
>
> --
> Russell
> Sent by K-9 Mail

-- 
Russell
Sent by K-9 Mail