Hello:
I have a customer who is requesting the following security features on a Solaris 8 system:
1. Password history for the three previous passwords.
2. User account lockout after 3 failed login attempts.
Can anyone help provide me with a solution or direction for the above? (1 Reply)
Sorry for the duplicate thread this one is similar to the one in
https://www.unix.com/shell-programming-scripting/88132-awk-sed-script-read-values-parameter-files.html#post302255121
Since there were no responses on the parent thread since it got resolved partially i thought to open the new... (4 Replies)
Okay, title is kind of confusion, but basically, I have a lot of scripts on a server that I need to replace a ps command, however, the new ps command I'm trying to replace the current one with pipes to sed at one point. So now I am attempting to create another script that replaces that line.
... (1 Reply)
I know this script is crummy, but I was just messing around.. how do I get sed's insert command to allow variable expansion to show the filename?
#!/bin/bash
filename=`echo $0`
/usr/bin/sed '/#include/ {
i\
the filename is `$filename`
}' $1
exit 0 (8 Replies)
I need to be able to take the results from ls -l command and modify the output as follows:
I will run
ls -l *.mak
My results will be
aa.mak
bb.mak
cc.mak
I then need to take those results and create a file that has the following info:
dsjj/ubin/aa
dsjj/ubin/bb
dsjj/ubin/cc
... (3 Replies)
Hi all,
I have script to monitor and sum up the total memory use up for each individual process.
proc=$1
svmon -P -O summary=basic,unit=MB|awk 'NR>4'|grep -w "${proc}" |awk '{sum+=$3} END {printf "\t" sum """\n";}'
But I would like the script to be able to display as following
... (3 Replies)
Hi,
I am running a script sample.sh in bash environment .In the script i am using sed and awk commands which when executed individually from terminal they are getting executed normally but when i give these sed and awk commands in the script it is giving the below errors :-
./sample.sh: line... (12 Replies)
Hi All,
I'm relatively new to Unix scripting and am trying to get my head around piping.
I'm trying to take a header record from one file and prepend it to another file. I've done this by creating several temp files but i'm wondering if there is a cleaner way to do this.
I'm thinking... (10 Replies)
Hello i am having an issue with bash script and this is the code
now=$(cat hosts1.txt | awk '{print $2;}')
while read n ;do
ssh root@$now 'useradd test1; echo -e "test1\ntest1" | passwd test1 && echo "test1 ALL=(ALL:ALL) ALL" >> /etc/sudoers'
When i execute only part with cat, it... (8 Replies)
Discussion started by: tomislav91
8 Replies
LEARN ABOUT XFREE86
pswrap
PSWRAP(1) General Commands Manual PSWRAP(1)NAME
pswrap - creates C procedures from segments of PostScript language code
SYNOPSIS
pswrap [ -apr ] [ -o outputCfile ] [ -h outputHfile ] [ -s maxstring ] inputfile
DESCRIPTION
pswrap reads input from inputfile and creates C-callable procedures, known as wraps, that send PostScript language code to the PostScript
interpreter. inputfile contains segments of PostScript language code wrapped with a C-like procedure syntax.
Wraps are the most efficient way for an application to communicate with the PostScript interpreter. For complete documentation of pswrap
and the language it accepts, see "pswrap Reference Manual" in Programming the Display PostScript System with X.
OPTIONS
inputfile
A file that contains one or more wrap definitions. pswrap transforms the definitions in inputfile into C procedures. If no input
file is specified, the standard input (which can be redirected from a file or pipe) is used. The input file can include text other
than wrap definitions. pswrap converts wrap definitions to C procedures and passes the other text through unchanged. Therefore, it
is possible to intersperse C-language source code with wrap definitions in the input file.
Note: Although C code is allowed in a pswrap input file, it is not allowed within a wrap body. In particular, no CPP macros (for
example, #define) are allowed inside a wrap.
-a Generates ANSI C procedure prototypes for procedure definitions in outputCfile and, optionally, outputHfile. The -a option allows
compilers that recognize the ANSI C standard to do more complete type checking of parameters. The -a option also causes pswrap to
generate const declarations.
Note: ANSI C procedure prototype syntax is not recognized by most non-ANSI C compilers, including many compilers based on the Porta-
ble C Compiler. Use the -a option only in conjunction with a compiler that conforms to the ANSI C Standard.
-f specialHFile
Adds a #include to the generated source file for a special header file.
-h outputHFile
Generates a header file that contains extern declarations for non-static wraps. This file can be used in #include statements in mod-
ules that use wraps. If the -a option is specified, the declarations in the header file are ANSI C procedure prototypes. If the -h
option is omitted, a header file is not produced.
-o outputCFile
Specifies the file to which the generated wraps and passed-through text are written. If omitted, the standard output is used. If the
-a option is also specified, the procedure definitions generated by pswrap are in ANSI C procedure prototype syntax.
-p Specifies that strings passed by wraps are padded so that each data object begins on a long-word (4-byte) boundary. This option
allows wraps to run on architectures that restrict data alignment to 4-byte boundaries and improves performance on some other archi-
tectures.
-r Generates reentrant code for wraps shared by more than one process (as in shared libraries). Reentrant code can be called recur-
sively or by more than one thread. The -r option causes pswrap to generate extra code, so use it only when necessary.
-s maxstring
Sets the maximum allowable length of a PostScript string object or hexadecimal string object in the wrap body input. A syntax error
is reported if a string is not terminated with ) or > within maxstring characters. maxstring cannot be set lower than 80; the
default is 200.
SEE ALSO
Programming the Display PostScript System with X (Addison-Wesley Publishing Company, Inc., 1993).
AUTHOR
Adobe Systems Incorporated
NOTES
PostScript and Display PostScript are trademarks of Adobe Systems Incorporated which may be registered in certain jurisdictions.
Copyright (c) 1988-1994 Adobe Systems Incorporated. All rights reserved.
Adobe Systems 4 Apr 1994 PSWRAP(1)