01-23-2011
Maybe this would also work for you:
Quote:
egrep -o '[^|]+' infile > outfile
(or use grep -Eo ... instead of egrep)
The grep basically says just print the matched pattern, which is anything but a pipe symbol ("[^|]", repeated more than one time, "+".
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am having this problem......when I run this script:
print -n "Enter file name to be deleted: "
read answer
if
then
rm $name
else
echo "No such file with the name: $name exists"
fi
I was trying to test my script for errors, and basically when the user had files with the rights: 400,... (1 Reply)
Discussion started by: Makaveli.2003
1 Replies
2. IP Networking
Hi
My computer of late started misbehaving. Whenever I switch it on
It say Override and then it takes long to boot. Surprising is that it opens excel automatic. What could be that? (1 Reply)
Discussion started by: Mulo
1 Replies
3. UNIX for Advanced & Expert Users
On Sun Solaris 8 I would like a user to post via FTP a file with a put command with higher permission than the standard 644. For instance 664.
I don't know how to perform it.
Thank you in advance. (4 Replies)
Discussion started by: cagnod
4 Replies
4. AIX
When the aix date function is called by a routine, is the date function 'aware' of the name of the routine that is calling it, such that if we had the source code of the date function, we could modify it so that it provides a date to the caller depending upon the identity of the calling routine.... (1 Reply)
Discussion started by: gerry shacter
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I've searched and read, and searched and read some more; but I'm still not connecting the dots or understanding what I need to change.
I have a script that creates a file. If I run it as root, the file gets created with 644 permissions like I want. That seems to make sense (at least I... (2 Replies)
Discussion started by: 65bit
2 Replies
6. Shell Programming and Scripting
I send an attachment 123.pdf using the below script:-
<< script content >>
#!/usr/bin/ksh
/usr/lib/sendmail -C sendmail.cf abc@gmail.com << END
Subject: HELLO
`uuencode 123.pdf 123.pdf`
END
However, the message I got in gmail look like:-
begin 644 123.pdf
... garbage ...
... many... (4 Replies)
Discussion started by: pok.fung
4 Replies
7. Shell Programming and Scripting
Hi,
When I login to my HP-UX and fire the "set" command I see that the weblogic 9.2 classpath is already set.
However, I wish to override the classpath to weblogic version 10.3
I have a script call setWLSEnv.sh that has the desired classpath.
Thus, in my unix script i write
.... (6 Replies)
Discussion started by: mohtashims
6 Replies
8. Shell Programming and Scripting
Hi All,
I'm using Ksh 88 version.
I'm trying to remove the files using the below script .The code is working fine but i'm getting override protection 644 (yes/no)?
message for every file .. Pelase suggest
#!/usr/bin/ksh
set -x
File_Path="/etc/home/logs"
Dest_Path="/etc/home/temp"... (1 Reply)
Discussion started by: smile689
1 Replies
9. AIX
Hi,
We are using AIX machines. How to create all files generated in a directory with 644 permissions automatically.
Regards,
Suresh (11 Replies)
Discussion started by: suresh3566
11 Replies
LEARN ABOUT LINUX
pkey_free
PKEY_ALLOC(2) Linux Programmer's Manual PKEY_ALLOC(2)
NAME
pkey_alloc, pkey_free - allocate or free a protection key
SYNOPSIS
#include <sys/mman.h>
int pkey_alloc(unsigned int flags, unsigned int access_rights);
int pkey_free(int pkey);
DESCRIPTION
pkey_alloc() allocates a protection key (pkey) and allows it to be passed to pkey_mprotect(2).
The pkey_alloc() flags is reserved for future use and currently must always be specified as 0.
The pkey_alloc() access_rights argument may contain zero or more disable operations:
PKEY_DISABLE_ACCESS
Disable all data access to memory covered by the returned protection key.
PKEY_DISABLE_WRITE
Disable write access to memory covered by the returned protection key.
pkey_free() frees a protection key and makes it available for later allocations. After a protection key has been freed, it may no longer
be used in any protection-key-related operations.
An application should not call pkey_free() on any protection key which has been assigned to an address range by pkey_mprotect(2) and which
is still in use. The behavior in this case is undefined and may result in an error.
RETURN VALUE
On success, pkey_alloc() returns a positive protection key value. On success, pkey_free() returns zero. On error, -1 is returned, and
errno is set appropriately.
ERRORS
EINVAL pkey, flags, or access_rights is invalid.
ENOSPC (pkey_alloc()) All protection keys available for the current process have been allocated. The number of keys available is architec-
ture-specific and implementation-specific and may be reduced by kernel-internal use of certain keys. There are currently 15 keys
available to user programs on x86.
This error will also be returned if the processor or operating system does not support protection keys. Applications should always
be prepared to handle this error, since factors outside of the application's control can reduce the number of available pkeys.
VERSIONS
pkey_alloc() and pkey_free() were added to Linux in kernel 4.9; library support was added in glibc 2.27.
CONFORMING TO
The pkey_alloc() and pkey_free() system calls are Linux-specific.
NOTES
pkey_alloc() is always safe to call regardless of whether or not the operating system supports protection keys. It can be used in lieu of
any other mechanism for detecting pkey support and will simply fail with the error ENOSPC if the operating system has no pkey support.
The kernel guarantees that the contents of the hardware rights register (PKRU) will be preserved only for allocated protection keys. Any
time a key is unallocated (either before the first call returning that key from pkey_alloc() or after it is freed via pkey_free()), the
kernel may make arbitrary changes to the parts of the rights register affecting access to that key.
EXAMPLE
See pkeys(7).
SEE ALSO
pkey_mprotect(2), pkeys(7)
Linux 2019-03-06 PKEY_ALLOC(2)