Hi, I'm trying to write a bash script to find some files. However it seems that the find command is not behaving the same way when the script is executed as it does when executed from the command line:
Script extract:
#!/bin/bash
...
NEW="/usr/bin/find current/applications/ -name '*jar'... (3 Replies)
I am thankful for this site and for the many links provided. I have been going through one of the tutorials, but as I try some things, they don't seem to work.
I am wondering if there is something I need first before being able to use a tutorial (like version number (HP-UX) or how I am getting... (1 Reply)
I use FreeBSD,and use signal,like follows:
signal(SIGHUP,sig_hup);
signal(SIGIO,sig_io);
when I run call following code,it can run,but I find a puzzled question,it should print some information,such as printf("execute main()") will print execute main(),but in fact,printf fuction print... (2 Replies)
Hi all.
I have a script as below:
cutmth=`TZ=CST+2160 date +%b`
export cutmth
echo $cutmth >> date.log
sed -n "/$cutmth/$p" alert_sbdev1.log > alert_summ.log
My purpose is to run through the alert_sbdev1.log and find the 1st occurence of 'Jan' and send everything after that line to... (4 Replies)
Following code is detecting solaris daytime,when I run it,I can't get any result,code is follows:
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#define BUFFSIZE 150
int main(){
... (2 Replies)
I use Solaris 10, I use following code:
#include <signal.h>
int main(void){
printf("----------testing-----------");
if(signal(SIGUSR1,sig_usr)==SIG_ERR)
err_sys("can't catch SIGUSR1");
for(;;)
pause();
sig_user(int signo){
.....
}
when I run above code,it print nothing... (3 Replies)
Hi,
I installed solaris 10 x86 on my local system. it was working fine. today when i started the system, it started up without any problem. when i tried to open the terminal it didn't open any terminal.
Plz help me (0 Replies)
Hello:
I can't get equivalence classes to work in globs or when passing them to tr. If I understood correctly, matches e, é, è, ê, etc. But when using them with utilities like tr they don't work. Here's an example found in the POSIX standard:
I decided to create the aforementioned files in... (9 Replies)
Discussion started by: Cacializ
9 Replies
LEARN ABOUT LINUX
logprof.conf
LOGPROF.CONF(5) AppArmor LOGPROF.CONF(5)NAME
logprof.conf - configuration file for expert options that modify the behavior of the AppArmor aa-logprof(1) program.
DESCRIPTION
The aa-logprof(1) program can be configured to have certain default behavior by the contents of logprof.conf.
The [qualifiers] section lists specific programs that should have a subset of the full ix/px/ux list when asking what mode to execute it
using.
Since creating a separate profile for /bin/bash is dangerous, we can specify that for /bin/bash, only (I)nherit, (U)nconstrained, and
(D)eny should be allowed options and only those will show up in the prompt when we're asking about adding that to a profile.
Likewise, if someone currently exec's /bin/mount in ix or px mode, things won't work, so we can provide only (U)nconstrained and (D)eny as
options.
And certain apps like grep, awk, sed, cp, and mkdir should always inherit the parent profile rather than having their own profile or
running unconfined, so for them we can specify that only (I)nherit and (D)eny are the allowed options.
Any programs that are not listed in the qualifiers section get the full (I)nherit / (P)rofile / (U)nconstrained / (D)eny option set.
If the user is doing something tricky and wants different behavior, they can tweak or remove the corresponding line in the conf file.
The [defaulthat] section lists changehat-aware programs and what hat aa-logprof(1) will collapse the entries to for that program if the
user specifies that the access should be allowed, but should not have it's own hat.
The [globs] section allows modification of the logprof rule engine with respect to globbing suggestions that the user will be prompted
with.
The format of each line is-- "<perl glob> = <apparmor glob>".
When aa-logprof(1) asks about a specific path, if the perl glob matches the path, it replaces the part of the path that matched with the
corresponding apparmor glob and adds it to the list of globbing suggestions.
Lines starting with # are comments and are ignored.
EXAMPLE
[qualifiers]
# things will very likely be painfully broken if bash has it's own profile
/bin/bash = iu
# mount doesn't work if it's confined
/bin/mount = u
# these helper utilities should inherit the parent profile and
# shouldn't have their own profiles
/bin/awk = i
/bin/grep = i
/bin/sed = i
[defaulthat]
/usr/sbin/sshd = EXEC
/usr/sbin/httpd2 = DEFAULT_URI
/usr/sbin/httpd2-prefork = DEFAULT_URI
[globs]
# /foo/bar/lib/libbaz.so -> /foo/bar/lib/lib*
/lib/lib[^/]+so[^/]*$ = /lib/lib*so*
# strip kernel version numbers from kernel module accesses
^/lib/modules/[^/]+/ = /lib/modules/*/
# strip pid numbers from /proc accesses
^/proc/d+/ = /proc/*/
BUGS
If you find any bugs, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>.
SEE ALSO apparmor(7), apparmor.d(5), aa-enforce(1), aa-complain(1), aa-disable(1), aa_change_hat(2), aa-logprof(1), aa-genprof(1), and
<http://wiki.apparmor.net>.
AppArmor 2.7.103 2012-06-28 LOGPROF.CONF(5)