09-12-2008
Yes, root can do pretty much anything.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Another newbie here and here is my dilemma. I created an account for me on Solaris 8 and I added myself to the root group. But when I login using that account I am unable to do superuser tasks.. (add users, admintool, etc). What am I missing? Thanks in advance..
Andre (5 Replies)
Discussion started by: jacobsa
5 Replies
2. Linux
What is the file you have to edit to allow or deny someone to be able to su - to root? (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
3. HP-UX
Hi all,
I cannot change root owned files/directories even though I am logged in as
root.
>drwxr-xr-x 11 root root 4096 Oct 25 14:00 prodbkp
>root / # chown oracle prodbkp
prodbkp: Not owner
>id
uid=0(root) gid=3(sys) groups=0(root)
please assist.
thanks (0 Replies)
Discussion started by: macgre_r
0 Replies
4. Solaris
Hi,
How can I start CDE for non root user created.For root CDE is working fine but for non root user CDE exits back to login screen after trying for some time.Also I cant see .dt and .dtprofile files in the users home directory.How can I create them.Kindly help.
Thanks & Regards,
Kiran. (1 Reply)
Discussion started by: kiranherekar
1 Replies
5. Solaris
Please let me know how to setup a non-root user to be able to access a privileged port (<1024) on Solaris 8. I am currently running tomcat as "tomcat" user and I get the following error during to start up:
SEVERE: Error initializing endpoint
java.net.BindException: Permission denied<null>:443 (5 Replies)
Discussion started by: pingmeback
5 Replies
6. Solaris
I am not able to get ftp working for Solaris 10 for root user. I am getting login failed error.
331 Password required for root.
Password:
530 Login incorrect.
Login failed.
Tried following things already.
1. SFTP works ok, still would like to know why FTP is not working (curious).
2.... (5 Replies)
Discussion started by: webkid
5 Replies
7. UNIX for Dummies Questions & Answers
I've been through many threads before i decide to create a separate thread.
I can't really find the solution to my (simple) problem.
Here's what I'm trying to achieve:
As "canar" user I want to run a command, let's say "/opt/ocaml/bin/ocaml" as "duck" user.
The only to achieve this is to... (1 Reply)
Discussion started by: canar
1 Replies
8. SuSE
Hi
New to Suse - mainly used Solaris.
In solaris dmesg will also show you contents of messages log file but in Suse Liux it doesnt appear to.
I dont have root access to this Suse server, and wondering is there any other tool / utility that allows me to see the messages file contents like on... (1 Reply)
Discussion started by: frustrated1
1 Replies
9. Solaris
Welcome to all.
Have an issue and looking for help so hope someone is able to give me some clues.
I prepared some shell scripts with coloured output to help other guys to have more automated task. Not sure if I did this but now whenever I use 'ls' command for root user every output in... (29 Replies)
Discussion started by: TiedCone
29 Replies
10. Solaris
Hello,
I got into a wired state on one of solaris 10 server. When I noticed that server is having some issue, I found that there were dumpadm.conf entries in /etc/shadow and real entries were wiped of. Probably somebody fat fingers.
I was able to boot into failsafe, break SVM mirror, copied... (25 Replies)
Discussion started by: solaris_1977
25 Replies
fvwm-root(1) Fvwm Modules fvwm-root(1)
NAME
fvwm-root - Sets the root window of the current X display to image
SYNOPSIS
fvwm-root [--retain-pixmap|-r] [--no-retain-pixmap] [--dummy|-d] [--no-dummy] [--dither] [--no-dither] [--color-limit [ncolors] ] [--no-
color-limit] [--help|-h|-?] [--version|-V] image_file
DESCRIPTION
fvwm-root reads the image file specified in the command line and displays it in the root window. The supported image formats are XBM, XPM,
PNG and SVG if appropriated libraries are compiled in.
SVG rendering options (as described in the ICONS AND IMAGES section of the main fvwm documentation) can be utilized.
OPTIONS
These command line options are recognized by fvwm-root:
--retain-pixmap | -r
Causes fvwm-root to retain and publish the Pixmap with which the background has been set (the ESETROOT_PMAP_ID and _XROOTPMAP_ID
properties are used). This is useful for applications which want to use the root Pixmap on the background to simulate transparency
(for example, Eterm and Aterm use this method). This option should also be used for the RootTransparent colorset option, refer to
the COLORSETS section of fvwm(1). If this option is not used, fvwm-root sets the _XSETROOT_ID property to None, and some programs,
like fvwm modules, may use this to update their background if the background is transparent (Transparent colorset).
Note, a well behaved program, like fvwm, should listen to both _XSETROOT_ID and _XROOTPMAP_ID property changes and update itself
correspondingly. However some programs listen only to one of them, so you should either use this option or not depending on what
part is implemented by these programs. You should also use this option to get fast root-transparent menus in fvwm.
--no-retain-pixmap
This is a default. May be useful to explicitely force the default even if "--retain-pixmap" is specified earlier.
--dummy | -d
Causes fvwm-root NOT to set the background, but to only free a memory associated with the ESETROOT_PMAP_ID property (if any). In
any case the _XSETROOT_ID property is set to None.
--no-dummy
This is a default. May be useful to explicitely force the default even if "--dummy" is specified earlier.
--dither
Causes fvwm-root to dither images for "smoother" rendition on displays with color depth of 16 or lower. This the defaut with color
depth less or equal to 8.
--no-dither
Causes fvwm-root NOT to dither images. This is the default with color depth greater than 8.
--color-limit ncolors
Causes fvwm-root to limit its color use to ncolors (if specified). This option is taken in account only with color depth less or
equal to 8 (and a TrueColor or GrayScale visual). The default is to use the same color limit as fvwm. So in normal situation this
option is not useful. However, if fvwm use a private colors map, as fvwm-root always use the default colors map you should use this
option for limiting colors correctly. If ncolors is not specified a default is used.
--no-color-limit
Causes fvwm-root NOT to limit its color use.
--help Shows a short usage.
--version
Shows a version number.
COMPATIBILITY
In the past this utility was called xpmroot. This name is still supported as a symlink.
BUGS
Repeated use of fvwm-root with different xpm pixmaps will use up slots in your color table pretty darn fast.
AUTHOR
Rob Nation
Rewritten and enhanced by fvwm-workers.
3rd Berkeley Distribution 7 May 208 (2.5.26) fvwm-root(1)