10 More Discussions You Might Find Interesting
1. Programming
I saw a header (.h) file with mixture of "regular" function declarations and other extern function declarations. As I was told all function declarations are implicitly external and the extern on functions declarations is superfluous. Here my focus is on function declaration, not variable yet.
int... (2 Replies)
Discussion started by: yifangt
2 Replies
2. Programming
In the header file data.h i got:
const char ack_msg = "ack: received your msg\n";
In the code file server.c i got:
extern const char ack_msg;
And else it is only used in a function call:
user$ grep ack_msg *c *h
server.c:extern const char ack_msg;
server.c: n = write(clientsfd,... (5 Replies)
Discussion started by: tornow
5 Replies
3. Ubuntu
Hi,
I am new to linux stuff. I want to use linux iptables to configure rule so that all my incoming traffic with protocol "tcp" is forwarded to the "FORWARD CHAIN". The traffic i am dealing with has destination addresss of my machine but i want to block it from coming to input chain and somehow... (0 Replies)
Discussion started by: arsipk
0 Replies
4. Programming
Why this is happening when both of them compiled together and run?
I am getting segmentation fault SIGSEGV.
File1.c:
int arr;
File2.c:
extern int *arr;
int main() {
arr = 100;
} (3 Replies)
Discussion started by: royalibrahim
3 Replies
5. Linux
Hello there Unix & Linux Guru's and Gifted ones,
Can anyone help me configure fetchmail on my redhat 9.0
This sounds to be silly but really I'm new to linux.
I really need step by step installation and configuration on our company's required Redhat 9.0 (shrike) OS.
Thank you and God... (2 Replies)
Discussion started by: struggled_boy
2 Replies
6. UNIX for Dummies Questions & Answers
Hi there,
I receive job applications sent by a website daemon. The email subject contains the job offer description. The problem is that gmail tends to concatenate emails with the same subject and I don't really want all applications in the same email. Thus the from field contains the candidate... (0 Replies)
Discussion started by: chebarbudo
0 Replies
7. Linux
Hi there, I'm having a bit of a strange problem which I would appreciate some help with.
The Problem:
I have two external hard drives, but I'm borrowing one off my parents to copy data too (one of mine, which is identical to theirs - WD MyBook 300g - is on its way out).
Fedora 9 recognizes... (3 Replies)
Discussion started by: lasthidingplace
3 Replies
8. Programming
file1.c
int a1;
int main()
{
a1 = 2;
printf("\na1 = %d\n", a1);
next();
printf("\na1 = %d\n", a1);
next1();
printf("\na1 = %d\n", a1);
}
file2.c
#include <stdio.h>
int b1 = 0;
void next(void) (1 Reply)
Discussion started by: Tanvirk
1 Replies
9. Programming
Hi,
Please let me know if the extern keyword is necessary for using functions which is defined and declared in another file and and used in a different file where both these files are linked together.
thanks (8 Replies)
Discussion started by: naan
8 Replies
10. UNIX for Dummies Questions & Answers
Hi peeps,
We are having around 60 users.
The time set to retrieve the mail is 300 sec.
But it's taking around 1 hour to deliver mails.
I am using debian sarge 3.1.
any clues?
And how it will affect if I decrease the time?
My machine has got 1 p4 3.0 GHZ processor and 1 GB ram.
The home... (2 Replies)
Discussion started by: squid04
2 Replies
MAILCHECK(1) General Commands Manual MAILCHECK(1)
NAME
mailcheck - Check multiple mailboxes and/or Maildirs for new mail
SYNOPSIS
mailcheck [-lbcsh] [-f rcfile]
DESCRIPTION
mailcheck is a simple, configurable tool that allows multiple mailboxes to be checked for the existence of mail. For local mail, it sup-
ports both the traditional mbox format and the newer Maildir format. Mail can also be checked for on remote servers using either the POP3
or IMAP protocol.
Typically, one would invoke mailcheck in /etc/profile or a user-specific login script. E-mail junkies may also find it useful to invoke
mailcheck occasionally to check for new mail in alternate mailboxes.
The author uses mailcheck to keep track of messages arriving in mailboxes corresponding to several mailing lists he subscribes to.
OPTIONS
-l Runs mailcheck in login mode. If a ~/.hushlogin file exists, mailcheck will exit silently. This option is intended to be used on
systems that invoke mailcheck from a global login script such as /etc/profile.
-b Brief mode. Produces less verbose output. If mailbox or Maildir is inside user's home direcory, only relative path is printed to
output.
-c Use more advanced counting method. While counting mails, mailcheck looks inside mboxes and Maildirs and count new and unread mes-
sages separately. If mbox/maildir does not contain any new or unread mail, it's excluded from report. Produced output contains
more valuable information, but this method is more time-consuming.
-s Print "no mail" summary. If no new mail message is found, print at least "no mail message" at the end. Only makes sense in combi-
nation with -c.
-f Specify alternative rc file location. If provided, default locations (see FILES) are not checked.
-h Print short usage information.
CONFIGURATION
Configuring mailcheck is simple. Upon startup, mailcheck looks for a file called .mailcheckrc in the user's home directory. If that file
does not exist, the default configuration file /etc/mailcheckrc is used instead.
Lines beginning with a hash sign (#) are treated as comments and will not be processed. Lines beginning with pop3: or imap: are parsed
like URLs and used to connect to network mail servers. All other lines are treated as pathnames to mailbox files or Maildir directories.
Environment variables in the format $(NAME) will be expanded inline. For example:
/var/spool/mail/$(USER)
Will check the user's mailbox in /var/spool/mail.
$(HOME)/Mailbox
Will check the default mailbox used by qmail installations.
When connecting to POP3 or IMAP servers, the account password is not stored in the mailcheckrc file. Instead, the .netrc file in the
user's home directory is used. This file, originally intended for use with ftp(1) and later used by fetchmail(1), should be readable only
by the user owning it. It stores server/user/password combinations in the form:
machine servername login username password password
FILES
/etc/mailcheckrc
This is the site-default mailcheck configuration file. It should be edited by the system administrator to meet the needs of most
users on the system.
~/.mailcheckrc
This is the user-specific mailcheck configuration file. If it exists for a particular user, the site-default configuration file
will not be used.
~/.netrc
This tells mailcheck what password to use for a given server/user combination when checking POP3 or IMAP mail.
COPYRIGHT
Copyright (C) 1996, 1997, 1998, 2001, Jefferson E. Noxon.
Portions Copyright (C) 1996, Free Software Foundation, Inc.
Portions Copyright (C) 1996, Gordon Matzigkeit.
Portions Copyright (C) 1998, Trent Piepho.
Other copyrights may apply.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
On Debian GNU/Linux see /usr/share/common-licenses/GPL
AUTHOR
Mailcheck was written for Debian GNU/Linux by Jefferson E. Noxon <jeff@planetfall.com>.
ACKNOWLEDGEMENTS
POP3 and IMAP support was added by Rob Funk <rfunk@funknet.net>.
Several enhancements by Tomas Hoger <thoger@pobox.sk>.
BUGS
It is probably not a good idea to store passwords in a .netrc file.
No SSL/TLS support for POP3 and IMAP.
SEE ALSO
netrc(5), mbox(5), maildir(5), login(1), fetchmail(1)
2 July 2005 MAILCHECK(1)