11-24-2010
There seems to be some fundamental misunderstanding: the "console" is a directly attached terminal which is used for emergencies (like network connections being all down and the like).
As you use it in cases of emergency only and you can easily physically protect it (it is perhaps in the immediate vicinity of the system itself) you don't want to hinder roots access via this terminal. You would only unnecessarily complicate your work in cases of emergency.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
My ssytem is mounted on a rack and not connected with any console. When I rebooted it remotely, it didn't go thru the bootup process. when I connect my laptop to the system locally and found that it was waiting for user interaction. Do you know how to disable it, so that it will boot... (1 Reply)
Discussion started by: stancwong
1 Replies
2. AIX
Hi everyone,
I have no AIX experience at all. We have an IBM Server running AIX v.5.1. The server has a DDS-4 tape drive. I need to take complete system and user data backup.Should be able to restore the system and the user data in the event of system corruption or disaster. I was told that for... (5 Replies)
Discussion started by: Sezgin
5 Replies
3. Solaris
Hi Friends,
I would like to block the root user for doing ftp. As I am aware that I need to put the entry for root in /etc/ftpusers.....am I right...??? But I am not able to edit the file & even more command is not working.
#ls -l ftp*
total 14
-rw-r--r-- 1 root sys 1249 Jun... (3 Replies)
Discussion started by: jumadhiya
3 Replies
4. AIX
I use AIX 5.2 I want to allow a non-root user to do a system backup with 'mksysb' command.
I try to add 'ManageBackup' Role to that non-root user but it have an error "ksh: mksysb: 0403-006 Execute permission denied."
What should I do? (8 Replies)
Discussion started by: AIX122
8 Replies
5. AIX
Hi all,
I cannt use 'su' to login to root or any other users though everything seems ok. I read some articles that says if you do recursive chmod 777 on /usr it can create this problem.
I did the same. can anybody tell me how to repair it. Any ideas will be appreciated.
thnks (7 Replies)
Discussion started by: itesh.dash
7 Replies
6. Emergency UNIX and Linux Support
Hi All,
I'm stuck in a severe problem here , Someone have changed the root password
and he cannot remember it and there is no other user privileged user on the system , But I do have access to a non privileged user.
On the top of the system an application which requires a theoretical ... (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies
7. Solaris
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies
8. AIX
Hi,
on running system, a disk was added
hdiskx
then importvg -y oraclevg hdiskx
but hdiskx was actually a rootvg so since rootvg was already present in the existing system this happened
Imported hdisk2 which was rootvg as importvg -y oraclevg hdisk2 in server since rootvg already... (1 Reply)
Discussion started by: filosophizer
1 Replies
9. AIX
Hello,
I am testing sudo and I want to test it. Can anyone please let me know few commands (of course other than shutdown, reboot etc. as I can't reboot the box) on AIX that can be run by ROOT only.
Thanks
---------- Post updated at 07:43 PM ---------- Previous update was at 07:38 PM... (5 Replies)
Discussion started by: prvnrk
5 Replies
10. AIX
Hi,
what are the ideal/best/recommended ulimit settings for a root user in AIX?
I understand that it depends on our environment. But I would like to know...what are settings you guys use in your environment for best performance.
default:
fsize = 2097151
core = 2097151
... (8 Replies)
Discussion started by: System Admin 77
8 Replies
LEARN ABOUT LINUX
systemd.target
SYSTEMD.TARGET(5) systemd.target SYSTEMD.TARGET(5)
NAME
systemd.target - Target unit configuration
SYNOPSIS
target.target
DESCRIPTION
A unit configuration file whose name ends in ".target" encodes information about a target unit of systemd, which is used for grouping units
and as well-known synchronization points during start-up.
This unit type has no specific options. See systemd.unit(5) for the common options of all unit configuration files. The common
configuration items are configured in the generic [Unit] and [Install] sections. A separate [Target] section does not exist, since no
target-specific options may be configured.
Target units do not offer any additional functionality on top of the generic functionality provided by units. They exist merely to group
units via dependencies (useful as boot targets), and to establish standardized names for synchronization points used in dependencies
between units. Among other things, target units are a more flexible replacement for SysV runlevels in the classic SysV init system. (And
for compatibility reasons special target units such as runlevel3.target exist which are used by the SysV runlevel compatibility code in
systemd. See systemd.special(7) for details).
IMPLICIT DEPENDENCIES
There are no implicit dependencies for target units.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Target units will automatically complement all configured dependencies of type Wants= or Requires= with dependencies of type After=
unless DefaultDependencies=no is set in the specified units. Note that Wants= or Requires= must be defined in the target unit itself --
if you for example define Wants=some.target in some.service, the automatic ordering will not be added.
o Target units automatically gain Conflicts= dependency against shutdown.target.
EXAMPLE
Example 1. Simple standalone target
# emergency-net.target
[Unit]
Description=Emergency Mode with Networking
Requires=emergency.target systemd-networkd.service
After=emergency.target systemd-networkd.service
AllowIsolate=yes
When adding dependencies to other units, it's important to check if they set DefaultDependencies=. Service units, unless they set
DefaultDependencies=no, automatically get a dependency on sysinit.target. In this case, both emergency.target and systemd-networkd.service
have DefaultDependencies=no, so they are suitable for use in this target, and do not pull in sysinit.target.
You can now switch into this emergency mode by running systemctl isolate emergency-net.target or by passing the option
systemd.unit=emergency-net.target on the kernel command line.
Other units can have WantedBy=emergency-net.target in the [Install] section. After they are enabled using systemctl enable, they will be
started before emergency-net.target is started. It is also possible to add arbitrary units as dependencies of emergency.target without
modifying them by using systemctl add-wants.
SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.special(7), systemd.directives(7)
systemd 237 SYSTEMD.TARGET(5)