10-05-2006
$ /opt/omni/bin/xomni -cde
Uses CDE color scheme instead of default...
worth a try.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
People,
Can any one tell me the meaning of the "-main" option in the Omniback cell_info file. (We have Data Protector 5.5)
?? (4 Replies)
Discussion started by: Andrek
4 Replies
2. Solaris
Hello.
I had installed solaris 10 in morning , and all was running fine... I just logged out and logged in with another user ID oracle - It got stuck and then I pressed the button for restart.
Now I see only word GRUB written in top line rest everything is black.
What to do? (2 Replies)
Discussion started by: panchpan
2 Replies
3. HP-UX
playing around with a command-line restore from omniback...anyone ever play with omnir?
I have the following test backup:
$ omnidb -session 2008/02/01-6
Object Name Object Type Object Status... (1 Reply)
Discussion started by: mr_manny
1 Replies
4. Solaris
Hello
I'm new in sun and i have a liitle problem.
I buy sun enterprise 420r and connect keyboard and monitor crt (non Sun).
But when i start server i have blank screen on crt. I'm new in sun servers and i dont know why its doin this. (11 Replies)
Discussion started by: elmik
11 Replies
5. Linux
Hi guys.
Opening port 5555 for Data Protector on Linux box but can't telnet to it.
Modified /etc/services to have:
omni 5555/tcp # DATA-PROTECTOR
But when I telnet into it:
telnet <ip address> 5555
Doesn't connect
Need help figuring out what I need to do to open this port.
... (0 Replies)
Discussion started by: jamie_collins
0 Replies
6. Red Hat
Dear All,
I have my HP Data Protector installed on the backup server.
I want to connect this backup server with the client server through
telnet port 5555 like below
telnet < ipaddress of client> 5555
But when I try like this , it says ...Connection refused ...unable to connect to... (0 Replies)
Discussion started by: jegaraman
0 Replies
7. Solaris
I have a SunFire V490
Recently when the server is rebooted the screen goes blank from when the CDE is shutdown to when it is started up again.
Has anyone got any ideas what might be causing this?
I've had a quick look in messages but can't find anything in there. I've had a look at... (2 Replies)
Discussion started by: sonic72
2 Replies
8. AIX
hello,
i am trying to test connection to a 5.3 box. from an xp machine, telnet connects but shows only a blank screen. cursor moves as i type, but no response back.
have used telnet, putty and accuterm - all same result
verified that telnet services are active in xp
xp windoze firewall is... (10 Replies)
Discussion started by: allenhibbert
10 Replies
9. Ubuntu
Hello,
I got blank screen when reboot after I tried to upgrade Ubuntu (64 bit server version) from 11.10 to 12.04 at update manager.
The normal login GUI is missing, but mouse cursor is fine. Then I switched to terminal (tty1 ~ tty6), which looked fine and showed it is Ubuntu 12.04 ! (Forgot how... (4 Replies)
Discussion started by: yifangt
4 Replies
10. Linux
Hi All,
Am working in a major IT company, due to security issues, being a fresher am not allowed to install or asking for a specific business reason to install it in my system.
The thing is i want to learn Linux, due to the same security issues we need Admin pass to install certain... (6 Replies)
Discussion started by: mr_ganapathy
6 Replies
LEARN ABOUT HPUX
dtwsmgetworkspaceinfo
DtWsmGetWorkspaceInfo(library call) DtWsmGetWorkspaceInfo(library call)
NAME
DtWsmGetWorkspaceInfo -- get detailed workspace information
SYNOPSIS
#include <Dt/Wsm.h>
int DtWsmGetWorkspaceInfo(
Display *display,
Window root,
Atom aWorkspace,
DtWsmWorkspaceInfo **ppWsInfo);
DESCRIPTION
The DtWsmGetWorkspaceInfo function works with the CDE workspace manager, dtwm(1), and returns detailed information on a specific workspace.
The display argument is the X display.
The root argument is the root window of the screen of interest.
The aWorkspace argument is the workspace name (converted to an X atom).
The *ppWsInfo argument is the address of a variable to receive the returned pointer to the workspace information data.
The DtWsmWorkspaceInfo structure contains at least the following members:
Atom workspace The workspace name (con-
verted to an X atom).
unsigned long bg The pixel ID used for the
background color of the
backdrop.
unsigned long fg The pixel ID used for the
foreground color of the
backdrop.
Atom backdropName The backdrop file name
(converted to an X atom).
The file must be in either
X Bitmap file format (with
extension .bm) or X Pixmap
file format (with extension
.pm). The workspace man-
agement services look for
the file along the same
path used for searching
icons. The directory
/usr/dt/backdrops is the
default directory if the
file cannot be found along
the icon search path.
int colorSetId The colorset number used
for this workspace, which
affects the backdrop color
and the button color for
this workspace on the front
panel.
char *pchTitle The title displayed in the
button for this workspace
on the front panel. This
string is interpreted in
the locale in which the CDE
workspace manager, dtwm(1),
is running. The title is
different from the
workspace name. The
workspace name, when con-
verted from an X atom, is
used as the identifier for
a workspace in the
workspace manager function
calls. The CDE workspace
manager, dtwm(1). also uses
the workspace name as a
resource name; thus, the
characters used in a
workspace name are
restricted to the charac-
ters in the X Portable
Character Set. The
workspace name for a
workspace created from the
front panel is generated
automatically by the CDE
workspace manager, dtwm(1).
Window *backdropWindows A pointer to an array of
windows that make up the
backdrop.
int numBackdropWindows The number of elements in
the backdropWindows array.
RETURN VALUE
Upon successful completion, the DtWsmGetWorkspaceInfo function returns Success and the workspace manager returns in *ppWsInfo a pointer to
a DtWsmInfo structure that contains information about the workspace aWorkspace; otherwise, it returns a value not equal to Success.
APPLICATION USAGE
If the DtWsmGetWorkspaceInfo function is not successful, failure may be due to a memory allocation error or failure to find the correct
workspace information (that is, the CDE workspace manager, dtwm(1), is not running). The application must use the DtWsmFreeWorkspaceInfo(3)
function to free the data returned in *ppWsInfo. The *backdropWindows pointer may be useful for applications that are interested in some
events on the root window. Since the backdrop covers the root window, the backdrop catches the button events before they reach the root.
SEE ALSO
Dt/Wsm.h - DtWsm(5), dtwm(1), DtWsmGetWorkspaceList(3), DtWsmFreeWorkspaceInfo(3).
DtWsmGetWorkspaceInfo(library call)