HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- syslog owner & perms reset; how do I prevent?
Operating System - HP-UX
1833296
Members
3190
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2005 09:17 AM
01-26-2005 09:17 AM
We are modifying the owner and permissions of syslog.log so that it is available to specific groups only. That's fine, except that every time syslog starts up, or is restarted, it resets the ownership of the file back to root:sys, with perms of 644.
The modifications to syslog work on other platforms, and work on HP-UX, as long as we don't restart syslogd (or reboot the box..).
How do I work around this? I simply need to prevent the reset from happening, or be able to reset the reset every time it happens.
The modifications to syslog work on other platforms, and work on HP-UX, as long as we don't restart syslogd (or reboot the box..).
How do I work around this? I simply need to prevent the reset from happening, or be able to reset the reset every time it happens.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2005 09:24 AM
01-26-2005 09:24 AM
Solution
The place to make sure the reset happens everytime syslog is (re)started is in the /sbin/init.d/syslogd file. When that is used to start syslog, like when you reboot, syslog.log gets moved to OLDsyslog.log and a new syslog.log gets created with the command '> /var/adm/syslog/syslog.log' and the permissions on the file are 644 (the umask is set to 022 before the file is created).
So the thing to do is put your chown/chmod/chgrp in that file right after the file creating line. Then you should be set as long as /sbin/init.d/syslogd is used to start syslog.
So the thing to do is put your chown/chmod/chgrp in that file right after the file creating line. Then you should be set as long as /sbin/init.d/syslogd is used to start syslog.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2005 09:37 AM
01-26-2005 09:37 AM
Re: syslog owner & perms reset; how do I prevent?
And even though the answer is simple and clean, it works! Thanks, Patrick.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP