Sponsored Content
Full Discussion: syslog file
Operating Systems HP-UX syslog file Post 302153811 by blowtorch on Wednesday 26th of December 2007 11:56:32 PM
Old 12-27-2007
I cannot say for sure, but there might be a problem with memory. If you have root, you can try to run the command mentioned (/opt/resmon/bin/resdata -R 176357378 -r /system/events/memory/8 -n 176357391 -a) to get more details.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

syslog log file sizes

I am logging the messages from a router network and the log files are getting enormous is there any way to limit the size of the log file by either wrapping it or preferably creating a new one and renaiming the old. Cheers mike (4 Replies)
Discussion started by: mscomms
4 Replies

2. SCO

Syslog file too large

I have a very large syslog file on a Unixware 7.01 system. Can I delete the syslog file and will Unixware 7.01 recreate it? If not, what is the best way to clear the syslog file to reduce its size? (1 Reply)
Discussion started by: rries
1 Replies

3. UNIX for Advanced & Expert Users

Large Unixware 7.01 Syslog file

I have a very large syslog file on a Unixware 7.01 system. Can I delete the syslog file and will Unixware 7.01 recreate it? If not, what is the best way to clear the syslog file to reduce its size? (2 Replies)
Discussion started by: rries
2 Replies

4. Solaris

syslog file is full

dear all i have solaris 10 and it send mail into the file syslog file how can i stop this because is too big ........ and big day by day thanks to all murad jaber (6 Replies)
Discussion started by: murad.jaber
6 Replies

5. HP-UX

How to Redirect the error messages from Syslog file to our own Application Log File

Hello, I am New to Unix. I am Using HP-UX 9000 Series for my Application. I am Currently Facing an Issue that the error messages are being written in the syslog file instead of the Application Log File. The Codes for that Syslog.h is written in Pro*C. I want to know how to Redirect these... (3 Replies)
Discussion started by: balasubramaniam
3 Replies

6. AIX

/etc/syslog.conf file and warnings

Hi All, I am working on a server which has an /etc/syslog.conf file with the following entries (example): local6.debug /dplogs/uss1udp001.log rotate size 1500m time 1d files 14 local7.debug /dplogs/uss1udp002.log rotate size 1500m time 1d files 14 -----------------------------... (3 Replies)
Discussion started by: jeffpas
3 Replies

7. UNIX for Advanced & Expert Users

writing the log file into syslog

Hi, we are trying to enable auditing for few oracle 9i database. and right now it writies into adump directory. As adump can be read/write by oracle user so could it be possible to write into syslog while oracle keeps writing to adump . thanks in advance. Pk (2 Replies)
Discussion started by: p4cldba
2 Replies

8. AIX

syslog file permission

Hi, I have setup syslog.conf to rotate and compress a messages file but the only problem is when it creates the new log file it creates it with the following permissions -rw-r-----. I just wondered if there is anywhere where i can specify what permissions this new log file is created with so I... (4 Replies)
Discussion started by: elmesy
4 Replies

9. Shell Programming and Scripting

Retrieving Information From A Syslog File

Hi, I have a number of firewalls that send there traffic logs to a syslog server. Each log entry takes up about 3 lines and the text within the log entry is delimited by a space. There are parts of the three lines that I need from every traffic log entry. I have been using a combination of sed,... (2 Replies)
Discussion started by: andyblaylock
2 Replies

10. Ubuntu

How redirect syslog message to a specified file?

Hello to everyone! I have a question about syslog. I want put the messages of log in a particular file but really i don't know how to do that or i don't get the results that I want. I do this: #include <stdio.h> #include <stdlib.h> #include <syslog.h> int main (void) { ... (4 Replies)
Discussion started by: Kovalevski
4 Replies
wine_selinux(8) 						SELinux Policy wine						   wine_selinux(8)

NAME
wine_selinux - Security Enhanced Linux Policy for the wine processes DESCRIPTION
Security-Enhanced Linux secures the wine processes via flexible mandatory access control. The wine processes execute with the wine_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep wine_t ENTRYPOINTS
The wine_t SELinux type can be entered via the unlabeled_t, proc_type, file_type, wine_exec_t, mtrr_device_t, filesystem_type, sysctl_type file types. The default entrypoint paths for the wine_t domain are the following: all files on the system, /usr/bin/wine.*, /opt/teamviewer(/.*)?/bin/wine.*, /opt/google/picasa(/.*)?/bin/wdi, /opt/google/picasa(/.*)?/bin/wine.*, /opt/google/picasa(/.*)?/bin/msiexec, /opt/google/picasa(/.*)?/bin/notepad, /opt/google/picasa(/.*)?/bin/progman, /opt/google/picasa(/.*)?/bin/regedit, /opt/google/picasa(/.*)?/bin/regsvr32, /opt/google/picasa(/.*)?/Picasa3/.*exe, /opt/google/picasa(/.*)?/bin/uninstaller, /opt/cxoffice/bin/wine.*, /opt/picasa/wine/bin/wine.*, /usr/bin/msiexec, /usr/bin/notepad, /usr/bin/regedit, /usr/bin/regsvr32, /usr/bin/uninstaller, /home/[^/]*/cxoffice/bin/wine.+, /dev/cpu/mtrr PROCESS TYPES
SELinux defines process types (domains) for each process running on the system You can see the context of a process using the -Z option to ps Policy governs the access confined processes have to files. SELinux wine policy is very flexible allowing users to setup their wine pro- cesses in as secure a method as possible. The following process types are defined for wine: wine_t Note: semanage permissive -a wine_t can be used to make the process type wine_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. BOOLEANS
SELinux policy is customizable based on least access required. wine policy is extremely flexible and has several booleans that allow you to manipulate the policy and run wine with the tightest access possible. If you want to deny user domains applications to map a memory region as both executable and writable, this is dangerous and the executable should be reported in bugzilla, you must turn on the deny_execmem boolean. Enabled by default. setsebool -P deny_execmem 1 If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by default. setsebool -P deny_ptrace 1 If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default. setsebool -P domain_fd_use 1 If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by default. setsebool -P domain_kernel_load_modules 1 If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. setsebool -P fips_mode 1 If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default. setsebool -P global_ssp 1 If you want to control the ability to mmap a low area of the address space, as configured by /proc/sys/kernel/mmap_min_addr, you must turn on the mmap_low_allowed boolean. Disabled by default. setsebool -P mmap_low_allowed 1 If you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. Enabled by default. setsebool -P secure_mode_insmod 1 If you want to boolean to determine whether the system permits loading policy, setting enforcing mode, and changing boolean values. Set this to true and you have to reboot to set it back, you must turn on the secure_mode_policyload boolean. Enabled by default. setsebool -P secure_mode_policyload 1 If you want to allow unconfined executables to make their heap memory executable. Doing this is a really bad idea. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the selin- uxuser_execheap boolean. Disabled by default. setsebool -P selinuxuser_execheap 1 If you want to allow all unconfined executables to use libraries requiring text relocation that are not labeled textrel_shlib_t, you must turn on the selinuxuser_execmod boolean. Enabled by default. setsebool -P selinuxuser_execmod 1 If you want to allow unconfined executables to make their stack executable. This should never, ever be necessary. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla, you must turn on the selin- uxuser_execstack boolean. Enabled by default. setsebool -P selinuxuser_execstack 1 If you want to support X userspace object manager, you must turn on the xserver_object_manager boolean. Enabled by default. setsebool -P xserver_object_manager 1 If you want to allow ZoneMinder to run su/sudo, you must turn on the zoneminder_run_sudo boolean. Disabled by default. setsebool -P zoneminder_run_sudo 1 MANAGED FILES
The SELinux process type wine_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. file_type all files on the system FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type. You can see the context of a file using the -Z option to ls Policy governs the access confined processes have to these files. SELinux wine policy is very flexible allowing users to setup their wine processes in as secure a method as possible. STANDARD FILE CONTEXT SELinux defines the file context types for the wine, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk. semanage fcontext -a -t wine_exec_t '/srv/wine/content(/.*)?' restorecon -R -v /srv/mywine_content Note: SELinux often uses regular expressions to specify labels that match multiple files. The following file types are defined for wine: wine_exec_t - Set files with the wine_exec_t type, if you want to transition an executable to the wine_t domain. Paths: /usr/bin/wine.*, /opt/teamviewer(/.*)?/bin/wine.*, /opt/google/picasa(/.*)?/bin/wdi, /opt/google/picasa(/.*)?/bin/wine.*, /opt/google/picasa(/.*)?/bin/msiexec, /opt/google/picasa(/.*)?/bin/notepad, /opt/google/picasa(/.*)?/bin/progman, /opt/google/picasa(/.*)?/bin/regedit, /opt/google/picasa(/.*)?/bin/regsvr32, /opt/google/picasa(/.*)?/Picasa3/.*exe, /opt/google/picasa(/.*)?/bin/uninstaller, /opt/cxoffice/bin/wine.*, /opt/picasa/wine/bin/wine.*, /usr/bin/msiexec, /usr/bin/notepad, /usr/bin/regedit, /usr/bin/regsvr32, /usr/bin/uninstaller, /home/[^/]*/cxoffice/bin/wine.+ wine_home_t - Set files with the wine_home_t type, if you want to store wine files in the users home directory. Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. COMMANDS
semanage fcontext can also be used to manipulate default file context mappings. semanage permissive can also be used to manipulate whether or not a process type is permissive. semanage module can also be used to enable/disable/install/remove policy modules. semanage boolean can also be used to manipulate the booleans system-config-selinux is a GUI tool available to customize SELinux policy settings. AUTHOR
This manual page was auto-generated using sepolicy manpage . SEE ALSO
selinux(8), wine(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8) wine 14-06-10 wine_selinux(8)
All times are GMT -4. The time now is 09:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy