Sponsored Content
Special Forums IP Networking Howto configure AIX DHCP Client ? Post 9431 by zumbi on Friday 26th of October 2001 01:08:58 PM
Old 10-26-2001
btw. if I edit the /etc/hosts and insert my local hostname and my current IP, I can run the CDE without any trouble,.
thx for hints.
 

10 More Discussions You Might Find Interesting

1. Linux

How to configure Dhcp in linux?

Please let me know step by step, I am new to this configuration.... (2 Replies)
Discussion started by: dhineshcs
2 Replies

2. SCO

dhcp client

I have openserver 5.0.7 running on a machine and would like to know how to configure a dhcp client for it and make it run at startup. Thank you. (1 Reply)
Discussion started by: izzzy
1 Replies

3. IP Networking

How to configure DHCP to Static IP

I am pretty new to this. My router was earlier configured to enable DHCP, thus my UNIX box is using the dhcp address, i.e. I have to do a ifconfig dhcp hme0 start. Since I am planning to use my NT as a web server, I needed to use the static IP address. How do I configure the unix box to use the... (5 Replies)
Discussion started by: lee30320
5 Replies

4. Solaris

Failed to configure IPv4 for DHCP afe0

Hi All, i have been accessing ip address through DHCP for my windows..i tried to configure the same for solaris also and got the error " Failed to configure IPv4 for DHCP afe0 " can anyone explain what should i do ...i want to acees internet in solaris am i need to configure for... (0 Replies)
Discussion started by: srikanthg
0 Replies

5. AIX

aix-configure nim client

:b:Hi... I need help to configure nim client on nim server.. can i define aix 5.3.4.0 on aix 5.3.7.0 nim server.. while i m configuring nim client on nim server its getting msg that images not same.. i need to confirm that both version should be same or not.. Thanks.. (5 Replies)
Discussion started by: sumathi.k
5 Replies

6. IP Networking

HOWTO: Linux multihomed dns client

The Linux resolver queries all nameservers in the order they are listed in /etc/resolver.conf. If a nameserver times out, it advances on to the following nameserver. But, if a nameserver returns "not found" (NXDOMAIN) it stops. This behaviour is problematic when you need to resolve names from... (0 Replies)
Discussion started by: colemar
0 Replies

7. IP Networking

HOWTO: Linux multihomed dns client - reverse lookup

The following thread is closed: 133552-howto-linux-multihomed-dns-client (Sorry I am not allowed to post URLs) Therefore I write this append in an own thread. The HOWTO in the referenced thread helped me a lot and I only want to append how to make reverse lookup working for a local zone: ... (0 Replies)
Discussion started by: scheruga
0 Replies

8. Solaris

How to configure the host to dhcp mode

I try a static ip assign mode while i installed the Solaris 10(U 8). But i can't access the internet, i try the ifconfig -a command and see my configuration is correct in the interface. So i want to get my ip using dhcp. I search from internet. They give me the suggestions. ifconfig interface... (1 Reply)
Discussion started by: papertiger
1 Replies

9. Solaris

Configure network in unix with dynamic ip on my DHCP server?

can anyone tell me how can i configure network in unix with dynamic ip on my DHCP server?? (7 Replies)
Discussion started by: Reham.Donia
7 Replies

10. IP Networking

About Configure the DHCP to assign the Default-Gateway

I have a question. How to write the DHCP to assign the default-gateway to clients. Thank you. (2 Replies)
Discussion started by: thsecmaniac
2 Replies
CRONTAB(1)							   User Commands							CRONTAB(1)

NAME
crontab - maintains crontab files for individual users SYNOPSIS
crontab [-u user] file crontab [-u user] [-l | -r | -e] [-i] [-s] crontab -n [ hostname ] crontab -c DESCRIPTION
Crontab is the program used to install, remove or list the tables used to serve the cron(8) daemon. Each user can have their own crontab, and though these are files in /var/spool/, they are not intended to be edited directly. For SELinux in MLS mode, you can define more crontabs for each range. For more information, see selinux(8). In this version of Cron it is possible to use a network-mounted shared /var/spool/cron across a cluster of hosts and specify that only one of the hosts should run the crontab jobs in the particular directory at any one time. You may also use crontab(1) from any of these hosts to edit the same shared set of crontab files, and to set and query which host should run the crontab jobs. Running cron jobs can be allowed or disallowed for different users. For this purpose, use the cron.allow and cron.deny files. If the cron.allow file exists, a user must be listed in it to be allowed to use cron If the cron.allow file does not exist but the cron.deny file does exist, then a user must not be listed in the cron.deny file in order to use cron. If neither of these files exists, only the super user is allowed to use cron. Another way to restrict access to cron is to use PAM authentication in /etc/security/access.conf to set up users, which are allowed or disallowed to use crontab or modify system cron jobs in the /etc/cron.d/ directory. The temporary directory can be set in an environment variable. If it is not set by the user, the /tmp directory is used. OPTIONS
-u Appends the name of the user whose crontab is to be modified. If this option is not used, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) may confuse crontab, thus, when executing commands under su(8) you should always use the -u option. If no crontab exists for a particular user, it is created for him the first time the crontab -u command is used under his username. -l Displays the current crontab on standard output. -r Removes the current crontab. -e Edits the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. -i This option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab. -s Appends the current SELinux security context string as an MLS_LEVEL setting to the crontab file before editing / replacement occurs - see the documentation of MLS_LEVEL in crontab(5). -n This option is relevant only if cron(8) was started with the -c option, to enable clustering support. It is used to set the host in the cluster which should run the jobs specified in the crontab files in the /var/spool/cron directory. If a hostname is supplied, the host whose hostname returned by gethostname(2) matches the supplied hostname, will be selected to run the selected cron jobs subsequently. If there is no host in the cluster matching the supplied hostname, or you explicitly specify an empty hostname, then the selected jobs will not be run at all. If the hostname is omitted, the name of the local host returned by gethostname(2) is used. Using this option has no effect on the /etc/crontab file and the files in the /etc/cron.d directory, which are always run, and considered host-specific. For more information on clustering support, see cron(8). -c This option is only relevant if cron(8) was started with the -c option, to enable clustering support. It is used to query which host in the cluster is currently set to run the jobs specified in the crontab files in the directory /var/spool/cron , as set using the -n option. SEE ALSO
crontab(5), cron(8) FILES
/etc/cron.allow /etc/cron.deny STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. DIAGNOSTICS
An informative usage message appears if you run a crontab with a faulty command defined in it. AUTHOR
Paul Vixie <vixie@isc.org> Colin Dean <colin@colin-dean.org> cronie 2012-11-22 CRONTAB(1)
All times are GMT -4. The time now is 05:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy