Re: Command help?

Bradley wrote:
Aldo Foot wrote:
On Wed, Sep 24, 2008 at 12:58 PM, Bradley <pursley001@xxxxxxxxxxx> wrote:

Okay,

I am starting to do some more advanced automated maintenance on my
system but can't find a nifty way to do something and was wondering if
anyone out there can help me with this. I am configuring my system to
do an automated backup of all my data (2 to 4 hours per week) but need
it to do certain things to protect the process.

For an unattended process, I need to know how to:

1. Force all users currently logged on to be logged off (preferably
with at least a 5 minute notice).
2. Prevent anyone from logging on.
3. Prevent the system from being shut down or rebooted.
4. Shut down the X server (speeds up processing time considerably).
5. After finished to restart X server and allow shutdown and logins.

If anyone knows any commands to do at least some of these, I would
appreciate knowing how. The part about shutting down the X server is
optional but would be nice but not allowing anyone to be logged in and
preventing system shut down is necessary.

Bradley

My 0.02 cents.

start by doing man on login, nologin, shutdown, killall etc...

/etc/nologin -- prevents user logins

shutdown -k Don't really shutdown; only send the warning messages
to everybody.

killall -u, --user
Kill only processes the specified user owns.
Command names are
optional.

~af
Thanks for the input but, unfortunately, this doesn't give the results
that I need.

I gave up and configured one of the run levels for doing the needed
tasks and have the system reboot into that run level where it does what
I need it to and then reboots the system back to the normal run level.
Not a pretty arrangement but it seems to work. While in the special run
level, it does not activate any unnecessary services (network, servers,
Xserver, etc.) and does not allow any user logins. This turned out to
be simpler and cleaner to set up than what I had previously considered.

Bradley

Instead of rebooting, you could use telinit to change the run level.
It will stop/start services as necessary to match the configuration
for that run level.

Mikkel
--

Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

Attachment: signature.asc
Description: OpenPGP digital signature

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Relevant Pages

  • Re: Command help?
    ... I am starting to do some more advanced automated maintenance on my ... After finished to restart X server and allow shutdown and logins. ...
    (Fedora)
  • Re: tsshutdn causes TS to hang
    ... We don't have the problem anymore bacause I couldn't find a working ... The way we solved it is to schedule the shutdown on the Terminal Server ... reboot gives the problems. ...
    (microsoft.public.windows.terminal_services)
  • Re: Command help?
    ... I am starting to do some more advanced automated maintenance on my ... After finished to restart X server and allow shutdown and logins. ... hard reboot, but you can't stop ...
    (Fedora)
  • Re: SBS server blue blank screen - but running.... need to reboot
    ... A hard shutdown - holding power button in for 10 secs did the trick. ... option to reboot, ... resatrt the server prior with server management over RWW. ...
    (microsoft.public.windows.server.sbs)
  • Re: rebooting in a RDP session server never reboots then is unavailabl
    ... There are a couple of problems with shutdown / reboot, ... Shutdown.exe command is invoked ... Server 2003-based terminal server ...
    (microsoft.public.windows.terminal_services)
Loading