Hi. On Sat, 4 Apr 2015 14:14:21 -0400 Gene Heskett <ghesk...@wdtv.com> 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. Unless you install badly-written third-party software - there should be small amount of processes running in single-user. From the top of my head - init, root's bash, iscsi daemon, nfs-client and dhcp-client. Nothing that writes in /home or /opt, that's for sure. > Which "runlevel" is "single"? The one that is marked with '1'. > I get this from chkconfig --list > cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off And as expected, cron should not run in single-user. > > 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 update-rc.d networking enable Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150404213302.d096168b3fa7577dfddef...@gmail.com
