Hi,
for weekly updates, I'm using the usual update commands, such as
emerge -NDuv @world
emerge -c
revdep-rebuild -i
In order to find out which services are still using old versions
of updated programs/libraries, I add
lsof | grep -w DEL | grep portage
and /etc/init.d/XXX restart for those ser
Running kill on the current pids?
On Sat, Aug 12, 2017, 12:36 AM Matthias Hanft wrote:
> Hi,
>
> for weekly updates, I'm using the usual update commands, such as
>
> emerge -NDuv @world
> emerge -c
> revdep-rebuild -i
>
> In order to find out which services are still using old versions
> of upda
Logout and login again?
Matthias Hanft wrote:
> Hi,
>
> for weekly updates, I'm using the usual update commands, such as
>
> emerge -NDuv @world
> emerge -c
> revdep-rebuild -i
>
> In order to find out which services are still using old versions
> of updated programs/libraries, I add
>
> lsof | grep -w DEL | grep portage
On Sat, Aug 12, 2017 at 3:35 AM, Matthias Hanft wrote:
>
> But now, there's agetty left, and I don't know how to restart this
> service (without reboot):
>
This is because these are run directly by init and not by openrc,
unlike all the other daemons on the system. As others pointed out you
can
Dale wrote:
>
> I do it this way.
> pkill agetty
> Simple, quick and easy to remember. One could script it I guess???
I'm pretty sure this would work, but is there something which would
start them again? As far as I understand, these are the processes
that provide console login - correct? Nor
On Sat, Aug 12, 2017 at 4:22 AM, Matthias Hanft wrote:
> Dale wrote:
>>
>> I do it this way.
>> pkill agetty
>> Simple, quick and easy to remember. One could script it I guess???
>
> I'm pretty sure this would work, but is there something which would
> start them again? As far as I understand, t
Rich Freeman wrote:
> On Sat, Aug 12, 2017 at 4:22 AM, Matthias Hanft wrote:
>> Dale wrote:
>>> I do it this way.
>>> pkill agetty
>>> Simple, quick and easy to remember. One could script it I guess???
>> I'm pretty sure this would work, but is there something which would
>> start them again? As
On 12/08/17 10:35, Matthias Hanft wrote:
Hi,
for weekly updates, I'm using the usual update commands, such as
emerge -NDuv @world
emerge -c
revdep-rebuild -i
In order to find out which services are still using old versions
of updated programs/libraries, I add
lsof | grep -w DEL | grep portage
On Sat, 12 Aug 2017 07:51:46 -0400,
Rich Freeman wrote:
>
> On Sat, Aug 12, 2017 at 4:22 AM, Matthias Hanft wrote:
> > Dale wrote:
> >>
> >> I do it this way.
> >> pkill agetty
> >> Simple, quick and easy to remember. One could script it I guess???
> >
> > I'm pretty sure this would work, but is
I have a Thinkpad T410 where, after I installed Gentoo on it, everything "just
worked (TM)". The sound is via the bog-standard Intel chips on the mobo and
uses the hda_intel drivers. I didn't use the TP for a long time, just
periodically updating Gentoo, but when I eventually did try to use it t
On Saturday 12 Aug 2017 20:49:48 Robin Atwood wrote:
> I have a Thinkpad T410 where, after I installed Gentoo on it, everything
> "just worked (TM)". The sound is via the bog-standard Intel chips on the
> mobo and uses the hda_intel drivers. I didn't use the TP for a long time,
> just periodically
On Sat, Aug 12, 2017 at 4:49 PM, Robin Atwood wrote:
> I have a Thinkpad T410 where, after I installed Gentoo on it, everything
> "just worked (TM)". The sound is via the bog-standard Intel chips on the
> mobo and uses the hda_intel drivers. I didn't use the TP for a long time,
> just periodically
Dale wrote:
>
> Correct. I should have mentioned that in my post but assumed it would
> be known. Anytime agetty is killed, it just pops back up. I suspect it
> doesn't stay dead for even a second. Sort of like those zombie movies.
Looks good. I used "pkill agetty", and now it looks like
r
Nikos Chantziaras wrote:
>>
>> lsof | grep -w DEL | grep portage
>
> You should probably use app-admin/lib_users for this.
Thank you, I didn't know this. Looks good (and found mysql
in addition to my "lsof" command).
-Matt
On Saturday 12 August 2017, Mick wrote:
> On Saturday 12 Aug 2017 20:49:48 Robin Atwood wrote:
> Which device does alsamixer or pulseaudio show as being active? I found on
> some PCs that HDMI is now set as the default audio device and I had to
> change the configuration to make analogue sound dev
On Sat, 12 Aug 2017 16:30:34 +0300, Nikos Chantziaras wrote:
> > lsof | grep -w DEL | grep portage
>
> You should probably use app-admin/lib_users for this.
Or app-admin/needrestart, which also has an option to restart affected
services.
--
Neil Bothwick
Don't put all your hypes in one hom
On 2017-08-12 17:39, Alexander Kapshuk wrote:
> (5). Postinst message for alsa-utils:
> pkg_postinst() {
> if [[ -z ${REPLACING_VERSIONS} ]]; then
> elog
> elog "To take advantage of the init script, and automate the process of"
> elog "saving and restoring sound-card mixer levels you should"
> el
On Saturday 12 Aug 2017 09:05:10 Ian Zimmerman wrote:
> On 2017-08-12 17:39, Alexander Kapshuk wrote:
> > (5). Postinst message for alsa-utils:
> > pkg_postinst() {
> > if [[ -z ${REPLACING_VERSIONS} ]]; then
> > elog
> > elog "To take advantage of the init script, and automate the process of"
> >
On Sat, 12 Aug 2017 12:31:45 -0400,
Mick wrote:
>
> [1 ]
> On Saturday 12 Aug 2017 09:05:10 Ian Zimmerman wrote:
> > On 2017-08-12 17:39, Alexander Kapshuk wrote:
> > > (5). Postinst message for alsa-utils:
> > > pkg_postinst() {
> > > if [[ -z ${REPLACING_VERSIONS} ]]; then
> > > elog
> > > elog
On 2017-08-12 17:31, Mick wrote:
> > My ALSA is built as modules, including the core (I'm guessing that
> > means snd.ko, right?). I don't do anything particular to load them,
> > they're not listed in /etc/conf.d/modules. Yet the mixer save and
> > restore via alsasound works.
> >
> > Could it
On Thu, 10 Aug 2017 16:37:57 -0400,
Ian Zimmerman wrote:
>
> On 2017-08-09 08:31, Ian Zimmerman wrote:
>
> > So, bug #627244 is relevant after all.
> >
> > I don't have doc in make.conf, so it should just work for me [murmurs a
> > belief-neutral invocation/]
>
> And it did work with no problem
On 2017-08-12 13:21, John Covici wrote:
> How about checking the various volumes rather than muting maybe some
> of them are 0 or rather some negative number or something? Also, you
> might delete the asound.state and let the system start over. Last
> resort, there is an alsa users mailing list.
23 matches
Mail list logo
