rescan of sata channels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, is there a way to detach and attach a device on a sata channel in FreeBSD 9 on FreeBSD 8 I used atacontrol detach to detach a sata HD bevor removing it from a hotswap bay and atacontroll attach to rescan the channel after inserting a new Harddrive in die Bay. In camcontroll there is no such command. an rescan or reinit doesn't reveal the new hdd. Is there a way to force the sata channel to rescan an detect the Harddisk without reboot. Regards Estartu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (FreeBSD) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQCVAwUBUMb3KAzx22nOTJQRAQJhygP/c4VUBQTpTko66ZuNuV06tryPf5T9gxIE j0ViE9hzzjcuazo0tBlqwO/RGNIn5z0K8JWYj9SLWLdLBLI5fsk98Q3ApUvdr0bA 4/rq53wxvehJeqTfqywTs6ECIrpnHE0R49PKkf1CqNkHBntEtUDQXvfmBT0gh2vV wRZbky9sa9U= =xxsH -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ata controller problem
Am 26.10.2012 18:33, schrieb Jeremy Chadwick: Regarding this: http://lists.freebsd.org/pipermail/freebsd-questions/2012-October/245862.html No no NO *NO*! I wish people would stop recommending this utter garbage. There is absolutely no justification behind using the highly convoluted labelling mechanisms at multiple layers within FreeBSD. There are 3 (possibly 4) different label mechanisms which do nothing but confuse the user, or cause other oddities/complexities. Good grief, there is so much hard evidence on the mailing lists over the past 5 (maybe even 7?) years talking about the utter mess that is filesystem/device/geom/blahblah labels that to recommend this is borderline insane. The proper way to solve this problem is to user /boot/loader.conf tie-downs to assign each disk to each individual controllers' device number (e.g. ada0 -- scbus0 -- ahcich0, or whatever you want). Please note I said ahcichX, not ahciX. Different things. I have helped others in the past do this; Randy Bush is one such person. Taken directly from my /boot/loader.conf with a single SATA controller, but obviously this can be adjusted to whatever you want. # Wire down device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at=ahcich0 hint.scbus.1.at=ahcich1 hint.scbus.2.at=ahcich2 hint.scbus.3.at=ahcich3 hint.scbus.4.at=ahcich4 hint.scbus.5.at=ahcich5 hint.ada.0.at=scbus0 hint.ada.1.at=scbus1 hint.ada.2.at=scbus2 hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. Sorry this doesn't work because the numbering of the ahci change with the occupancy of the Hot-Swap Bays. And that is my Problem. This i have tried first. Any idea how i can fix which controller gets which number. Regard Estartu -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ata controller problem
On 26.10.2012 18:00, Polytropon wrote: On Fri, 26 Oct 2012 14:18:16 +0200, Gerhard Schmidt wrote: The Problem is that, if there is a Drive in one of the HotSwap Bays the PCI-Express controller is detected as ahci0 and the onboard is detected as ahci1. Therefore any drives in the HotSwap Bays become ada0-3 and the drives on the mainboard controller are the upper numbers which causes the boot to fail as the Root Partition isn't there where it's expected. The BIOS has the PCI-Express Card as second Card only so the Kernel is Booted but the RootFS is not Found. You can use labels (GPT or UFS labels) or UFSIDs to become independent of the actual device name where things are stored on. You could also use this to make disks easier to identify (e. g. /dev/label/red1root = the disk with a red 1 on it, carrying the root file system). I suggest those pages for more detailed information: http://www.wonkity.com/~wblock/docs/html/disksetup.html http://www.freebsd.org/doc/handbook/geom-glabel.html Maybe as well (specific and general notes and inspiration): http://www.daemonforums.org/showthread.php?t=2666 http://www.freebsdonline.com/content/view/731/506/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html I assume that you are using UFS. Is there a way to ensure that the onboard SATA Controller is always probed first. I'm not sure if this can be done, but using labels should make the question go away, and the problem causing it. :-) Labels are good for naming Drives but how does it help me if the root filesystem changing device ids. I don't think the boot loader is able to use the label for the root Filesystem. Regards Estartu -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ata controller problem
Am 27.10.2012 10:39, schrieb Erich Dollansky: Hi, On Sat, 27 Oct 2012 10:22:01 +0200 Gerhard Schmidt schm...@ze.tum.de wrote: hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 See CAM(4) man page (read it, don't skim!) for full details. Just please for the love of god do not use labels to solve this. Sorry this doesn't work because the numbering of the ahci change with the occupancy of the Hot-Swap Bays. And that is my Problem. This i have tried first. Any idea how i can fix which controller gets which number. just you labels. Chose the labelling method which fits best your file system. gpt seems to fit most scenarios. Labels came up to solve your problem. Can I mount the root filesystem via label. That's the problem here. Regard Estartu -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage signature.asc Description: OpenPGP digital signature
ata controller problem
Hi, i have a very strange Problem with my new Workstation. The Problem is the order of the sata controllers. The Mainboard has 6 sata Ports and i have a PCI-Express Card with 4 more sata Channels. I boot from a SSD connected to port 0 in the Mainboard. Channels 1-3 are additional Harddisks and 5 is a optical drive. I've a Hotswap-Bay for 3 SATA Drives the bay is connected to the PCI-Express Card SATA Channel. The Problem is that, if there is a Drive in one of the HotSwap Bays the PCI-Express controller is detected as ahci0 and the onboard is detected as ahci1. Therefore any drives in the HotSwap Bays become ada0-3 and the drives on the mainboard controller are the upper numbers which causes the boot to fail as the Root Partition isn't there where it's expected. The BIOS has the PCI-Express Card as second Card only so the Kernel is Booted but the RootFS is not Found. So Far i could have set some devices.hints entries to sort the scsi busses. But the problem is that if there are no drives in the Bays the PCI-Expresscard is detected as ahci1 Is there a way to ensure that the onboard SATA Controller is always probed first. Regards Gerhard -- - Gerhard Schmidt | E-Mail und JabberID: TU-München| schm...@ze.tum.de WWW Online Services | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
hardwire scsi busses
Hello list i'm setting up a FreeBSD system with two SCSI controller. One Ataptec (ahd) and a 3Ware Raid posing as SCSI Controller. The 3ware Raid is the Main Harddisk and on the ahd controll is an external scsi Raid that sometime isn't up. My Problem ist that the ahd ist scsibus0 and the twa is scsibus1. When I boot the system with the external raid aktiv the external raid (ahd) will be da0 and the internal raid (twa) will be da1 and the system doesn't boot becaus the bootdisks are on da1 on not on da0. How can I hardwire the ahd to become scsibus1 and the twa to become scsibus0, that regardless if the external raid is online the boot disk is allways da0 an the extern raid ist da1 if online. Regards Estartu -- --- Gerhard Schmidt| http://www.augusta.de/~estartu| Fischbachweg 3 | | PGP Public Key 86856 Hiltenfingen | JabberID: esta...@augusta.de | on request Germany| | signature.asc Description: OpenPGP digital signature
vinum raid degraded
Hi, I'm running a gvinum raid array with 4x80G drives. This raid is running for 4 Years now. Today i found out that the status in degraded. All drives are up but on subdisk is stale. How can get the raid out of degraded mode. I have attached the output of gvinum l Greeting Estartu -- - Gerhard Schmidt | E-Mail: schm...@ze.tum.de TU-München| WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage 4 drives: D vinumdrive3 State: up /dev/ad7A: 0/78533 MB (0%) D vinumdrive2 State: up /dev/ad6A: 0/78533 MB (0%) D vinumdrive1 State: up /dev/ad5s1 A: 0/78533 MB (0%) D vinumdrive0 State: up /dev/ad4A: 0/78533 MB (0%) 1 volume: V daten State: up Plexes: 1 Size:230 GB 1 plex: P daten.p0 R5 State: degraded Subdisks: 4 Size:230 GB 4 subdisks: S daten.p0.s3 State: up D: vinumdrive3 Size: 76 GB S daten.p0.s2 State: up D: vinumdrive2 Size: 76 GB S daten.p0.s1 State: staleD: vinumdrive1 Size: 76 GB S daten.p0.s0 State: up D: vinumdrive0 Size: 76 GB ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
files before ldap in nsswitch.conf
Hi, I'm setting up a new FreeBSD Server for out local Computer club. Most of the users are stored in LDAP and I've installed nss_ldap and pam_ldap and set up both. Everything works so far with nsswitch.conf entry passwd: ldap files. When I try passwd: files ldap the login doesn't work anymore because the LDAP_Server is never asked. I tried this to optimize the LDAP requests as the service users are in the local files. This would speed up the boot process and takes some load off the LDAP-Server. Is there a way to configure FreeBSD to look first in the local files and if a user isn't found in the LDAP-Server. And another question. Is there a way to use two different LDAP-Servers e.g. by calling nss_ldap with different config files. Greetings Estartu -- - Gerhard Schmidt | E-Mail: [EMAIL PROTECTED] TU-München| WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nss_ldap and openldap on the same server.
On Tue, Mar 13, 2007 at 12:07:15AM +0100, Pietro Cerutti wrote: On 3/12/07, Gerhard Schmidt [EMAIL PROTECTED] wrote: Hi, Hello, As I see it, nss asks all sources even if the frist one allready knows the answer. Is there a way to change this. man nsswitch.conf(5) Look for Status codes and Actions Doesn't work. Tried the follwing nsswitch.conf group: files [success=return] ldap hosts: files dns networks: files passwd: files [success=return] ldap shells: files This doesn't change the delay. And the nss_ldap timeout is still reported. This is not supprising because the manpage states [success=return] is default. Seams there is a bug somewhere. Bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpCnHmG5AcZf.pgp Description: PGP signature
Re: nss_ldap and openldap on the same server.
On Tue, Mar 13, 2007 at 07:58:05AM +0900, Daniel Marsh wrote: I've run into this very same problem... but the way I got around it was putting OpenLDAP in a jail all by its lonesome and making sure that jail would start before anything on the host system would start that may need LDAP... (effectively meaning the LDAP server is a different machine) Hitting the Problem with a really big hammer. Thats cures only the symptoms not the Problem. As i see it the Problem is that the status/actions in nsswitch.conf not working. Since man nsswitch.conf stats that success=return is default an therefore ldap should never be asked for Users that are in the /etc/passwd file. I will file a Problemreport for this one. Bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpZd5cyZ2vQO.pgp Description: PGP signature
Re: nss_ldap and openldap on the same server.
On Tue, Mar 13, 2007 at 10:01:09AM +0200, Jonathan McKeown wrote: On Tuesday 13 March 2007 09:16, Gerhard Schmidt wrote: On Tue, Mar 13, 2007 at 12:07:15AM +0100, Pietro Cerutti wrote: On 3/12/07, Gerhard Schmidt [EMAIL PROTECTED] wrote: Hi, Hello, As I see it, nss asks all sources even if the frist one allready knows the answer. Is there a way to change this. man nsswitch.conf(5) Look for Status codes and Actions Doesn't work. Tried the follwing nsswitch.conf group: files [success=return] ldap hosts: files dns networks: files passwd: files [success=return] ldap shells: files This doesn't change the delay. And the nss_ldap timeout is still reported. This is not supprising because the manpage states [success=return] is default. Seams there is a bug somewhere. It's a well-known problem rather than a bug, and it arises when looking up group information for a user. The system needs a list of all the groups the user is a member of. Since it's a list, not a single answer, you can't short-circuit the process with ``success'' after finding a single result: initgroups(3) must work through all possible sources of group information to build the list. I think its still a bug. You are right that all groups should be found so the default for groups should be success=continue to have this done. But when I explicily specify that on success the process should abort, it should be done exacly this way. The only ``workaround'' I've seen suggested is the parameter introduced recently in nss_ldap: nss_initgroups_ignoreusers It takes a comma-separated list of users for whom the nss_ldap initgroups routine should immediately return NSS_STATUS_NOTFOUND. If you keep group information for all the system users in /etc/group only, and add them all to this line in nss_ldap.conf, it should remove the problem. (Warning: I haven't tested this). This may fix the problem with nss_ldap but its still there with other modules. Bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpSRTSjZBJDk.pgp Description: PGP signature
Re: nss_ldap and openldap on the same server.
On Tue, Mar 13, 2007 at 09:08:34AM +0100, Joerg Pulz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 13 Mar 2007, Gerhard Schmidt wrote: On Tue, Mar 13, 2007 at 12:07:15AM +0100, Pietro Cerutti wrote: On 3/12/07, Gerhard Schmidt [EMAIL PROTECTED] wrote: Hi, Hello, As I see it, nss asks all sources even if the frist one allready knows the answer. Is there a way to change this. man nsswitch.conf(5) Look for Status codes and Actions Doesn't work. Tried the follwing nsswitch.conf group: files [success=return] ldap hosts: files dns networks: files passwd: files [success=return] ldap shells: files This doesn't change the delay. And the nss_ldap timeout is still reported. This is not supprising because the manpage states [success=return] is default. Seams there is a bug somewhere. AFAICT, there is no bug. The behavior is completely correct as a look into the openldap code turns out. When starting up slapd, it tries to switch the credentials to the user and group specified, normally ldap:ldap. Therefor it uses getpwuid(3), getpwnam(3), getgrgid(3) and getgrnam(3) functions. If lookup for the user and group specified is okay, it then calls getuid(3) and initgroups(3). Reading initgroups(3) turns out the following: The initgroups() function uses the getgrouplist(3) function to calculate the group access list for the user specified in name. Reading getgrouplist(3) turns out the following: The getgrouplist() function reads through the group file and calculates the group access list for the user specified in name. [...] The getgrouplist() function uses the routines based on getgrent(3). Reading getgrent(3) turns out the following: The getgrent() function sequentially reads the group database and is intended for programs that wish to step through the complete list of groups. [...] The getgrent() and getgrent_r() functions make no attempt to suppress duplicate information if multiple sources are specified in nsswitch.conf(5). So after following the way through all man pages, it turns out that the behavior is fully correct as a lookup is done to find out all groups to which the specified slapd user belongs to. This includes lookups using nss_ldap when ldap is configured as source for groups in nsswitch.conf. As a side note, a short look into the bind and cron source turns out that these, and probably others too, also use the initgroups(3) function. yes. But still there is something missing. The Admin should have controll over this behavior. The reasonable default action for groups should be success=continue to go though all group sources. But the admin should still have the posibility to stop the process on success which is not possible right now. Bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpPoqYTY6DQl.pgp Description: PGP signature
Re: nss_ldap and openldap on the same server.
On Tue, Mar 13, 2007 at 11:13:00AM +0200, Jonathan McKeown wrote: On Tuesday 13 March 2007 10:26, Gerhard Schmidt wrote: It's a well-known problem rather than a bug, and it arises when looking up group information for a user. The system needs a list of all the groups the user is a member of. Since it's a list, not a single answer, you can't short-circuit the process with ``success'' after finding a single result: initgroups(3) must work through all possible sources of group information to build the list. I think its still a bug. You are right that all groups should be found so the default for groups should be success=continue to have this done. But when I explicily specify that on success the process should abort, it should be done exacly this way. You've now had responses from me and Joerg Pulz, and given us essentially the same reply. I'm not sure success means what you think it means: group information is a complete list, not ``first item found'' like a user account. You have told the system to check for group information in files and ldap. You have, therefore, not succeeded in listing all groups until you have both searched the files *and* received a response from nss_ldap, either group information or NSS_STATUS_NOTFOUND. It looks as though you can instruct nss_ldap to unconditionally return NSS_STATUS_NOTFOUND for a user, by adding nss_initgroups_ignoreusers user in nss_ldap.conf. I'd be interested to hear whether it works, having not tested it myself, but at the moment you're banging your head against the wall and shouting about how much it hurts. It will hurt less if you stop. It's not. added nss_initgroups_ignoreusers ldap but it still blockes for 2 Min. I have found a solution that work for me. The problem is not that nsswitch asks nss_ldap but that nss_ldap take so long to realise the ldap isn't running. I have changed the bind_policy setting of nss_ldap from hard to soft and nss_ldap fails without delay. So it's working for me for now. But still there is a problem with that. Right now there is no way we could prevent any source from adding users to any group (e.g wheel). I think thats a security problem in envoriments where you don't have control over all sources used for authentication und usermanagement. If there was a way you could tell the nss to stop wenn a group definition is found in a module we had a way to stop this. That shouldn't be the default way but it schould be possible. Bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgp9i8MG1LO1C.pgp Description: PGP signature
nss_ldap and openldap on the same server.
Hi, I have a small problem. On my central server we run an openldap server that contains the userdata for some systems. An the server uses this ldap server for authentication and nss. The problem is that when the server is booting slapd takes a very long time to start up. I think it's trying to get an answer from ldap for the user ldap. But user ldap is in /etc/passwd and in /etc/groups My nsswitch.conf looks like this. group: files ldap hosts: files dns networks: files passwd: files ldap shells: files The system comes up but takes very long to do so (i think it's somekind of timeout) Mar 12 14:58:23 phobos slapd[584]: nss_ldap: could not search LDAP server - Server is unavailable As I see it, nss asks all sources even if the frist one allready knows the answer. Is there a way to change this. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpmmM9wgc5jS.pgp Description: PGP signature
Re: BSDstats Project v2.0 ...
On Mon, Aug 07, 2006 at 12:42:27AM -0300, Marc G. Fournier wrote: I've now committed v2.0 of the 300.statistics periodic script ... this one adds the device reporting that we'd talked about previously, and the summary reports now reflect the driver(s) in use for those deciding to report ... This Phase of the script is optional, and not enabled by default ... I can't think of any reason why you wouldn't want to report it, but just in case someone feels it poses a problem, its an opt-in report ... pkg-message updated to reflect the extra line you need to add to /etc/periodic.conf: monthly_statistics_report_devices=yes I've written it to report driver + chip= information from pciconf -l, since even pciconf -lv doesn't seem to use card= ... the summary report will be extended next to show both vendor and chip statistics ... Only out of curiosity. What kind of webserver have you. If only a part of the FreeBSD Users install your script and it got executed at the same time, this will get an awfull lot of load for your server. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpGFZhFEDFkK.pgp Description: PGP signature
Re: zope-3.2.0 and plone trouble
On Thu, Mar 23, 2006 at 09:34:28AM +0100, Michel Le Cocq wrote: Hi, I just install zope-3.2.0 and made it working just well. Now I wanted to run plone on it so i go to /usr/portswww/plone and type make install, and there, it install zope-2.7.8_1 and also python-2.3.5_1 (i already had python-2.4.2). My ports list is up to date. I can't make plone working in zope 3.2 but it work under zope 2.7 Zope 2 and Zope3 are two different Products. Zope3 is a complete new implemantation and is not backwars compartible with Zope2 software. Actual Plone runes an Zope up to 2.9 (I Think. I have tested it on Zope 2.8.2) Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpFYYiIEK8Kj.pgp Description: PGP signature
Re: No free space add after removing large file
On Tue, Aug 30, 2005 at 01:37:56PM +0200, Frank de Bot wrote: Hi, On my fs I had a file of 20gb. The free space on that fs was at that time around 1gb. But after removing the 20gb file, the freespace wasn't added :-S ? What has gone wrong and how can I 'reclaim' the free space? There could be a process which has an open filehandle to this file. The file isn't deleted until all filehandles are closed. Try to install /usr/ports/sysutils/lsof and look for the open handle. E.g. lsof | grep filename Kill the process and the freespace should grow. If this doesn't work or there is no open handle try do go to single user mode an force an fsck on this fielsystem. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgp4Hh1xxAMEU.pgp Description: PGP signature
Re: Mysql startup question
On Tue, May 24, 2005 at 04:02:45PM -0700, Philip Wege wrote: No problems there , and all files and folders owned by root. That's the problem /var/db/mysql should be owned by mysql:mysql because mysqld is started as user mysql. bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | Privat: [EMAIL PROTECTED] | auf Anfrage/ Germany||on Request pgprgWftQ8Phb.pgp Description: PGP signature
createing users homedir on first login
Hi, I have set up some FreeBSD 5 Workstations and configured nss to get the accounts from ldap. Pam is also set up to work with ldap. Everything so far is runningnperfectly smooth. The problem is the workstations don`t have a shared filesystem. Each user should have an seperate homedir on every workstation. I tried to use pam_exec to create the homedir on the first login. But it seams there is now way of knowing who is logging. I've even tried to use pw usershow -a to get all users and create all homedirs but pw usershow -a don't report any users when started from a shellscript called by the pam_exec module. Anyone successfully implemented a system to create homedirs on the fly. bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | E-Mail: [EMAIL PROTECTED] | auf Anfrage/ Germany||on request pgp7vWPDIuOPS.pgp Description: PGP signature
Re: Updated perl - broke stuff
On Sun, Feb 13, 2005 at 06:15:18PM -0800, Michael C. Shultz wrote: On Sunday 13 February 2005 02:02 pm, Paul Schmehl wrote: - Original Message - From: Ean Kingston [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Cc: Paul Schmehl [EMAIL PROTECTED] Sent: Sunday, February 13, 2005 3:42 PM Subject: Re: Updated perl - broke stuff I stopped using portupgrade because it only upgrades ports that are out-of date. It then modifies the installed software database to change any dependencies that relied on the old port to show them as relying on the new port. For most ports, this works. For Perl, particularly mod_perl, this doesn't work. If you install a new perl you have to rebuild everything that depends on perl even if it hasn't been updated. So I stopped using portupgrade. Wouldn't it make more sense to fix mod_perl? (Or portupgrade - whichever one is the culprit?) All the ports that depended upon perl appear to have had their dependencies updated properly except for libwww and mod_perl. ISTM, fixing those two ports makes more sense. If you don't use portupgrade, then what *do* you do? Wouldn't you have to deinstall and reinstall every port that depended upon perl? Or will pkgdb -F do the trick? Pkgdb -F is what screws up the installed ports registry. Here is an example of what happens: 1. port-A needs dependency port-B installed 2. port-B is installed 3. port-A is installed and marks its registry as being dependent on port-B and here is where things go wrong using sysutils/portupgrade: 4. port-B gets upgraded to port-B.1 and portupgrade reports port-A has a stale dependency. Then you run pkgdb -F and port-A's registry is changed to say it was built with port-B.1, portupgrade claims this fixes the registry when it really breaks it. Remember, port-A was built with port-B, not port-B.1 and the correct way to fix the stale dependency is to upgrade port-A so it is built with the newer dependency. sysutils/portmanager also updates ports, put it doesn't cheat. When port-B became port-B.1 portmanager will rebuild port-A using port-B.1 as the dependency. port-A's registry stays reliable, reflecting how the I don't see why any port should be rebuild just because a Port it depend on is updated. In more than 99% of all cases this is not needed. you whould en up in rebuilding openoffice or mozilla/firefox quite often. Correct me if im wrong. But most of the problem was caused by the fact that the installation directory of the perl modules has changed with the update. That's a Problem that ist unique to script languages like perl, ruby and python, and don't affect the vast majority of the Ports. Most ob the dependencies a of the type program A uses program B or program A uses a library ob program B. In both cases there is no need for an update of program A when program B is updated because programm a will work well with the new version of program b or more than just a recomile is needed to make it work with the new version. I might have helped if with the update of the perl ports all ports depending on perl would have been version bumped. So portupgrade had updated them with the perl port automaticly. I don't see where there is cheating with the update ob the dependency information. You install port A and port B. port B depends on port A. after some time you update port A to a new version. port B still works without a problem. But port B still has the dependency for the old version of port A. Some time later you try to delete program A. There is a hell of work to be done finding out if any of the ports still installed need this port if the dependency information is not consisten with the installed version numbers. The dependency infomation should reflect the information what other ports are needed and not the information which version of a port A was installed on the system on building time of port B. It should be the responsibility of a Port Maintainer to decide if a port has to be rebuild or not. A port maintainer can trigger a rebuild with a bump of the port revision. In case of such a widly dependen port like perl this bump could be done by the portmgr. A totaly different problem is the fact that the update of the perl port didn't update the information in /etc/make.conf. So the rebuild ob all dependend ports din't work until you called use.perl ports yourself after afterthe perl update. just my 2 cent. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | Privat: [EMAIL PROTECTED] | auf Anfrage/ Germany||on Request pgpi0095AEUmi.pgp Description: PGP signature
Re: Sil 3114 RAID controller issues with FreeBSD 5.3 Release AMD-64 - and Promise RAID controllers???
On Mon, Jan 10, 2005 at 02:26:34PM +0100, Olaf Greve wrote: Hi, Last Friday I ranted: In this case, time IS money, so that's why I'm trying to convince my client to better spend that money (and my time) on simply buying a supported hardware RAID controller, which really is a win-win situation for both my client and myself. However, somehow I've not yet been able to drive that argument home, so who knows...:/ Well, eureka, I did it! :) That is... I managed to convince the client to go hardware RAID. ;) They have a preference for the following controller: Promise FAST Trak S150TX4 But.. As far as I gather from the supported hardware list (fbsd 5.3, amd-64) at: http://www.freebsd.org/releases/5.3R/hardware-amd64.html#DISK It looks like this controller is not supported. :( To further compound matters, checking the docs on the controller suggests that, again, this is basically a software RAID solution (no CPU, no on-board memory, and a 66MHz PCI 2.2 32-bit interface): nice to complement their otherwise blazingly fast 64-bit AMD machine, duh! :((( Oh well, again I made a very strong suggestion to buy the Adaptec 2200s U320 SCSI RAID controller, but we'll see... :) Meanwhile, does anyone know of a good hardware SATA RAID controller capable of supporting RAID 10, and which is properly supported by FreeBSD 5.3 (amd64)? Any experiences? Any do's and dont's? Hi, I'am runnig some 3ware Storage Controllers on 5.2.1 and 5.3 on i386 Hardware. They work well. I use a 3ware 3W-8500-8 disk controller with 4 disks in Raid 5 Mode and some 3ware 3W-7006-2 disk controller with 2 disks in Raid 1 Mode. So far no problems with them. They react well on HotSwaps of defectiv disks (had one diskfailure allready). Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | Privat: [EMAIL PROTECTED] | auf Anfrage/ Germany||on request pgpxQ7cH4nKo0.pgp Description: PGP signature
Strange behavior of sysinstall
Hi, i´ve try to set up an pxeboot for automatic installation of my FreeBSD systems. Installing works without a problem. To do the custom setup I need for my servers, I have created a package and a post-install script for this package. The post Install script does some changes to /etc/rc.conf. I initializes a second network device and activates some auf the installed packages. That works fine. The script also add sshd_enabled=YES to /etc/rc.conf. When i do a cat /etc/rc.conf from the holographic shell everything seems OK but after reboot some of the additions are gone (some not all) The lines missing are inetd_enable=YES keymap=german.iso nfs_client_enable=YES ntpdate_enable=YES ntpdate_flags=... rpcbind_enable=YES sshd_enable=YES usbd_enable=YES the lines for the second Networkdevice and activation of the installed packages remain in the rc.conf. Bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | Privat: [EMAIL PROTECTED] |on Request pgptZGIEAohxJ.pgp Description: PGP signature
