05-19-2015
Just distributing clues. This one was from some recent experience -- had to clean up a mess on many of 'my' systems where a jr. admin was changing permissions of system files and directories to give users "access" - 'cause he didn't know.
This User Gave Thanks to derekludwig For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All
I have written one shell script for GPRS route add is given below named GPRSRouteSet.sh
URL="www.google.com"
VBURL="10.5.2.211"
echo "Setting route for $URL for GPRS"
URL_Address=`nslookup $URL|grep Address:|grep -v "#"|awk -F " " '{print $2}'|head -1`
echo "Executing ... (3 Replies)
Discussion started by: mnmonu
3 Replies
2. UNIX for Dummies Questions & Answers
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
Discussion started by: suryashikha
5 Replies
3. Solaris
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
Discussion started by: ksvaisakh
5 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I seem to be having a problem with accumulation of root CRON jobs occuring when I have a user's cron job(s) running.
Here is an example of a user's crontab file:
*/1 * * * * echo "hello" > /dev/nullps aux|grep CRON
root 14333 0.0 0.0 91236 2172 ? S ... (12 Replies)
Discussion started by: Narnie
12 Replies
5. Solaris
I am getting the following error in the cron log:
! bad user (root) Wed Sep 22 14:30:00 2010
< root 8989 c Wed Sep 22 14:30:00 2010 rc=1
What does this mean? (5 Replies)
Discussion started by: jastanle84
5 Replies
6. Shell Programming and Scripting
I've been bashing my head on the desk for 2 days trying to get this to work, but I've had no luck. I'll try to be as clear as possible in my explanation without dragging out the details. I'm trying to set up a cron job for user "john" which runs a script. This script initiates an ssh connection to... (5 Replies)
Discussion started by: eh3civic
5 Replies
7. UNIX for Dummies Questions & Answers
I've been through many threads before i decide to create a separate thread.
I can't really find the solution to my (simple) problem.
Here's what I'm trying to achieve:
As "canar" user I want to run a command, let's say "/opt/ocaml/bin/ocaml" as "duck" user.
The only to achieve this is to... (1 Reply)
Discussion started by: canar
1 Replies
8. UNIX for Advanced & Expert Users
Hi!! one strange problem occurred with my RHEL 5 box.
i'm having logs folder with ownership of non-root user. Created some files with root user under logs folder.
here is the scene:
-rw-r----- 1 root root 1048227 Feb 28 12:34 SystemOut_13.02.28_12.34.10.log
-rw-r----- 1 root root ... (6 Replies)
Discussion started by: sukhdip
6 Replies
9. Shell Programming and Scripting
Currently in my system Red Hat is installed. And Many user connect to my machine via SSH Techia Terminal.
I want to give some users a root level access.
Can anyone please help me how to make it possible. I too searched on the Google but didn't find the correct way
Regards
ADI (4 Replies)
Discussion started by: adisky123
4 Replies
10. Shell Programming and Scripting
I am trying a cron on root user to backup to tape using TAR command
here is the cron entry
11 08 * * 6 /erdhot1cron 2>&1 >> /test3/scripts/dba/erdhot1cron.log
here is script inside - edhot1cron
#!/bin/bash
vsysdt=`date +%d%m%y`
date
tar -cvf /dev/st0... (4 Replies)
Discussion started by: vijaymec50
4 Replies
LEARN ABOUT MOJAVE
systemd-tmpfiles
SYSTEMD-TMPFILES(8) systemd-tmpfiles SYSTEMD-TMPFILES(8)
NAME
systemd-tmpfiles, systemd-tmpfiles-setup.service, systemd-tmpfiles-setup-dev.service, systemd-tmpfiles-clean.service, systemd-tmpfiles-
clean.timer - Creates, deletes and cleans up volatile and temporary files and directories
SYNOPSIS
systemd-tmpfiles [OPTIONS...] [CONFIGFILE...]
System units:
systemd-tmpfiles-setup.service
systemd-tmpfiles-setup-dev.service
systemd-tmpfiles-clean.service
systemd-tmpfiles-clean.timer
User units:
systemd-tmpfiles-setup.service
systemd-tmpfiles-clean.service
systemd-tmpfiles-clean.timer
DESCRIPTION
systemd-tmpfiles creates, deletes, and cleans up volatile and temporary files and directories, based on the configuration file format and
location specified in tmpfiles.d(5).
If invoked with no arguments, it applies all directives from all configuration files. If one or more absolute filenames are passed on the
command line, only the directives in these files are applied. If "-" is specified instead of a filename, directives are read from standard
input. If only the basename of a configuration file is specified, all configuration directories as specified in tmpfiles.d(5) are searched
for a matching file.
OPTIONS
The following options are understood:
--create
If this option is passed, all files and directories marked with f, F, w, d, D, v, p, L, c, b, m in the configuration files are created
or written to. Files and directories marked with z, Z, t, T, a, and A have their ownership, access mode and security labels set.
--clean
If this option is passed, all files and directories with an age parameter configured will be cleaned up.
--remove
If this option is passed, the contents of directories marked with D or R, and files or directories themselves marked with r or R are
removed.
--user
Execute "user" configuration, i.e. tmpfiles.d files in user configuration directories.
--boot
Also execute lines with an exclamation mark.
--prefix=path
Only apply rules with paths that start with the specified prefix. This option can be specified multiple times.
--exclude-prefix=path
Ignore rules with paths that start with the specified prefix. This option can be specified multiple times.
--root=root
Takes a directory path as an argument. All paths will be prefixed with the given alternate root path, including config search paths.
Note that this option does not alter how the users and groups specified in the configuration files are resolved. With or without this
option, users and groups are always resolved according to the host's user and group databases, any such databases stored under the
specified root directories are not consulted.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
It is possible to combine --create, --clean, and --remove in one invocation. For example, during boot the following command line is
executed to ensure that all temporary and volatile directories are removed and created according to the configuration file:
systemd-tmpfiles --remove --create
UNPRIVILEGED --CLEANUP OPERATION
systemd-tmpfiles tries to avoid changing the access and modification times on the directories it accesses, which requires CAP_ADMIN
privileges. When running as non-root, directories which are checked for files to clean up will have their access time bumped, which might
prevent their cleanup.
EXIT STATUS
On success, 0 is returned. If the configuration was invalid (invalid syntax, missing arguments, ...), so some lines had to be ignored, but
no other errors occurred, 65 is returned (EX_DATAERR from /usr/include/sysexits.h). Otherwise, 1 is returned (EXIT_FAILURE from
/usr/include/stdlib.h).
SEE ALSO
systemd(1), tmpfiles.d(5)
systemd 237 SYSTEMD-TMPFILES(8)