08-22-2013
You certainly have the cart before the horse! Usually an implementation is required before a standard (RFC) is agreed. And frankly I see no advantage(s) to your proposed design.
if you want people to take your proposal seriously, then you need to develop a reference implementation.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
I'm not sure if this is the right forum, but I would like to know if Redhat running NIS ( not NIS +) would have conflict with Solaris running NIS+. Currently I am running NIS+ on Solaris but will be adding RedHat to the network. I seem to be unable to find and information regarding... (2 Replies)
Discussion started by: larry
2 Replies
2. IP Networking
Hello together.
Is there someone who is able to explain me the differences between NIS and NIS+.
thanks in advance
joerg (2 Replies)
Discussion started by: joerg
2 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I just took over the admin role from someone and I wanna setup sendmail (just to send mail from the host) however, after I config all the resolv.conf, nssitch.conf, hosts file and when I try to send a mail out, after I punched ctl-D, it returned he following,
"NIS map mail.aliases... (2 Replies)
Discussion started by: stancwong
2 Replies
4. UNIX for Advanced & Expert Users
We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave.
We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation.
However, no matter what i do, the SUSE machines will not talk to the NIS Servers.
If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies
5. Solaris
Hi Guys,
I have lots of doubts regarding NIS+.I also think by basics could be wrong......I am trying to pick up stuff from documents which are a bit murky. I am working on production environment so I am afraid of trial and error! Please help.
1) What is the difference between root domain master... (1 Reply)
Discussion started by: nitinkgoud
1 Replies
6. Solaris
Hi, all.
I have a Solaris client here needs to bind to NIS server in another subnet. Following is the configuration i made on the client,
1) edit /etc/inet/hosts to add an entry of the NIS server -- nserver01
2) execute `domainname` to set local NIS domain to the domain of the NIS server.... (1 Reply)
Discussion started by: sn_wukong
1 Replies
7. Shell Programming and Scripting
I'm creating a scrip for auditing our AIX box's to ensure that they are built according to our system standards. I'm not sure on the logic for checking to see if the NIS and NIS+ services are disabled. any idea's? (2 Replies)
Discussion started by: sport
2 Replies
8. Solaris
how to see the all nis user details and individual user details ? (0 Replies)
Discussion started by: tirupathi
0 Replies
9. Linux
Hi All,
I have configured NIS server in linux rhel5 and made one client member to that server.
nfs share created for users home directory
i have created one nis user, user not able to change the passwd of his login.
getting below mentioned error
" yppasswdd not running on NIS master... (1 Reply)
Discussion started by: vinay_ks
1 Replies
10. UNIX for Advanced & Expert Users
Last year I posted I had written some new internet drafts designed to replace NIS and which would be the next evolution of RFC2307 (a standard describing how to represent NIS data in LDAP).
DBIS is now a reality. I have just completed a fully working reference implementation, and I would... (0 Replies)
Discussion started by: cambridge
0 Replies
LEARN ABOUT XFREE86
sd-readahead
SD-READAHEAD(7) sd-readahead SD-READAHEAD(7)
NAME
sd-readahead - Reference implementation of APIs for controlling boot-time read-ahead
SYNOPSIS
#include "sd-readahead.h"
DESCRIPTION
sd-readahead.c and sd-readahead.h provide a reference implementation for APIs for controlling boot-time read-ahead, as implemented by the
read-ahead subsystem of the systemd(1) init system.
See sd_readahead(3) for more information about the function implemented.
NOTES
This interface is provided by the reference implementation of APIs for controlling boot-time read-ahead and distributed with the systemd
package. The algorithms it implements are simple, and can easily be reimplemented in daemons if it is important to support this interface
without using the reference implementation. See the respective function man pages for details.
In addition, for details about the algorithms check the liberally licensed reference implementation sources:
http://cgit.freedesktop.org/systemd/systemd/plain/src/readahead/sd-readahead.c resp.
http://cgit.freedesktop.org/systemd/systemd/plain/src/systemd/sd-readahead.h
These APIs are implemented in the reference implementation's drop-in sd-readahead.c and sd-readahead.h files. It is recommended that
applications consuming these APIs copy the implementation into their source tree, either verbatim or in excerpts. These interfaces are
currently not available in a dynamic library.
The functions provided by this interface become NOPs when -DDISABLE_SYSTEMD is set during compilation. In addition, if sd-readhead.c is
compiled on non-Linux systems it becomes NOPs.
SEE ALSO
systemd(1), sd_readahead(3), sd-daemon(7)
AUTHOR
Lennart Poettering <lennart@poettering.net>
Developer
systemd 03/16/2012 SD-READAHEAD(7)