Sponsored Content
Full Discussion: admintool : error display..
Top Forums UNIX for Dummies Questions & Answers admintool : error display.. Post 32975 by yls177 on Wednesday 11th of December 2002 08:47:13 PM
Old 12-11-2002
xmanager is shareware will will expire indefinitely..

is there any freeware which is equivalent to xmanager.. thanks
yls177
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Admintool

Hi, Does anyone here know where I can find out what commands admintool runs while adding a new user and setting up the account? Reason being is the script I am writting, I can add the user create the path. But it wont set the path for the user. The password well it wont add without... (1 Reply)
Discussion started by: merlin
1 Replies

2. UNIX for Dummies Questions & Answers

sun solstice, admintool, smc

hi, i tried these sun command on a sun0s 5.7 but get the "cant open display" message. please advise. i am using netterm to telnet. (5 Replies)
Discussion started by: yls177
5 Replies

3. UNIX for Dummies Questions & Answers

problem with admintool

hi, after i execute admintool, i got the below "Error, cant open display" what is wrong? thanks (5 Replies)
Discussion started by: yls177
5 Replies

4. UNIX for Dummies Questions & Answers

Admintool

I am new to unix....How do I enable XWindows... Or for that matter, use Admintool. .....Pls. help. Thanks. PS. I am running Solaris 8. (3 Replies)
Discussion started by: d4jtwvb
3 Replies

5. UNIX for Advanced & Expert Users

Printer Error with Admintool

Hi I have a unix box [ Solaris 2.5.1 , sparc staion 5_10 ) I could successfully configure a LOCAL printer using lpadmin -p XX -v /dev/term/a But when I tried to do local printer configuration with admintool, ( as root user ) it throws up error. " add printer failed ". Also when I... (4 Replies)
Discussion started by: shibz
4 Replies

6. Solaris

Admintool and rpc call

Hi all, I'm trying to launch admintool via an export DISPLAY. i get the message: Received communication service error 4: Remote procedure call timed out: program = 100087, version = 10 Just to say, i don't use nis/nisplus on my server... What to do? Thanx Jason (17 Replies)
Discussion started by: penguin-friend
17 Replies

7. Solaris

what happened to admintool?

what happened to admintool in Solaris10? (2 Replies)
Discussion started by: mndavies
2 Replies

8. Solaris

Admintool

How can I solve this admintool Error: Can't open display: (4 Replies)
Discussion started by: iwbasts
4 Replies

9. UNIX for Advanced & Expert Users

Does admintool write to eeprom?

Hi: I was setting up a modem on an Ultra5 running 2.6. (yes I know, how quaint) There are 15 systems that are interlinked but not accessible to the outside world. This will end soon with new updated sun systems but until then the system needs to be accessed by the outside world. Hence the... (1 Reply)
Discussion started by: mndavies
1 Replies

10. Solaris

HP Printer without SMC, Admintool, or Jetadmin

Jetadmin fails saying that it is not a network printer despite the fact that it is and can be pinged from UNIX. I am administering this remotely (long remote, I can't go there soon) and can't run smc or admintool. Any help configuring this spooler would be appreciated. (1 Reply)
Discussion started by: TT Fan
1 Replies
EXPIRE(8)						    InterNetNews Documentation							 EXPIRE(8)

NAME
expire - Usenet article and history expiration program SYNOPSIS
expire [-iNnptx] [-d dir] [-f file] [-g file] [-h file] [-r reason] [-s size] [-v level] [-w number] [-z file] [expire.ctl] DESCRIPTION
expire scans the history(5)-format text file pathdb/history and uses the information recorded in it to purge itself of old news articles. Articles stored using a storage method that has self-expire functionality are by default not affected by expire's primary behavior (but see the -N flag to disable this). In this case, expire.ctl is ignored except the "/remember/" line for that article; expire does still probe to see if the article still exists and purges the relevant history and overview entries if appropriate. However, if groupbaseexpiry in inn.conf is true, expire acts on all articles as specified by expire.ctl regardless of whether their storage methods have self-expire functionality. Note that expire never purges articles which do not match any entry in expire.ctl. OPTIONS
-d dir If the -d flag is used, then the new history file and database is created in the specified directory dir. This is useful when the filesystem does not have sufficient space to hold both the old and new history files. When this flag is used, expire leaves the server paused and creates a zero-length file named after the new history file, with an extension of ".done" to indicate that it has successfully completed the expiration. The calling script should install the new history file and unpause the server. The -r flag should be used with this flag. -f file To specify an alternate history file, use the -f flag. This flag is valid when used with the -d flag, and the output will be written to the specified file. The default without -f is "history". -g file If the -g flag is given, then a one-line summary equivalent to the output of -v 1, except preceded by the current time, will be appended to the specified file. -h file To specify an alternate input text history file, use the -h flag. expire uses the old dbz(3) database to determine the size of the new one. (If the -d flag is not used, the output filename will be the same as the input filename with an extension of ".n".) The default without the -h flag is pathdb/history. -i To ignore the old database, use the -i flag. -N The control file is normally ignored for articles in storage methods which have self-expire functionality. If the -N flag is used, expire still uses the control file for these articles. -n If innd is not running, use the -n flag and expire will not send the "pause" or "go" commands. (For more details on the commands, see ctlinnd(8)). Note that expire only needs exclusive access for a very short time -- long enough to see if any new articles arrived since it first hit the end of the file, and to rename the new files to the working files. -p expire makes its decisions on the time the article arrived, as found in the history file. This means articles are often kept a little longer than with other expiration programs that base their decisions on the article's posting date. To use the article's posting date, use the -p flag. -r reason expire normally sends a "pause" command to the local innd daemon when it needs exclusive access to the history file, using the string "Expiring" as the reason. To give a different reason, use the -r flag. The process ID will be appended to the reason. When expire is finished and the new history file is ready, it sends a "go" command. See also the -n flag. -s size Optimize the new history database for approximately size pairs (lines in history). Accurately specifying the size will create a more efficient database. (The size should be the estimated eventual size of the file, typically the size of the old file.) -t If the -t flag is used, then expire will generate a list of the tokens that should be removed on its standard output, and the new history file will be left in history.n, history.n.dir, history.n.index and history.n.hash. This flag is useful for debugging when used with the -n flag. Note that if the -f flag is used, then the name specified with that flag will be used instead of history. -v level The -v flag is used to increase the verbosity of the program, generating messages to standard output. The level should be a number, where higher numbers result in more output. Level one will print totals of the various actions done (not valid if a new history file is not written), level two will print a report on each individual file, while level five results in multiple lines of output for every history line processed. -w number Use the -w flag to "warp" time so that expire thinks it is running at some time other then the current time. The value should be a signed floating point number indicating the number of days to use as the offset. -x If the -x flag is used, then expire will not create any new history files. This is most useful when combined with the -n and -t flags to see how different expiration policies would change the amount of disk space used. -z file If the -z flag is used, then articles are not removed, but their names are appended to the specified file. See the description of delayrm in news.daily(8). If a filename is specified, it is taken as the control file and parsed according to the rules in expire.ctl. A single dash ("-") may be used to read the file from standard input. If no file is specified, the file pathetc/expire.ctl is read. HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. Converted to POD by Julien Elie. $Id: expire.pod 8577 2009-08-18 14:02:02Z iulius $ SEE ALSO
ctlinnd(8), dbz(3), expire.ctl(5), history(5), inn.conf(5), innd(8), inndcomm(3), news.daily(8). INN 2.5.2 2009-09-11 EXPIRE(8)
All times are GMT -4. The time now is 04:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy