Re: [gentoo-user] Basic questions about Distcc

2017-11-04 Thread mad.scientist.at.large
machines crashing during builds could also be a temperature problem as the 
drive, ram, network (in this case) and processor are all doing heavy lifting.  
if you launch a system monitor and try to compile on the laptops you can see 
why they are crashing, it should be in the logs as well.

mad.scientist.at.large (a good madscientist)
--

4. Nov 2017 13:30 by waltd...@waltdnes.org:


> On Fri, Nov 03, 2017 at 06:54:49PM +0200, Lasse Pouru wrote
>> I have a bunch of old laptops that large builds such as texlive
>> and ghc fail on, I'm assuming because of insufficient memory and
>> disk space. If I've understood correctly, with Distcc I could build
>> everything on my main desktop PC and have the binaries transferred
>> through network? How does this work, exactly, and is it a lot of
>> work to set up? I currently have no networking devices besides a
>> single modem/router, would something more be required?
>
>   My experiences with booby traps...
>
> * on the "old laptops" do *NOT* set "-march=native".  They'll dispatch
>   that flag to the compiler host, which will build "native" for the
>   compiler host... oops.  Instead, specify the the exact arch on the
>   client.  The compiler host will then build for that arch.  How do you
>   figure out the client's arch, you ask?  *ON THE CLIENT* (i.e. the old
>   laptop) run the command...
>
> gcc -c -Q -march=native --help=target | grep march=
>
>   ...and stick the result into "-march=" on the client
>
> * 32-bit clients should have a 32-bit build host.  If necessary, use a
>   32-bit QEMU VM or a 32-bit chroot on a 64-bit host.
>
> -- 
> Walter Dnes <> waltd...@waltdnes.org> >
> I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Re: Systemd

2017-11-04 Thread Canek Peláez Valdés
On Sat, Nov 4, 2017 at 12:17 PM, Nikos Chantziaras  wrote:
>
> On 04/11/17 18:15, siefke_lis...@web.de wrote:
>>
>> I have a short question to systemd. I would like to ask your experience
>> in the changeover. Was it easy? Were there problems?
>> Change or reinstall? What mean the profis here?
>
>
> I did both. Changed one system to systemd, re-installed one from scratch
with systemd.
>
> Both worked. The only problem I have with systemd is that it's unable to
reliably restore the ALSA mixer volumes/settings on startup. It fails 50%
of the time. Which is very annoying, but not the end of the world.

Do you have PulseAudio installed? What's the output of 'systemctl status
alsa-restore.service'? Do you have /var/lib under a "special" (RAID, LUKS,
whatever) partition?

Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México


Re: [gentoo-user] Systemd

2017-11-04 Thread siefke_lis...@web.de
On Sat, 04 Nov 2017 16:58:16 +
Neil Bothwick  wrote:

> It's pretty straightforward, just follow the wiki. The profile takes care of 
> setting the appropriate USE flags. One thing to watch out for is that systemd 
> will not pick up your openrc startup services so save the output from 
> rc-update - s then enable the services after changeover . 

That sounds good then I will do it. Thank you. 

Silvio



Re: [gentoo-user] Basic questions about Distcc

2017-11-04 Thread Walter Dnes
On Fri, Nov 03, 2017 at 06:54:49PM +0200, Lasse Pouru wrote
> I have a bunch of old laptops that large builds such as texlive
> and ghc fail on, I'm assuming because of insufficient memory and
> disk space. If I've understood correctly, with Distcc I could build
> everything on my main desktop PC and have the binaries transferred
> through network? How does this work, exactly, and is it a lot of
> work to set up? I currently have no networking devices besides a
> single modem/router, would something more be required?

  My experiences with booby traps...

* on the "old laptops" do *NOT* set "-march=native".  They'll dispatch
  that flag to the compiler host, which will build "native" for the
  compiler host... oops.  Instead, specify the the exact arch on the
  client.  The compiler host will then build for that arch.  How do you
  figure out the client's arch, you ask?  *ON THE CLIENT* (i.e. the old
  laptop) run the command...

gcc -c -Q -march=native --help=target | grep march=

  ...and stick the result into "-march=" on the client

* 32-bit clients should have a 32-bit build host.  If necessary, use a
  32-bit QEMU VM or a 32-bit chroot on a 64-bit host.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications



Re: [gentoo-user] Re: Systemd

2017-11-04 Thread Rich Freeman
On Sat, Nov 4, 2017 at 2:17 PM, Nikos Chantziaras  wrote:
> On 04/11/17 18:15, siefke_lis...@web.de wrote:
>>
>> I have a short question to systemd. I would like to ask your experience
>> in the changeover. Was it easy? Were there problems?
>> Change or reinstall? What mean the profis here?
>
>
> I did both. Changed one system to systemd, re-installed one from scratch
> with systemd.
>
> Both worked. The only problem I have with systemd is that it's unable to
> reliably restore the ALSA mixer volumes/settings on startup. It fails 50% of
> the time. Which is very annoying, but not the end of the world.
>

Out of curiosity - are you using alsa-state or alsa-restore?
Apparently alsa provides two different ways of preserving state.  You
might consider switching them (which is triggered by the existence of
/etc/alsa/state-daemon.conf - but it might have some other
requirements which I didn't bother to check on).

I've seen similar issues with iptables-restore.  To be fair those are
rare and I've also seen issues with that under openrc.

With any save/restore tool like these I always keep a copy of the
state somewhere where it doesn't get overwritten at shutdown if I have
a complex configuration.  If you get one of those situations where
something isn't detected by the kernel/udev/etc and then your state
gets blown away it is really nice to be able to run iptables-restore <
backupfile.

I believe the way alsa-restore operates is frowned upon in Gentoo
systemd circles, though to be honest I'm not sure what the specific
concern is.  The oneshot/RemainAfterExit approach seems
straightforward enough, and it is my guess that it is the upstream way
of doing things...

--
Rich



[gentoo-user] Re: Systemd

2017-11-04 Thread Nikos Chantziaras

On 04/11/17 18:15, siefke_lis...@web.de wrote:

I have a short question to systemd. I would like to ask your experience
in the changeover. Was it easy? Were there problems?
Change or reinstall? What mean the profis here?


I did both. Changed one system to systemd, re-installed one from scratch 
with systemd.


Both worked. The only problem I have with systemd is that it's unable to 
reliably restore the ALSA mixer volumes/settings on startup. It fails 
50% of the time. Which is very annoying, but not the end of the world.





[gentoo-user] Re: FYI: Daily / weekly / monthly cron jobs run twice on DST - non-DST transition

2017-11-04 Thread Ian Zimmerman
On 2017-11-04 01:39, Kai Peter wrote:

> > If you want to run a monthly job on a host that is not always on, do
> > you have to pretend it's an hourly job and check in the script
> > itself?
> 
> This is a special case to me. IMHO special cases have to be handled
> special or much better: avoid it.

Sorry, I don't get this.  How do you avoid this situation?  By not
having any monthly jobs?

-- 
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] Systemd

2017-11-04 Thread Neil Bothwick
It's pretty straightforward, just follow the wiki. The profile takes care of 
setting the appropriate USE flags. One thing to watch out for is that systemd 
will not pick up your openrc startup services so save the output from rc-update 
- s then enable the services after changeover . 

On 4 November 2017 16:15:39 GMT, "siefke_lis...@web.de"  
wrote:
>Hello, 
>
>I have a short question to systemd. I would like to ask your experience
>
>in the changeover. Was it easy? Were there problems?
>Change or reinstall? What mean the profis here?
>
>Thank you for help and have nice weekend.
>
>Silvio 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.



[gentoo-user] Systemd

2017-11-04 Thread siefke_lis...@web.de
Hello, 

I have a short question to systemd. I would like to ask your experience 
in the changeover. Was it easy? Were there problems?
Change or reinstall? What mean the profis here?

Thank you for help and have nice weekend.

Silvio 


pgpPdmay_r_Vp.pgp
Description: PGP signature