[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: firefox-37, where to put

On Saturday 04 April 2015 13:43:14 David Wright 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.
> 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.)
> Cheers,
> David.

This business of using cron to drive much of my stuff amply illustrates 
this "problem".  But there are several other things that cron runs on my 
behalf, most of which have been running so long that the only time I 
notice them is when I realise, finally, that they have stopped.  The 
above stuff would not prevent an attempt to execute some of them unless 
cron itself has been killed.

Since this could be a valid concern, is that easily done?  Possibly by, 
if systemd isn't running the show, making sure cron is not running in 
the "single" runlevel mode?  Or is that already done. Time for a 
chkconfig session I think.

Which "runlevel" is "single"?

I get this from chkconfig --list
cron                      0:off  1:off  2:on   3:on   4:on   5:on   6:off

And I also see this, which is why I had to hand start networking on the 
last reboot after expunging Network-Manager.
networking                0:off  1:off  2:off  3:off  4:off  5:off  6:off  S:on 

So it looks as if I need to consult the manpage to see how to enable that.

Thanks David, for bring up the subject.

Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Reply to: