03-03-2016
Threads disappeared
Dear admins,
it seems that some threads or even users have recently (~ 2 days or so) disappeared. Examples: giuliangiuseppe and greycells. The latter asked me for the solution I provided earlier this week.
What happened? Can you help?
Regards
Rüdiger
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I just inst freeBSD boot installation and it didnt work for(probably my lack of knowledge) reasons but i now have to partitions in freeBSD and i really need them back for windows at the moment. i just cant find them. The bad thing is that i only got this bundled version of windows so i cant really... (2 Replies)
Discussion started by: riwa
2 Replies
2. UNIX for Dummies Questions & Answers
when i am doing the crontab editing i am using the setenv EDITOR /usr/bin/vi
but their was an error i tried to put set EDITOR /usr/bin/vi and it wnet through and i started editing using the command crontab -e but somehow it is slow and displayed something like e300 and i tried to stop because it... (3 Replies)
Discussion started by: afuella
3 Replies
3. UNIX for Advanced & Expert Users
Hi all,
How can I get the list of all Threads and the Total count of threads under a particular process ?
Do suggest !!
Awaiting for the replies !!
Thanks
Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies
4. Solaris
Hi all
I have a really strange situation. This morning I ran lpstat -p and it didn't return any results. I ran lpstat -t and the scheduler is running.
How strange, it seems all the printers have disappeared from my server.
Can anyone perhaps explain to me how this is possible? (4 Replies)
Discussion started by: soliberus
4 Replies
5. UNIX Desktop Questions & Answers
I'm doing an assignment for a Unix course at school.
I attempted to rename one of the shell programming questions from home to Q1 by typing:
mv home Q1
It returned a message saying
mv: cannot access home
And now there's no home or Q1 in the directory. Please help! (8 Replies)
Discussion started by: slogged
8 Replies
6. Solaris
Hello all I was configuring a SUN 2540 raid and after a reboot the hba`s is gone.
There is no longer an entry in etc/path_to_inst for them (2 cards).
I tried a reconfigure boot several times but it does not work.
The hba`s is a SUN qlogic 2200 in x4240 server (AMD).
Using solaris 10 update7.... (6 Replies)
Discussion started by: vettec3
6 Replies
7. Solaris
Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out.
exit
rebootxscf
logout
#.
#>
#>
~#
~#
exit
sendbreak
exit
I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies
8. Solaris
Can't find the data in either pool.
bash-3.00# zoneadm -z PPSMzone1 move /zpool/ppsmzone1
cannot create ZFS dataset zpool/ppsmzone1: dataset already exists
Moving across file-systems; copying zonepath /rpool/PPSMzone1...
Cleaning up zonepath /rpool/PPSMzone1...
bash-3.00# zonecfg -z... (1 Reply)
Discussion started by: LittleLebowski
1 Replies
9. Solaris
System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD.
I have been experimenting on the above system, using ldmp2v to create "clones" of my physical systems as LDoms on the server when there was an unscheduled power outage. After the system came back up I had lost my LDoms, although... (7 Replies)
Discussion started by: apmcd47
7 Replies
10. Solaris
I have a problem where I installed several OSes as partitions on one disk. And suddenly I cannot see Solaris 11.3 in the bios boot screen anymore. I have no clue why. Do anyone have a suggestion so I can dig further somewhere?
I first installed Solaris 11.3. Then Windows10 (gaming). Then Linux... (3 Replies)
Discussion started by: kebabbert
3 Replies
LEARN ABOUT DEBIAN
time.conf
TIME.CONF(5) Linux-PAM Manual TIME.CONF(5)
NAME
time.conf - configuration file for the pam_time module
DESCRIPTION
The pam_time PAM module does not authenticate the user, but instead it restricts access to a system and or specific applications at various
times of the day and on specific days or over various terminal lines. This module can be configured to deny access to (individual) users
based on their name, the time of day, the day of week, the service they are applying for and their terminal from which they are making
their request.
For this module to function correctly there must be a correctly formatted /etc/security/time.conf file present. White spaces are ignored
and lines maybe extended with '' (escaped newlines). Text following a '#' is ignored to the end of the line.
The syntax of the lines is as follows:
services;ttys;users;times
In words, each rule occupies a line, terminated with a newline or the beginning of a comment; a '#'. It contains four fields separated with
semicolons, ';'.
The first field, the services field, is a logic list of PAM service names that the rule applies to.
The second field, the tty field, is a logic list of terminal names that this rule applies to.
The third field, the users field, is a logic list of users or a netgroup of users to whom this rule applies.
For these items the simple wildcard '*' may be used only once. With netgroups no wildcards or logic operators are allowed.
The times field is used to indicate the times at which this rule applies. The format here is a logic list of day/time-range entries. The
days are specified by a sequence of two character entries, MoTuSa for example is Monday Tuesday and Saturday. Note that repeated days are
unset MoMo = no day, and MoWk = all weekdays bar Monday. The two character combinations accepted are Mo Tu We Th Fr Sa Su Wk Wd Al, the
last two being week-end days and all 7 days of the week respectively. As a final example, AlFr means all days except Friday.
Each day/time-range can be prefixed with a '!' to indicate "anything but". The time-range part is two 24-hour times HHMM, separated by a
hyphen, indicating the start and finish time (if the finish time is smaller than the start time it is deemed to apply on the following
day).
For a rule to be active, ALL of service+ttys+users must be satisfied by the applying process.
Note, currently there is no daemon enforcing the end of a session. This needs to be remedied.
Poorly formatted rules are logged as errors using syslog(3).
EXAMPLES
These are some example lines which might be specified in /etc/security/time.conf.
All users except for root are denied access to console-login at all times:
login ; tty* & !ttyp* ; !root ; !Al0000-2400
Games (configured to use PAM) are only to be accessed out of working hours. This rule does not apply to the user waster:
games ; * ; !waster ; Wd0000-2400 | Wk1800-0800
SEE ALSO
pam_time(8), pam.d(5), pam(7)
AUTHOR
pam_time was written by Andrew G. Morgan <morgan@kernel.org>.
Linux-PAM Manual 06/04/2011 TIME.CONF(5)