Sponsored Content
Operating Systems Solaris Persistent Security Banner on Gnome Desktop Post 302566679 by ArizonaTraveler on Thursday 20th of October 2011 09:01:50 PM
Old 10-20-2011
Persistent Security Banner on Gnome Desktop

I'm looking for options for displaying a persistent, security banner on a Solaris 10 workstation running JDS that would display at the top of each workspace for all users, have the option to change the color and the capability to add text to the banner.

The company I work for has used JEDI for Windows before, but not the Solaris version. Are there any alternatives to JEDI for Solaris 10 and JDS?

Thanks.
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Gnome desktop crash log

Hi All, When ever gnome desktop crashes, is it write errors to any log files? if yes please let me know log file name and path for the same. Thanks in advance for your inputs. Regards Bachegowda (0 Replies)
Discussion started by: bache_gowda
0 Replies

2. UNIX for Dummies Questions & Answers

Umask, in Desktop(gnome)

I want user, have umask 007, i just add in .bashrc and working, but our user using GDM for login, so I just add umask in /etc/profile. Is ther other way to put umask than in /etc/profile if using GDM? How to make .bash_profile with our define(default with my setting). Thank you. (1 Reply)
Discussion started by: blesets
1 Replies

3. SuSE

SLED 10.2 Default gnome desktop generation

Hi! Does anyone know where to alter the default gnome setup that SLED 10.2 does? I work for a big company and we have a huge issue with SLED adding the "main-menu" gnome panel applet thingie.... /opt/gnome/lib/gnome-main-menu/main-menu Is there any way to exchange this process for ex the... (0 Replies)
Discussion started by: Esaia
0 Replies

4. Shell Programming and Scripting

Backup & restore Gnome Desktop and all settings in Gnome

Hi I'm looking for scripts to backup & restore Gnome Desktop and all settings in Gnome. (0 Replies)
Discussion started by: ccc
0 Replies

5. UNIX Desktop Questions & Answers

GNOME Desktop - Setting missing from dconf-editor?

Hello All, Last night I installed OpenSuSE 12.1 (i586) on a HP Mini 110 laptop. And I selected GNOME as my Desktop during install... So I was trying to customize some things about the desktop, for example adding the Maximize/Minimize/Close options to the titlebar of a window. I did this... (2 Replies)
Discussion started by: mrm5102
2 Replies

6. Red Hat

Unable to get a Xterm or X app to appear under a Linux Gnome Desktop

I want to have a xterm or xapplication from a Solaris client to appear on my RHEL Server running GNOME desktop. It may sound easy at first but, I have done the basics and I be stuck. Have Tried: Linux - logged in as root, open a Terminal and did a echo $DISPLAY and it reports back :0.0 I... (7 Replies)
Discussion started by: mrmurdock
7 Replies
deallocate(1)                                                                                                                        deallocate(1)

NAME
deallocate - device deallocation SYNOPSIS
deallocate [-s] device deallocate [-s] [-F] device deallocate [-s] -I The deallocate utility deallocates a device allocated to the evoking user. device can be a device defined in device_allocate(4) or one of the device special files associated with the device. It resets the ownership and the permission on all device special files associated with device, disabling the user's access to that device. This option can be used by an authorized user to remove access to the device by another user. The required authorization is solaris.device.allocate. When deallocation or forced deallocation is performed, the appropriate device cleaning program is executed, based on the contents of device_allocate(4). These cleaning programs are normally stored in /etc/security/lib. The following options are supported: device Deallocate the device associated with the device special file specified by device. -s Silent. Suppresses any diagnostic output. -F device Forces deallocation of the device associated with the file specified by device. Only a user with the solaris.device.revoke authorization is permitted to use this option. -I Forces deallocation of all allocatable devices. Only a user with the solaris.device.revoke authorization is permitted to use this option. This option should only be used at system initialization. The following exit values are returned: non--zero An error occurred. /etc/security/device_allocate /etc/security/device_maps /etc/security/dev/* /etc/security/lib/* See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ allocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5) The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. /etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment. 28 Mar 2005 deallocate(1)
All times are GMT -4. The time now is 10:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy