redhat-list Digest, Vol 53, Issue 3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,


will u please tell me how to configure samba pdc with ldap please reply

Thanks in advance
Ankit Jariwala
call:-91-9725655020
India

On 7/4/08, redhat-list-request@xxxxxxxxxx
<redhat-list-request@xxxxxxxxxx> wrote:
> Send redhat-list mailing list submissions to
> 	redhat-list@xxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.redhat.com/mailman/listinfo/redhat-list
> or, via email, send a message with subject or body 'help' to
> 	redhat-list-request@xxxxxxxxxx
>
> You can reach the person managing the list at
> 	redhat-list-owner@xxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of redhat-list digest..."
>
>
> Today's Topics:
>
>    1. RHEL5 Desktop Nautilus config question (John H. Nyhuis)
>    2. utmp and wtmp (Paula J. Lindsay)
>    3. Re: utmp and wtmp (chaim.rieger@xxxxxxxxx)
>    4. Re: utmp and wtmp (George Magklaras)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 3 Jul 2008 10:18:29 -0700 (PDT)
> From: "John H. Nyhuis" <cabal@xxxxxxxxxxxxxxxx>
> Subject: RHEL5 Desktop Nautilus config question
> To: redhat-list@xxxxxxxxxx
> Message-ID:
> 	<Pine.LNX.4.64.0807031015300.13844@xxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
>  	Greetings,
>
>  	I am trying out the RHEL's Desktop 5 package, and have discovered an
> annoying problem with Nautilus.  The 'type to browse' feature times out and
> resets about every second, making it nearly impossible to enter a full
> address.
>  	Does anyone know how to reset this timeout to something reasonable, or
> make the address bar a static display that stays put?  Thus far I have not
> found the solution.
>
>  	Thanks,
>
> John H. Nyhuis
> IT Manager
> Dept. of Pediatrics
> HS RR541C, Box 356320
> University of Washington
> Desk: (206)-685-3884
> jnyhuis@xxxxxxxxxxxxxxxx
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 03 Jul 2008 11:23:45 -0700
> From: "Paula J. Lindsay" <paula@xxxxxxxxxxx>
> Subject: utmp and wtmp
> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx>
> Message-ID: <486D1931.80106@xxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi everyone,
> I have a scientist that runs an instrument in her lab.  She uses utmp
> and logrotate to rotate the wtmp file and then
> at the beginning of the month, she records everyone's logging in and out
> usage on her RHE 5 machine so she
> can charge them for the use of the instrument.  Sometimes students and
> other doctor's run experiments all night.
> Well, I have her RHE 5 machine rotating every month at the beginning of
> the month, it does this at midnight.
> The problem is that whoever is logged in at that  time is dropped and
> the utmp doesn't continue to record his/her
> time on the machine.  They could be on there for another 5 hours, but it
> doesn't pick up that user again.  Is there
> any way to make the utmp pick up that user or continue recording that
> user when the logs are processing again?
> I know this is somewhat of an irritating quirk, but it is important to
> her to find out when the person logs back out
> so she doesn't charge him too much or too little.  Any
> help/advice/suggestions would be greatly appreciated.  Many
> thanks in advance.
> Paula
>
> --
> Paula J. Lindsay
> IT Analyst III
> IT Services
> 10550 North Torrey Pines Road
> La Jolla, CA  92037
> 858.784.9378 (office)
> 858.784.9301 (fax)
> paula@xxxxxxxxxxx
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 3 Jul 2008 18:35:50 +0000
> From: chaim.rieger@xxxxxxxxx
> Subject: Re: utmp and wtmp
> To: "General Red Hat Linux discussion list" <redhat-list@xxxxxxxxxx>
> Message-ID:
> 	<2081169125-1215110171-cardhu_decombobulator_blackberry.rim.net-1714623295-@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> 	
> Content-Type: text/plain
>
> Did you look at the security logs
>
> I believe that logs in and out as well if ssh is setup to do so
>
>
> Sent via BlackBerry from T-Mobile
>
> -----Original Message-----
> From: "Paula J. Lindsay" <paula@xxxxxxxxxxx>
>
> Date: Thu, 03 Jul 2008 11:23:45
> To: General Red Hat Linux discussion list<redhat-list@xxxxxxxxxx>
> Subject: utmp and wtmp
>
>
> Hi everyone,
> I have a scientist that runs an instrument in her lab.  She uses utmp
> and logrotate to rotate the wtmp file and then
> at the beginning of the month, she records everyone's logging in and out
> usage on her RHE 5 machine so she
> can charge them for the use of the instrument.  Sometimes students and
> other doctor's run experiments all night.
> Well, I have her RHE 5 machine rotating every month at the beginning of
> the month, it does this at midnight.
> The problem is that whoever is logged in at that  time is dropped and
> the utmp doesn't continue to record his/her
> time on the machine.  They could be on there for another 5 hours, but it
> doesn't pick up that user again.  Is there
> any way to make the utmp pick up that user or continue recording that
> user when the logs are processing again?
> I know this is somewhat of an irritating quirk, but it is important to
> her to find out when the person logs back out
> so she doesn't charge him too much or too little.  Any
> help/advice/suggestions would be greatly appreciated.  Many
> thanks in advance.
> Paula
>
> --
> Paula J. Lindsay
> IT Analyst III
> IT Services
> 10550 North Torrey Pines Road
> La Jolla, CA  92037
> 858.784.9378 (office)
> 858.784.9301 (fax)
> paula@xxxxxxxxxxx
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 04 Jul 2008 13:11:43 +0200
> From: George Magklaras <georgios@xxxxxxxxxxxxx>
> Subject: Re: utmp and wtmp
> To: General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx>
> Message-ID: <486E056F.4010502@xxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> The best thing in that case would be to increase the logrotate interval
> for wtmp from a monthly to yearly basis. Somewhere under /etc you should
> have an /etc/logrotate.conf file. Normally, a default entry for wtmp
> would be:
>
> # no packages own wtmp -- we'll rotate them here
> /var/log/wtmp {
>      monthly
>      minsize 1M
>      create 0664 root utmp
>      rotate 1
> }
>
> In plain English, this means "rotate the file once per month with
> priority the timestamp and not the minimum size at 1 Meg". If you
> replace the line "monthly" bit with "yearly" and take the minsize
> parameter out, it should do the job.
>
> After that, do a: logrotate -dv /etc/logrotate.conf and verify what the
> logrotate tool is planning to do with the new parameters. It should
> verify the yearly rotation for wtmp.
>
> Warning: Depending on how busy the system is not only wtmp/utmp log wise
> but from other logs, I normally partition /var separarely to make sure I
> have plenty of space. If you have /var under root, watch out for the
> size of the log(s).
>
> GM
>
> --
> --
> George Magklaras
>
> Senior Computer Systems Engineer/UNIX Systems Administrator
> EMBnet Technical Management Board
> The Biotechnology Centre of Oslo,
> University of Oslo
> http://folk.uio.no/georgios
>
>
>
> Paula J. Lindsay wrote:
>> Hi everyone,
>> I have a scientist that runs an instrument in her lab.  She uses utmp
>> and logrotate to rotate the wtmp file and then
>> at the beginning of the month, she records everyone's logging in and out
>> usage on her RHE 5 machine so she
>> can charge them for the use of the instrument.  Sometimes students and
>> other doctor's run experiments all night.
>> Well, I have her RHE 5 machine rotating every month at the beginning of
>> the month, it does this at midnight.
>> The problem is that whoever is logged in at that  time is dropped and
>> the utmp doesn't continue to record his/her
>> time on the machine.  They could be on there for another 5 hours, but it
>> doesn't pick up that user again.  Is there
>> any way to make the utmp pick up that user or continue recording that
>> user when the logs are processing again?
>> I know this is somewhat of an irritating quirk, but it is important to
>> her to find out when the person logs back out
>> so she doesn't charge him too much or too little.  Any
>> help/advice/suggestions would be greatly appreciated.  Many
>> thanks in advance.
>> Paula
>>
>
>
>
>
>
> ------------------------------
>
> __
> redhat-list mailing list
> Unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
> End of redhat-list Digest, Vol 53, Issue 3
> ******************************************
>

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux