I'm not sure what it means to put a path or put a user.
Quote:
I use the root account. tcpdump is installed on the root.
What do you mean by "installed on the root"? tcpdump is installed inside /root? If you've put tcpdump anywhere funny, you should run it with an absolute path like /path/to/tcpdump -s2000 ... Otherwise it will have no idea where to look for it.
Quote:
I also save files to the root as well. What should I be using if not just /root ?
You can save them wherever you want. The system can't stop you because you're root. Running as root may be unavoidable if you need to run tcpdump. In short, /root will work.
Last edited by Corona688; 04-15-2011 at 06:42 PM..
Hello!
my crontab -e dosent work. Im getting this error message:
sh: VI: not found
The crontab files was not changed.
How do i make it work? I think you should use "export editor=vi"
or something. But i cant seem to get the correct line!
pleas help... (11 Replies)
Not sure what has changed in the Unix environment.
The following script which was working is now not working.
#!/usr/bin/ksh
# -----------------------------------------------------------------------------
# File: monitor_db.sh
#
#... (1 Reply)
Hi All,
I have created crontab using following steps-
1) crontab -e
(edited the file with) 0 10 * * 1-5 /home/user01/exercise/cron.sh
2) then saved this file with :wq
3) cron.sh contains the code-
#!/bin/bash
DAY=`date +%a`
mkdir abc_${DAY}
4) done the execut permision... (3 Replies)
Hello,
My question is very basic for the settings to SSH my home PC from work.
Home network two PC:
Internet comes into my house through ISP modem and then the two PCs are connected with the router (Trendnet). The IPs for my PCs are
How to set other stuffs for me to access my home PC from... (5 Replies)
Hi,
0 9 1,2,3,4,5,6,7 3,4 6
I want a cronjob to run on every 1st Sat of Mar & Apr. But the above schedule is running is running on the 1st 7 days. How do i rectify it?
Thanks in advance. (2 Replies)
Hi, i wanted to schedule a backup script to run on 7.30pm every 1st Sat of month MAR, APR, SEP, OCT.
Am i understanding it correctly? Because it doesn't seem to run according to the schedule i needed.
= (7.30pm) & (1st to 7th day of the month) & (MAR, APR, SEP, OCT) & (Sat)
30 19 1-7... (1 Reply)
Hi Team,
Please help me to set one script in crontab.
I have one script and inside script, its creating one log file for saving ouptut of script. i have to out that script in crontab. When i put the script in cronatab, it executed and log file created but no data in log.
like this i put in... (3 Replies)
Hi All,
Can anyone tell me how to schedule the dbshell.sh script to run on sunday.
I have scheduled as 1 19 7 * * /home/svr/dbshell.sh. kindly confirm confirm whether coded "7" or it should set to '0'.
unix:$ crontab -l
0 19 6 * * /home/svr/dbemail.sh
1 19 7 * * /home/svr/dbshell.sh (2 Replies)
Hello,
Here is my crontab
# Reboot one Sunday out of 2 at 02:00
0 2 * * 0/2 /usr/bin/reboot
2017-04-16
2017-04-23
2017-04-30
and so on
I tested my crontab here, it seems to work
Http://cron.schlitt.info/index.php?c...=100&test=Test
However on my distrib linux mageďa
When I register... (4 Replies)
Discussion started by: amazigh42
4 Replies
LEARN ABOUT HPUX
chroot
chroot(2) System Calls Manual chroot(2)NAME
chroot() - change root directory
SYNOPSIS DESCRIPTION
causes the named directory to become the root directory, the starting point for path searches for path names beginning with path points to
a path name naming a directory. The user's working directory is unaffected by the system call.
The entry in the root directory is interpreted to mean the root directory itself. Thus, cannot be used to access files outside the subtree
rooted at the root directory.
Security Restrictions
The effective user ID of the process must be a user with the privilege to change the root directory.
See privileges(5) for more information about privileged access on systems that support fine-grained privileges.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
is set to indicate the error.
ERRORS
fails and the root directory remains unchanged if one or more of the following is true:
Any component of the path name is not a directory.
The named directory does not exist or a component of the
path does not exist.
The effective user
ID is not a user who has the privilege.
path points outside the allocated address space of the process. The reliable detection of this error is implementation
dependent.
The length of the specified path name exceeds
bytes, or the length of a component of the path name exceeds bytes while is in effect.
Too many symbolic links were encountered in translating the path
name.
WARNINGS
Obsolescent Interfaces
is to be obsoleted at a future date.
SEE ALSO chroot(1M), chdir(2), privileges(5).
STANDARDS CONFORMANCE
TO BE OBSOLETED chroot(2)