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 OSF1
chroot
chroot(8) System Manager's Manual chroot(8)NAME
chroot - Changes the root directory of a command
SYNOPSIS
/usr/sbin/chroot directory command
DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command
executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated
by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in
effect, directory is relative to the current root of the running process.
Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file
system and the relevant pathnames for the files map correctly in the new root file system.
For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and
/etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the
output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on
description files produced by the ctab command may also fail if the required description files are not present in the new root file system.
The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe-
cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring
use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new
root file system in the appropriate locations.
EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is
on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec-
ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root
file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must
contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among
others) on the new root file system.
Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and
return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and
the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command
similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a:
chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out
The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c
file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial
root file system. To create a file relative to the original root rather than the new one, use this syntax and enter:
chroot directory command > file
CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite
the file system.
FILES
Specifies the command path.
RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1)
Functions: chdir(2), chroot(2)exec(2) delim off
chroot(8)