Re: firefox-37, where to put
Hi.
On Sat, 4 Apr 2015 12:43:14 -0500
David Wright <deblis@lionunicorn.co.uk> wrote:
> Quoting Reco (recoverym4n@gmail.com):
> > On Sat, 4 Apr 2015 09:04:53 +0200
> > Petter Adsen <petter@synth.no> wrote:
> > > On Fri, 03 Apr 2015 12:30:45 -0400
> > > The Wanderer <wanderer@fastmail.fm> wrote:
> > > > Not necessarily as easy as you might think. You'd need to be careful
> > > > to make sure that nothing got autostarted (or left running on logout)
> > > > which would try to access files under /home/*/ - and though I don't
> > > > know of anything offhand which would necessarily do that, I wouldn't
> > > > want to assume that nothing would.
> > >
> > > If you are running Jessie, you can use "loginctl terminate-user USER",
> > > and if there is anything left, "loginctl kill-user USER". For Wheezy I
> > > don't know, though.
> >
> > pgrep -lU $USER
> >
> > pkill -TERM -U $USER
> >
> > pgrep -lU $USER
> >
> > pkill -KILL -U $USER
> >
> > Be universal. Don't depend on systemd for such easy task.
>
> But that still doesn't address The Wanderer's point. For example, on
> one of my machines, a cron job pops up every minute, day and night, to
> see whether to record music off the radio.
There's nothing in that cannot be fixed with stopping cron, isn't it?
But for the sake of completeness I'd like to add that fiddling with
logind does not prevent cron jobs from starting either.
> It just seems sensible to me to use "single" for what it's for, rather
> than try to fly-swat a number of corner cases (to mix metaphors).
> (Particularly if others, like gene, might archive this method.)
Single-user is a bulletproof way to be sure, but it requires a console
access (which is not always available or is convenient).
Killing all user processes *and* renaming /home is much simpler and
almost correct way to accomplish the needed task.
Reco
Reply to: