11-26-2008
How about SELinux? Could this do the trick? I am running on RHEL 4.
Again, I am just googling around and came across this. Could a .sh file be called twice to start up 2 sessions of the software, but each having a different context accoring to the SELinux permissions: one for deptA, the other for deptB?
Steve
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi there.
How do I make the DB connection see the parameter variables passed to the unix script ? The code snippet below isn't working properly.
sqlplus << EOF
user1@db1/pass1
BEGIN
PACKAGE1.perform_updates($1,$2,$3);
END;
EOF
Thanks in advance,
Abrahao. (2 Replies)
Discussion started by: 435 Gavea
2 Replies
2. Solaris
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies
3. Shell Programming and Scripting
Hi
I want to do something that might sound strange.
I have a code that in written in C and is executed at startup (it's a custom process). It occasionally calls some bash scripts.
The process doesn't have any terminal associated with it.
One thing I don't know how to do is to start a... (5 Replies)
Discussion started by: alirezan
5 Replies
4. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
5. Shell Programming and Scripting
Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
Discussion started by: jgt
3 Replies
6. Solaris
what is the difference between desktop session and console session in solaris
as i am wondering we use option -text for the former and -nowin for the later (1 Reply)
Discussion started by: kishanreddy
1 Replies
7. Solaris
Hi,
i got the following error when i tried to access the cygwin x server from a windows XP PC.
"xdmcp fatal error session failed session 23 failed for display"
Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies
8. Linux
Hi Guys,
Is there a way to recover a lost session? I was working in a server and that lost the connection, now, I have a new session but all the previous processes that I was running, like scripts, etc, are still running.
Is there a way to bring them to my session?
Best regards,
Marco. (4 Replies)
Discussion started by: ocramas
4 Replies
9. Shell Programming and Scripting
I have below directories. All directories create as per some some logging software by today so all directories current time is today date.
Direct 2013-08-12 23123
Direct 2013-08-13 24121
Direct 2013-08-14 34513
Direct 2013-08-31 15435
...........
Direct 2013-09-12 53145
Direct... (5 Replies)
Discussion started by: learnbash
5 Replies
LEARN ABOUT CENTOS
sepolicy-communicate
sepolicy-communicate(8) sepolicy-communicate(8)
NAME
sepolicy-communicate - Generate a report showing if two SELinux Policy Domains can communicate
SYNOPSIS
sepolicy communicate [-h] -s SOURCE -t TARGET [-c TCLASS] [-S SOURCEACCESS] [-T TARGETACCESS]
DESCRIPTION
Use sepolicy communicate to examine SELinux Policy to if a source SELinux Domain can communicate with a target SELinux Domain. The default
command looks to see if there are any file types that the source domain can write, which the target domain can read.
OPTIONS
-c, --class
Specify the SELinux class which the source domain will attempt to communicate with the target domain. (Default file)
-h, --help
Display help message
-s, --source
Specify the source SELinux domain type.
-S, --sourceaccess
Specify the list of accesses used by the source SELinux domain type to communicate with the target domain. Default Open, Write.
-t, --target
Specify the target SELinux domain type.
-T, --targetaccess
Specify the list of accesses used by the target SELinux domain type to receive communications from the source domain. Default Open,
Read.
AUTHOR
This man page was written by Daniel Walsh <dwalsh@redhat.com>
SEE ALSO
sepolicy(8), selinux(8)
20121005 sepolicy-communicate(8)