Well, this is the second bug (the first was ipv6) I've found on this stupid router (like all d-link stuff) that made me crazy...
Some applications are unable to resolve domains (such as wget, lynx and whois in my case) and I didn't knew why until I changed the default nameserver (the router address from dhcp) on /etc/resolv.config to the ones gave from my ISP: ALL MAGICALLY WORKS NOW (FUCK!!!)
If you don't like dhcpcd to change your nameserver settings then either set DHCLIENT_MODIFY_RESOLV_CONF=no in /etc/sysconfig/network/dhcp, or set MODIFY_RESOLV_CONF_DYNAMICALLY=no in /etc/sysconfig/network/config or (manually) use dhcpcd with -R. If you only want to keep your searchlist, set DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or (manually) use the -K option.
see you
antonio
giovedì, novembre 24, 2005
giovedì, novembre 17, 2005
the Cron Jobs :)
(* extract from suse administration manual )
The cron tables are located in /var/spool/cron/tabs. /etc/crontab serves as a systemwide cron table. Enter the name of the user who should run the command directly after the time table. In Example 10.1, “Example of an Entry in /etc/crontab”, root is entered. Package-specific tables, located in /etc/cron.d, have the same format. See man cron.
Example 10.1. Example of an Entry in /etc/crontab
1-59/5 * * * * root test -x /usr/sbin/atrun && /usr/sbin/atrun
/etc/crontab cannot be processed with crontab -e. It must be loaded directly into an editor, modified, then saved.
A number of packages install shell scripts to the directories /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly, whose instructions are controlled by /usr/lib/cron/run-crons. /usr/lib/cron/run-crons is run every 15 minutes from the main table (/etc/crontab). This guarantees that processes that may have been neglected can be run at the proper time.
The daily system maintenance jobs have been distributed to various scripts for reasons of clarity. They are contained in the package aaa_base. /etc/cron.daily contains, for instance, the components backup-rpmdb, clean-tmp, or clean-vi.
The cron tables are located in /var/spool/cron/tabs. /etc/crontab serves as a systemwide cron table. Enter the name of the user who should run the command directly after the time table. In Example 10.1, “Example of an Entry in /etc/crontab”, root is entered. Package-specific tables, located in /etc/cron.d, have the same format. See man cron.
Example 10.1. Example of an Entry in /etc/crontab
1-59/5 * * * * root test -x /usr/sbin/atrun && /usr/sbin/atrun
/etc/crontab cannot be processed with crontab -e. It must be loaded directly into an editor, modified, then saved.
A number of packages install shell scripts to the directories /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly, whose instructions are controlled by /usr/lib/cron/run-crons. /usr/lib/cron/run-crons is run every 15 minutes from the main table (/etc/crontab). This guarantees that processes that may have been neglected can be run at the proper time.
The daily system maintenance jobs have been distributed to various scripts for reasons of clarity. They are contained in the package aaa_base. /etc/cron.daily contains, for instance, the components backup-rpmdb, clean-tmp, or clean-vi.
lunedì, novembre 14, 2005
Skype for Linux Resources
Iscriviti a:
Post (Atom)