Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators User generated FAQ and Best Practices section Post 43772 by Neo on Friday 21st of November 2003 06:17:29 PM
Old 11-21-2003
We are certainly looking for someone to accept administrative responsibility and 'run with' developing the FAQ section.

kduffin, are you interested? If you, I will grant you privs' to take control and enhance the important area.

Neo
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Scripting Best Practices

Hi - I am new to this and was wondering if some of you can help me out. I am just starting to write scripts and need some guidelines on creating scripts. I'm calling them "Best Practices"...what should I do and not do when creating scripts. All I know so far is that I should avoid putting... (5 Replies)
Discussion started by: toddjameslane
5 Replies

2. UNIX for Advanced & Expert Users

Q on <user> of syslog message generated by logger command

Generally(at least on AIX5.3, Solaris9, OS X)'logger' command would create syslog messages which carry <login name> . On Solaris9, I have experienced two circumstances in which 'logname' command fails. In this circumstance I saw the 'logger' command generated syslog messages which carry... (0 Replies)
Discussion started by: masaki
0 Replies

3. Shell Programming and Scripting

Disconnecting the User Section through Shell Script

Dear All, I am new to this forum and also I am new to Unix. Our database is running under unix. I want to write a shell script in unix to kill the user section after given idle time. This script should be applicable to specific users / should not be applicable to specific users, Could... (0 Replies)
Discussion started by: pyb_rkumar
0 Replies

4. Shell Programming and Scripting

Unix Shell scripting -How to skip User Standard input section from another script

All, problem Description: For example: I have two shell scripts(executables). let name it as script1 and script2.I'm trying to execute script1 from script2. while executing script2, script1 is asking for manual input(input from keyboard). Now i need to know how I can skip this user input... (3 Replies)
Discussion started by: techie99
3 Replies

5. Shell Programming and Scripting

Extract section of file based on word in section

I have a list of Servers in no particular order as follows: virtualMachines="IIBSBS IIBVICDMS01 IIBVICMA01"And I am generating some output from a pre-existing script that gives me the following (this is a sample output selection). 9/17/2010 8:00:05 PM: Normal backup using VDRBACKUPS... (2 Replies)
Discussion started by: jelloir
2 Replies

6. Shell Programming and Scripting

Prepend first line of section to each line until the next section header

I have searched in a variety of ways in a variety of places but have come up empty. I would like to prepend a portion of a section header to each following line until the next section header. I have been using sed for most things up until now but I'd go for a solution in just about anything--... (7 Replies)
Discussion started by: pagrus
7 Replies

7. Shell Programming and Scripting

Files generated by a particular user

Hi I have the following files generated by different users on a directory -rw-rw-r-- 1 NAME1 database03 809 Nov 17 10:41 PCAS_CARD_TRANS_OFF.1111171041.lg -rw-rw-r-- 1 richard ccsdba 10968411 Nov 17 10:43 load_123_RX0_0.1111171016.lg -rw-rw-r-- 1 DEV db03 10713 Nov 17... (5 Replies)
Discussion started by: bobby1015
5 Replies

8. Solaris

Best practices

Dear all, Kinda lame question but i'd like to hear your experiences and advice. Question in short ----------------- What permission should a mount point "ideally" have - i think it's root. Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies

9. AIX

Best practices for sugroups for root ? backdoor user access ?

greetings, just ran across a fun situation we had overlooked. We have a backdoor user, no special privileges, which we put on every server so that anyone in the shop can get in (passwd in vault) if they need to, even if they don't have a local account on that server. The point of course is to... (3 Replies)
Discussion started by: maraixadm
3 Replies
Perspective(3I) 					    InterViews Reference Manual 					   Perspective(3I)

NAME
Perspective - visible portion of an interactor SYNOPSIS
#include <InterViews/perspective.h> DESCRIPTION
A perspective object describes which part of an interactor's total display area is visible in the interactor's canvas. The main use of perspectives is for scrolling, panning, and zooming interactors. The member variables (x0, y0) define the origin of the interactor's dis- play area; width and height define the total height of the area. The member variables (curx, cury) define the lower-left corner of the interactor's canvas relative to the total area; curwidth and curheight define how much of the total area is displayed in the canvas. The member variables sx, sy, lx, and ly specify small and large increments in each dimension. These increments are used by a scroller to implement line and page scrolling. PUBLIC OPERATIONS
Perspective() Define a new perspective with all member variables initialized to zero. void Attach(Interactor*) Add to the list of interactors that are interested in updates to the perspective. These interactors reflect the perspective visual- ly; examples include scrollers and sliders. void Detach(Interactor*) Remove an interactor from the list of those interested in updates. This operation should be called from the interactor's destruc- tor. void Init(Coord x0, Coord y0, Coord width, Coord height) Initialize the perspective display area. void Update() Notify all the interactors interested in the perspective that it has changed. The perspective's interactor should call Update after modifying its perspective. SEE ALSO
Adjuster(3I), Interactor(3I), Panner(3I), Scroller(3I) InterViews 15 June 1987 Perspective(3I)
All times are GMT -4. The time now is 04:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy