Re: CVSup to local copy
At 9:00 AM +0800 12/12/03, [EMAIL PROTECTED] wrote: Hello, I need to update the sources of several servers in my network. I have already made a cvsup -g -L 2 cvs-supfile on one of the servers and placed all under /home/ncvs. I assume that /home/ncvs is a directory that is NFS-exported to all of your machines? Btw, you do not have to put your local copy of the CVS repository at /home/ncvs, even though that is the directory used for the master copy. However, you *do* want it to be on some directory which is local to each of your machines (local as far as CVS is concerned, I mean). NFS-mounted is fine, I believe, but you do not want to do 'cvs remote' operations with a repository the size of FreeBSD. Would anyone be so kind to tell me what to do next? Can't seem to find the concrete steps on the net. On each machine, log into root and: First, create a ~/.cvsrc file with at least the following two lines in it: checkout -P update -d -P And then you can: cd /usr rm -Rf src cvs -d /home/ncvs checkout -r BLAH src where the value of 'BLAH' will depend on which release you want to run on that system. RELENG_4 for stable, for instance. Or RELENG_4_9 for the 4.9-security branch. Or RELENG_5 for the more-daring current branch. Then you can 'cd /usr/src' and follow the standard instructions for building from source. Strictly speaking you don't *have* to do the above as userid root, but you will have to do the 'make installkernel' and 'make installworld' steps as root. You will want that ~/.cvsrc file in whatever userid you use for checking-out or updating the src via 'cvs'. Later on, when you want to update some system, you can just cd /usr/src cvs update -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD vs Samba machine account creation
At 1:12 PM + 11/30/03, Stacey Roberts wrote: Hello, Some time ago, I saw a thread on this list that had concluded that the adduser facility in FreeBSD had been amended so that samba machine accounts can be created with the required $ at the end of the desired machine user name. The 'pw' command was changed in freebsd-current to allow a '$' to be the last character of a userid or group name. This was done in January, and MFC-ed to freebsd-stable in February. This change is more significant in freebsd-current than freebsd-stable, because 'adduser' is a perl-script in freebsd-stable. It does not use the 'pw' command. In freebsd-current, 'adduser' was rewritten (because perl is no longer in the base system), and the rewrite depends on the 'pw' command. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: connection to remote printer is down
At 12:26 AM -0600 11/27/03, Charles Howse wrote: I have an HP1100 printer that I set up on machine moe with apsfilter, and is working perfectly. I'm trying to setup machine larry to print text only to the printer on moe, but I'm not getting anywhere. Jobs get into the local spool, but time out waiting on the remote machine to come up. I can ping the remote machine with no difficulty. I have the following in /etc/hosts.lpd: [EMAIL PROTECTED] ~]$ cat /etc/hosts.lpd # $FreeBSD: src/etc/hosts.lpd,v 1.4 1999/08/27 23:23:42 peter Exp $ # # See lpd(8) #machine.domain larry.howse.homeunix.net Here's larry's /etc/printcap: lp|hp1100:\ :lp=:rm=moe:rp=hp1100:sd=/var/spool/output/moe:lf=/var/log/lpd-errs: In your /etc/hosts.lpd file, you specify a fully-qualified name for 'larry'. But in your printcap file, you specified only 'moe', and not something like 'moe.howse.homeunix.net'. That seems a bit inconsistent to me, but I assume it is not too important. To me, it looks like lpd is not accepting remote connections on moe. That would happen if lpd is not being started during system startup, or if you have started it up with the '-s' (secure) flag. What do you see if you type the following command on moe: ps axuww | grep lpd And what startup-variables do you find on moe if you type the following command: grep lpd /etc/defaults/rc.conf /etc/rc.conf -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: connection to remote printer is down
At 1:26 PM -0600 11/29/03, Charles Howse wrote: On Saturday 29 November 2003 01:03 pm, Garance A Drosihn wrote: To me, it looks like lpd is not accepting remote connections on moe. That would happen if lpd is not being started during system startup, or if you have started it up with the '-s' (secure) flag. What do you see if you type the following command on moe: The -s flag was the problem. Thanks! FEATURE. It's a FEATURE...:-) May I ask another printer-related question? Using KDE, is there a way to change the quality or resolution of a print job on the fly? For example, when I open KEdit to print a file, I don't have an option to print in a different resolution or to lower the quality setting. I'm having to edit /usr/local/etc/apsfilter/hp1100/apsfilterrc and change things to suit me before each print job at a different setting. I don't use KDE or apsfilter, so someone else will have to answer this. If I understand what you're looking for, you might be able to get the effect you want by defining multiple print queues, with different options for each queue. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: printer/tcp: bind: Address already in use
At 4:47 PM -0800 11/17/03, K Anderson wrote: Hey there all. For quite some time I've been noticing messages on the primary console as well as the message log. inetd[630]: printer/tcp: bind: Address already in use I have cups installed and happen to notice something in the /usr/local/etc/rc.d director called lprng.sh. I have, as the file says, lpd_enabled/lpd_enable equal to NO inside quotes (yep, inside rc.conf) and the darn thing still starts up. Any ideas on fixing? Are things working, other than the annoying message? Are all the messages from the same process? And is that process really 'inetd'? If so, what kind of entries do you have in /etc/inetd.conf? -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: printer/tcp: bind: Address already in use
At 6:02 PM -0800 11/17/03, K Anderson wrote: Garance A Drosihn wrote: Are all the messages from the same process? And is that process really 'inetd'? If so, what kind of entries do you have in /etc/inetd.conf? Woa, thanks for the quick response. Just a matter of luck... :-) Yes, the process is really inetd. Since in the inetd.conf there is the following entry: printer 515/tcpspooler printer 515/udpspooler Are those lines really in your /etc/inetd.conf file? Those look more like lines from /etc/services. And the lprng.sh wants to load lpd from /usr/local/sbin. I do have cups-lpr installed but I don't recall this issue arising from it. I have no experience with cups-lpr or lprng, so I'm not sure what would be causing the problems you described. But anything named /usr/local/etc/rc.d/blah.sh will be executed at startup. (well, if it is marked as executable). I don't think inetd enters into that. But maybe the script launches another copy of inetd with a different config file. I killed the lpd process and the renamed lprng.sh to something like lprng.sh.runthisandyoudie. Now inetd doesn't complain. Of course I don't understand what application put it there. Try: pkg_info -W /usr/local/etc/rc.d/lprng.sh or pkg_which /usr/local/etc/rc.d/lprng.sh (pkg_which is under /usr/local/sbin, if you've installed the portupgrade port). You might have to move the file back to it's original name for those commands to work... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBsd , I REALLY need some help :-)
At 1:47 PM +0100 11/4/03, Nic Bergen wrote: Hi, I'm trying to install freebsd on an old i486 (75mhz) with 40mb ram I have two harddrives 260 and 349mb. Which version of FreeBSD are you trying to install? -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: problems with LPD
At 8:55 PM -0700 10/31/03, [EMAIL PROTECTED] wrote: Hi Garance. Thanks for your answer, ... I think that the solution to my dilemma, is modify the source code of LPD. But before this I like to try the netgroup option, where can I begin to read? Well, you can check: man hosts.lpd which will tell you almost nothing. Now it happens that the hosts.lpd is actually processed by the same code that handles hosts.equiv, although that is not documented. So, it happens to be true that: man hosts.equiv will tell you some additional hints as to what is available. However, you will notice that the man page for hosts.equiv does little more than point you to the source code. So, that is not very helpful either. There is also: man netgroup which will tell you the format of the /etc/netgroup file. I should mention that I have never actually used netgroups, so I am not sure that they will help you in this case. I have skimmed through all of the above, and my guess is that your original idea is probably the easiest one to do. It should be easier to change the source code in lpr/lpd/lpd.c to make it behave the way you want it to behave. Now that I have read more about netgroups, I expect that they are not very useful for what you really want to do. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with LPD
At 8:45 PM -0700 10/28/03, [EMAIL PROTECTED] wrote: I have a printer configured in the BSD, is working fine, now I need to enable that other systems print in this printer, to do this I add 2 lines to the file /etc/hosts.lpd 10.192.2.134 as_nte.intranet.telmex.com. but the remote system can't print, so I run lpd with -c flag to enable all the connections error via syslog. In the file /var/log/lpd-errs I have this message repeated Oct 28 20:25:11 bsdsis lpd[10575]: Host name for remote host (10.192.2.134) not known (8) why doesn't print, if the ip is in the file hosts.lpd? If I run the command host 10.192.2.134, it return me 3 names and one of them is as_nte.intranet.telmex.com You should only need the real hostname in /etc/hosts.lpd. You do not need to list the real IP address in addition to the hostname. To get the mapping between hosts and IP addresses to work, you would have to put an entry in /etc/hosts: 10.192.2.134 as_nte.intranet.telmex.com and then put just the line: as_nte.intranet.telmex.com in /etc/hosts.lpd Also, I like to enable the printers (all) in this server to be accessible to any one in the net 10. I saw your earlier question on this, and I believe the answer is that there isn't any good way to do this. You might be able to set something up with a netgroup, although that is not documented very well. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Smbd process not disconnecting
At 7:42 AM -0600 10/29/03, Charles Howse wrote: Note below, that the connection was opened on the 28th, but did not close, however the connection to Seeds closed about 4 mins after I opened it. Snippet from /var/log/moe.log [2003/10/28 12:11:13, 1] smbd/service.c:make_connection_snum(698) moe (192.168.254.4) connect to service WWW initially as user nobody (uid=65534, gid=65534) (pid 3064) [2003/10/28 15:31:04, 1] smbd/service.c:make_connection_snum(698) moe (192.168.254.4) connect to service Seeds initially as user nobody (uid=65534, gid=65534) (pid 3064) [2003/10/28 15:35:49, 1] smbd/service.c:close_cnum(880) moe (192.168.254.4) closed connection to service Seeds Am I way off target here, or do I have a process that isn't disconnecting when it should? How can I find out why the connection to WWW didn't close, and prevent that from happening in the future? I believe that what happens is that samba starts a process which handles connections as they come-and-go from the client machine. If you make additional connections, you'll notice that they all happen to 'pid 3064' (in the above example). I expect samba does this because there are times when the windows client will make a whole bunch of very short-lived connections, and it's better to have one process which keeps track of client-information than to rebuild all that information every time. I'm not much of an expert on the low-level details, but I can say that what you're seeing is also what I've seen, and that I believe samba is supposed to work that way. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Smbd process not disconnecting
At 1:22 PM -0600 10/29/03, Charles Howse wrote: Garance wrote: I'm not much of an expert on the low-level details, but I can say that what you're seeing is also what I've seen, and that I believe samba is supposed to work that way. I just checked again, and the connection was closed at 12:13 local time, about 24 hours later. I guess that's acceptable, as long as it *does* finally close on it's own. Thanks for the reply! I believe there's an option which controls how long that process will stay around. Glancing at my smb config file, it might be the one called dead time. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clarification on CVS Tags
At 11:00 AM -0800 10/28/03, Jason Williams wrote: Thanks Matthew for your explanation. You answered a lot of my questions. Makes sense now really. Just out of curiosity, why would someone want to use: RELENG_4_8_0_RELEASE? Is there some type of benefit? One would think that the best option for production servers is: RELENG_4_8 Thanks for your insight. The security or safe branches (such as RELENG_4_8) are relatively new. We still have to have tags such as RELENG_4_8_0_RELEASE for the release process, and you can use any tag for cvsup. Before the security branches existed, we used to encourage people to upgrade to those release-tags instead of upgrading to stable. There are still times when you might want to cvsup to a release point. Of course, once you do the buildworld for that point, then you'll never see any new changes until you switch to a different tag for cvsup. For instance, it might be quite reasonable to cvsup to a release tag, and once you know that worked you would then cvsup to some later release tag, or to RELENG_4 (stable). -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lpd setup for remote printer
At 2:17 PM -0400 10/15/03, Tom Parquette wrote: I'm trying to configure printing on the local machine (Stargate) to point to lp on P3R-272. This is what I currently have coded in Stargate's printcap file: lp|HP2000 on P3R-272:\ :sh:\ :sd=/var/spool/lpd/lp:lf=/var/log/lpd-errs:\ :rm=P3R-272.Tom.Parquette.name: If you do not have 'rp=' specified, then (iirc) lpd will assume you mean a local printer. Try addingrp=lp: to the above printcap entry. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/local/etc/rc.d/*sh and slow build world in FreeBSD 5.1
At 11:58 AM +0100 10/10/03, [EMAIL PROTECTED] wrote: 1) I can't get /usr/local/etc/rc.d/*sh to work. I don't have any ideas to offer on this. 2) Building kernels/worlds is MUCH slower than under 4.X. A kernel used to take around an hour; it's taking about 4 under 5.1 (Cyrix 166mhz/64Mb RAM). Is there still a lot of debugging code in 5.1 which could slow things down? a) I assume you've read /usr/src/UPDATING in your 5.x system, which explains some settings that you can look at if you are wondering about performance. b) the 5.x-series uses gcc 3.3.x for its compiler, while freebsd-4.x has stayed with gcc 2.94. gcc 3.3.x is definitely much slower at *compiling* code. If your only performance measurement is buildworld and buildkernel, then this difference in compile times is the reason for most of the slowdown that you're seeing. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Latest stable fixes are unstable
At 4:14 PM -0400 10/9/03, Jeffrey Wheat wrote: Apologies for being so vague... All that happens on the 4.8(4.9RC) servers is they suddenly reboot without leaving anything in the log files at all, so it is very difficult to provide more details on the crash. In the case of the 4.9 systems, are you VERY up-to-date? There were a few changes recently made which did cause problems for some users, but it should be true that all of those are now fixed. You'd pretty much want to be running *today's* sources to get all those. I think it should be telling you that the system name is 4.9-RC2 if it has (what we think are) all the fixes. (I might be wrong on that, I haven't actually rebuilt my 4.x machine yet this week). On the 5.0 servers, I get page faults. I am going to enable crash dumps on these servers now. I'm having some odd problems with 5.x-current right now, but I haven't been able to figure out what it is yet. In my case, it *might* still be a hardware problem, though it seems odd that I have zero trouble with 4.9 on the same hardware (and my problems with 5.x didn't start until this September). For me, the problem with the 5.x is that the machine completely locks up, which makes it a real hassle. It is also true that a week (or two?) ago there were changes to 5.x which caused problems for many people. Again, make sure you're up-to-the-minute with what you're running. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AFS Server + MAC + Jail
At 8:08 PM -0400 10/5/03, Kenny Freeman wrote: I'm using the latest release of openafs, plus I keep my entire system and kernel up to date with patches. ... Anyways, my question is really just about AFS and whether or not it works on 5.1-RELEASE. My understanding is that the server-side should work OK, but I don't know anyone who tried to run it in a jail. There is some work going on to get the OpenAFS client working on freebsd-current. You should follow the OpenAFS mailing list for more details. Some details show up on the special list for the freebsd port of OpenAFS, and some freebsd info shows up on the general-info mailing list. So, Check: https://lists.openafs.org/mailman/listinfo/port-freebsd https://lists.openafs.org/mailman/listinfo/openafs-info -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AFS - OpenAFS
At 10:27 AM -0400 10/3/03, Jerry McAllister wrote: I am wondering how I might go about connecting to an AFS cell on my FreeBSD 4.8 system. Any input would be helpful. Currently, as far as I know, there is no version of AFS client available for FreeBSD although I keep hearing about openAFS coming.I wish it would. We use AFS here and so have to use something besides FreeBSD on those systems that need AFS access - unfortunately. For 4.x systems, you might be able to use the ARLA port. It's an afs-compatible client. I *think* it works under the 4.x-branch, but I have never tried it. But, I suppose creating a complete OpenAFS has ... If someone has any more encouraging information than this, please post it and indicate where this can best be tracked. All that the OpenAFS client needs is more developers who have time to work on it. Recently Garrett Wollman has started to work on getting OpenAFS to work on freebsd 5.x. He is hoping that he won't break the progress which has been made on the openafs client for freebsd-4.x, but he does not have a lot of 4.x systems to test on, and he needs to concentrate on 5.x. The openafs project has a web site at http://www.openafs.org/ Recently a request went out to the openafs-info mailing list, for people to help test Garrett's changes on the 4.x branch. Ie, to take his changes for 5.x, and test those changes on 4.x to make sure that patches needed for 5.x will not cause problems for 4.x. There is also a openafs mailing list for the port of openafs to freebsd. So, Check: https://lists.openafs.org/mailman/listinfo/port-freebsd https://lists.openafs.org/mailman/listinfo/openafs-info -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wireless S-L-O-W Samba Domain Logon...
At 9:59 AM -0700 9/17/03, RA Cohen wrote: I needed to extend the reach of the wiring in one of the buildings and installed an SMC inexpensive router/access point running the latest and greatest 802.11G. ... Everything works but the domain logins are so slow as to be almost unuseable. Does that wireless access-point do NAT? We have our wireless connections behind a NAT box, and that does cause problems for things like WINS and some kinds of samba connections. I have no idea if that is related to what you are seeing, but if the box is doing NAT then that could be significant. I am not a samba expert though, so I can't really answer your question. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind query logging stops after a logrotate.
At 12:04 PM -0700 9/8/03, Charlie Schluting wrote:
FBSD 5.1:
Using Bind9.2.2, and I have query logging turned on:
logging {
channel querylog { file /var/log/query.lo~g; print-time yes; };
category queries { querylog; };
};
After a logrotate, it stops logging completely. The permissions
are correct, and all I have to do to make it start logging again
is: rndc reload.
Anyone heard of this? Any ideas?
What do you mean by a logrotate? Do you mean a run of the
newsyslog program? Or are you using some other program?
--
Garance Alistair Drosehn= [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Samba and $
At 1:41 PM +0800 8/12/03, Katinka Mills wrote: I thought in the version with Freebsd 4.8 that you could now use accounts with $ signs in them The 'pw' command has been changed so that you can create user accounts (and user groups) which end in a $. That's all samba should need. I'm pretty sure that change was included in 4.8-release. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lpd logging
At 3:13 PM +1000 8/5/03, jason fiddian wrote: help please we have lpd -l running to log daemon activities but where does it log to? It depends on what lines you have in /etc/syslog.conf. You would want to check /var/log/lpd-errs, and you may also see the lines in /var/log/messages. If /var/log/lpd-errs does not exist, then you would need to create it before syslog will start logging to it. also we can print header pages to the local printer but not the network printers whose queues are on the same host. any ideas please? If you are saying that you can *not* get a header page on the remote-printer (and you have that specified by 'rm=' in your printcap file), then there is probably some setting that you need to change on that printer. Does the printer have some menu-based command panel on it? Some of them might allow for a web-based configuration. Different printers will call this different things. Some might call it a banner page, some will call it a separator page (or a job separator page). -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: About newsyslog behavior
At 12:08 PM +0300 7/2/03, Jim Xochellis wrote: I suspected that some processes are confused because a *new* log file is created and these processes are making the assumption that their log file will be always the same and perhaps they open it once and then work with the FILE pointer. If a program responds to SIGHUP by re-opening all of it's files, then it really should re-open the log file. If the program does not re-open the logfile when it get a SIGHUP, then it is more accurate to say it is ignoring the SIGHUP (as far as that log file is concerned). Ie, there is no way that it is correct for the program to behave in the way you describe, if it is trying to do the right thing with the log file. I have confirmed that newsyslog actually creates a new log file (instead of copying it and then disposing its contents) by reading the source of the newsyslog.c file Yes, and that doen because it is the safest and most reliable way for it to rotate a logfile without any hitting any race-conditions. Having the above in mind, isn't it worthwhile to add an option in newsyslog in order to avoid the creation of a new log file when it is inconvenient? This does not seem like a good idea to me. It might work okay in the case where you are keeping no backup files, but it is a really bad idea if you want to rotate the information to backup files. Isn't it feasible to dispose the contents of the old log file instead of creating a new one? Anything that I am missing here? (giving the fact that I am not a unix guru, only a C programmer) If the program does not have some way to REALLY re-open the log file, then the file-pointer might also be pointing to a specific point in the file. Let's say it is at byte 125000 into the file. You empty the file. The next time the program writes to the log file, it will write to byte 125001 (depending on how the program is written). Some programs may work with this strategy, but others will not. I think you should look at the programs you are having trouble with, and see if there is some alternate way to get them to correctly handle the log file that you want to rotate. disclaimer: I am about to go on holiday/vacation for a few days, so all of the above comments were just my initial reaction. I realize this reply is not very helpful, but I'll try to write up something more helpful if no one else comes up with a good solution for you. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VMware2 build under -CURRENT ... is Broken?
At 3:49 PM -0700 4/1/03, Danilo Fiorenzano wrote: 5.0-CURRENT with sources cvsup'd on March 30. portinstall vmware2 aborts with: .../vmmon-only/freebsd/hostif.c: In function `FindMPN': .../vmmon-only/freebsd/hostif.c:186: invalid operands to binary *** Error code 1 Stop in /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only. Just wondering if the port is actually currently broken under -CURRENT or if it is something with my system. I would like to know if it builds OK for other people tracking HEAD. It happens that I rebuilt the vmware2 port on my machine on March 25th. That went OK. Just now I tried a force-rebuild of it, and I see the same error that you reported. So, it looks like something has changed in the system includes, and that is confusing the vmware2 port. (I say in the system, because the vmware2 port itself has not changed since I last built it). There were a number of other compile-time warnings before the one you listed. My guess is that /sys/sys/param.h might be getting pulled into the compile when it did not used to be pulled into it, but that is a very shaky guess. Please note that I am not likely to look into this any farther, because what I think I finally determined is that vmware2 simply does not work on my new PC (it builds fine, but crashes when I try to run it, on both stable and current). I still run it on my older PC, but that PC is running freebsd-stable, and needs to stay that way for now. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: customizing printcap to email file
At 3:33 PM -0500 4/3/03, David Banning wrote: what I would like to do is have windows boxes print to a unix printer filter which would convert the file into pdf format and put the file into a directory where it could be emailed out. Anyone tried this? First off, I tried modifying the printcap if= entry to take the file and save it as a file. That was a no go - I just got an error. This is should be workable, although there are probably a number of subtle details that you'll need to pay attention to. You will probably want to set a log file (lf=) for the printer, as some useful error messages might show up there. Other errors show up in /var/log/messages or /var/log/lpd-errs. What error did you get? Note that you'd want to set if= to an executable script, and that the script should just *read* from stdin and write to where you want it written. Eg: #!/bin/sh cat /tmp/somefile First try to get it to work by writing to a /tmp file. If you get that working, you can then move on to getting it to work more like what you really want. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Personal development CVS question
At 12:04 PM -0500 3/24/03, Steve Bertrand wrote: The current state of my app is ready for production, so I would like to take a snapshot of it as is, then implement it. I would like to leave this snapshot alone, and further develop in other aspects of the program now. Am I correct with this method?: - commit my current source and branch as RELEASE - download RELEASE onto production server and put into use - further work will continue normally, and the RELEASE branch will not be affected - when I am ready for the new features, I can re-branch to a new RELEASE, redownload onto production and repeat You generally want to use a special name for the release branch, such as RELEASE_1. When you later want to make a new release, you name that branch RELEASE_2. You may still want to work off the RELEASE_1 branch even though RELEASE_2 has been made. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: question on samba install
At 1:01 AM -0500 3/19/03, David Banning wrote: If I install samba without cups, is it still possible to print with samba? I have a small network with a few win boxes and the samba install is older. It doesn't have cups. I am just wondering, since samba now installs cups by default, whether it is actually -needed- for win boxes to print to the FreeBSD printers. From my understanding of the samba port, it will use CUPS by default *if* cups is installed. Otherwise it still uses standard bsd-lpr printing. There may be some environment variable that you'll have to set when building the samba port if you do not want the samba port to install the CUPS port. But it definitely works, if you want it to run that way. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Installing CUPS pkg
At 12:58 AM -0600 3/12/03, Bob McCarty wrote: JBMAC# make install === Installing for cups-1.1.18.0_4 === cups-1.1.18.0_4 is already installed - perhaps an older version? If so, you may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of cups-1.1.18.0_4 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Try: FORCE_PKG_REGISTER=YES make install (all as one line). Or try: make FORCE_PKG_REGISTER=yes install Note that the variable name is FORCE_PKG_REGISTER and not MAKE_PKG_REGISTER -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: machine accounts and samba
At 11:48 AM +0100 3/2/03, Per olof Ljungmark wrote: charles pelletier wrote: how do you add a machine account in samba? i've already added users using 'smbpasswd -a username password' but cannot for the life of me remember how to add a machine to the samba domain. man smbpasswd smbpasswd -m machine name Then vipw to add a $ before the name. I don't think you can add the $ with smbpasswd in FreeBSD. Somebody correct me if I'm wrong. It depends on what version of freebsd you are running. I recently committed a change to freebsd-stable so 'pw' will accept userids and groups with a last-character of '$'. That change is also in the freebsd-current branch. 4.8-release will probably be the first official release which will have that change. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 5.0-RELEASE under VMWare 3 : slowdown and even hangup
At 10:51 AM +0100 2/13/03, [EMAIL PROTECTED] wrote: I'm kinda in the same situation : XP Pro, WMWare 3.2, several virtual machines running fine (linux,w2k), but the freebsd 5-RELEASE is quite a pain to use in this env. The guest OS keeps on slowing down, to the point that it's unusable. Kris Kenna talked about a kernel option for fix this. The problem would be related to a specific opcode emulation done by VMWare. If you look in the file: /usr/src/sys/i386/conf/NOTES You will find an option called CPU_DISABLE_CMPXCHG You need to compile a kernel which has this option when running under VMWare. You can not use this option with the SMP option, but then you probably should not be using an SMP kernel when running under VMWare! I realize you then have the problem of how to compile the new kernel when it takes so long to do anything with the standard GENERIC kernel. Perhaps it would go better if you booted up in single-user mode, and then compiled and installed the new kernel. However, that is just a guess on my part. It would probably be easier to get someone else to compile a 5.0-release kernel with that CPU_DISABLE_CMPXCHG option. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: printing error
At 8:44 PM -0800 2/8/03, chip wiegand wrote: I just setup my new Epson C62 printer, works great on my freebsd box. I am using samba to share it with the rest of the family pc's. They see it in network neighborhood, connect, install the drivers, all fine. but the test page won't print. Nothing appears in the queue with 'lpc stat all'. In the samba log I get the following error - printing/print_cups.c:cups_queue_get(731) Unable to connect to CUPS server localhost - Connection refused As I mentioned, I'm using samba, so why am I getting cups errors? How do I disable cups, it's not a running process that I can find. You probably built samba without the magic environment variable that causes it to skip CUPS. That probably resulted in CUPS being installed. And the error message is because samba is *expecting* to connect to CUPS, but that is failing. Thus, there is no CUPS process actually running. Re-check what makefile options you have when building the samba port. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: FreeBSD 4.7-RELEASE and X11R6 build on 5.0-CURRENT in one set
At 9:15 PM +0700 1/16/02, Pavel Burovsky wrote: Excuse me for, perhaps, plaqued question. FreeBSD 4.7-RELEASE (I obtained it from www.linuxcenter.ru) contains the XFree86 server built on 5.0-CURRENT snapshot(anyway it so reported by XFree86 server). Is it normal? FAQ says it's not. I would pleased for every answer :) It does sounds odd, but it isn't necessarily wrong. Are you seeing any problems with it? If it was really built on a 5.0-system, then I would expect that it would not even start to run on a 4.7-release system. Also note that the computer you sent that message on seems to be living in the wrong year. The timestamp on your message says January 16 2002, but we're now in 2003. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: lpd/lpr stopped working
At 8:39 PM +0100 2/3/03, Bjarne Wichmann Petersen wrote: Hi! I'm a bit pussled. I can print from OpenOffice and Phoenix. But konq chokes: A print error occured. Error message received from system: /usr/local/bin/lpr -P 'laserjet' '/var/tmp/kde-mekanix/kdeprint_pYNslYF' : execution failed with message: lpr: unable to print file: server-error-service-unavailable Note that the message refers to '/usr/local/bin/lpr'. You have probably installed some port which (one way or another) installed an alternate version of lpr. The behavior you will see from different applications will depend on what PATH they are using when they run. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Managing /etc/hosts.lpd??
At 1:19 PM -0500 1/28/03, Bill Moran wrote: Mark wrote: Is there a better way to manage lpd permissions than specifying individual hosts in /etc/hosts.lpd? I have a heterogeneous network here (there are a few Winder's machines in addition to a bunch of Unix machines) that has a bunch of machines on it, all of which are listed in a local DNS server. What I'd really like to be able to do is just say: Allow any machine from this local domain to connect to lpd. The documentation for hosts.lpd doesn't help out on format here, and the source code for lpd.c seems to confirm that there is, indeed, no wildcarding supported. Any other options? I wouldn't normally chime in like this, but I want to add a me too here. In my case it would be perfectly acceptable to eliminate all host checking on the part of LPD, since the LPD port is firewalled off from everything but our local network anyway. Haven't been able to find any way to do this (or what Mark asks for) in the docs anywhere. Am I missing something? The docs do not admit this, but iirc you can list a netgroup in your /etc/hosts.lpd file. Unfortunately, that is not a useful or convenient option for many users. I have been thinking I should add simple pattern-matching support, but I haven't decided exactly how I'd like that to work. I will move that higher in my list of things to do to lpr. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: printing over the network
At 8:02 PM +0200 12/21/02, [EMAIL PROTECTED] wrote: Are you using lpd or lprng (have to get that out of the way) lpd Is lpd running / listening? - Show me iulian#ps -ax | grep lpd 4544 ?? Is 0:00.01 lpd What does lpc status all return? Nothing What version of freebsd are you running? if 'lpc status all' returns nothing, then that indicates that lpd/lpc believes you have no printers defined. What do you get from: chkprintcap ? When lpd starts up, are there any messages written to /var/log/messages? -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Interest in diskless booting?
At 12:54 PM -0800 12/8/02, Gary W. Swearingen wrote: I mostly-wasted a bunch of time investigating web sites and articles which had schemes for diskless booting, and then discovered that the picobsd manpage told me everything I needed to know (to set up a non-harddisk filtering bridge booting off a floppy) in a staightforward, non-confusing manner. PicoBSD is great if you want to do what PicoBSD is geared for, but many people can think of their own custom systems that they would like to have burned on a CD-ROM. Not pico small, but still much less than the full-blown freebsd, and does not require a working hard disk to run. For those people, PicoBSD is *too* successful at being small. Besides, if you had a nice book with an accurate and detailed info on how to do build such systems, then you wouldn't have to waste any time searching those web sites... :-) Another example of where this information is useful is for hardware like the small, diskless boxes at http://www.soekris.com/. One of the CS grad students set up freebsd on a box like that, and gave a presentation of it at a local Unix users group, and everyone was very interested in what he had done. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Interest in diskless booting?
At 12:48 PM +1030 12/8/02, Greg 'groggy' Lehey wrote: I was at a local installfext yesterday (http://installfest.auug.org.au/), and a number of people were interested in doing diskless booting, either for reasons of economy or reliability. I'm currently about to finish the manuscript of the fourth edition of The Complete FreeBSD, and I was wondering if there was enough interest in this topic for me to include it in the book. If *you* are interested, please let me know. I'll make a decision depending on the amount of feedback I get. There's at least two cases, right? diskless booting off something like a custom CD-ROM, and diskless booting over the network? One of the students here at RPI worked on a project for the custom cd-rom idea. It's at http://www.sourceforge.net/projects/freebsdtogo/ He's used this to make CD's which boot up a laptop, and run without touching anything on the hard disk. I know he has it working for the 4.x-branch, and I believe he also updated it for the 5.0-current branch. This is very useful for having students use there laptops to take tests, while having the instructor have complete control over what they are running. (and not having to worry about the state of things on the student's hard disk) -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Interest in diskless booting?
At 12:28 AM -0500 12/8/02, Garance A Drosihn wrote: At 12:48 PM +1030 12/8/02, Greg 'groggy' Lehey wrote: If *you* are interested, please let me know. I'll make a decision depending on the amount of feedback I get. There's at least two cases, right? diskless booting off something like a custom CD-ROM, and diskless booting over the network? One of the students here at RPI worked on a project for the custom cd-rom idea. It's at http://www.sourceforge.net/projects/freebsdtogo/ Uh, the point of me mentioning this is that the project is still in testing stage (*), he has made no effort to promote the project, and yet he has gotten a fair amount of interest in it. So, I expect many people would be interested in the issues involved with making such a setup. (* - it works fine for his specific needs, but it could probably use some more polish so others could easily use it) -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problem pulling particular directory from CVS
At 1:43 PM -0800 11/26/02, Paul A. Scott wrote: From: Dan Nelson [EMAIL PROTECTED] Are you maybe running out of space on your local drive? You might also have a corrupted CVS repo, but I don't think you'd be getting those errors in that case. No, I have over 40GB available on the filesystem. CVSROOT is set to :pserver:[EMAIL PROTECTED]:/home/ncvs so, if the repository is corrupt, then someone else has to fix it. It's possible that it's the /tmp directory on the remote side which is running out of disk space. CVS does not work well over a remote connection, when dealing with a very large repository. If I had 40-gig to play with, I would much rather cvsup the CVS tree to my local hard disks, and then CVS to *that* repository. In fact, that's exactly what I do, on all my freebsd machines (except my sparc), and most of my machines have less than 10-gig available. This is much better for everyone involved, if you have an extra 2 gig or so that you can use for holding the repository. (extra in addition to the space you'll need for /usr/src when you check it out from your copy of the repository). -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: xargs -J
At 10:10 PM -0500 11/25/02, David S. Jackson wrote:
Hi,
I've been trying to use |xargs -J [] mv [] [].suffix
but to no avail.
I've tried |xargs -J mv \[\] \[\].suffix and variations but that
doesn't seem to work either. It seems to work fine with the -i
command under GNU xargs, but not under Freebsd.
If you're using '-i' with GNU xargs, then you probably don't want
'-J' on the xargs in freebsd. -J is meant to solve a problem that
can not be handled via -I.
An example would be
$ touch one two three
$ ls one two three | xargs -J [] mv [] [].suffix
I should now have one.suffix two.suffix three.suffix. At least,
that's what happens with GNU and the -i \{\}. (FreeBSD manpage
says to use -J [] without escapes though.)
Can anyone lend me a clue here please?
The man page for xargs says:
Furthermore, only the first occurrence of the
replstr will be replaced.
in the description of -J.
For your example, what you should use is -I, not -J.
--
Garance Alistair Drosehn= [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Samba taking too long to upload files.
At 6:56 AM -0800 11/4/02, Roberto Armenteros wrote: The download process is very fast, but not the upload process. When I upload to my other windows machine it goes five times as fast as my bsd box. What could be the problem? Make sure your ethernet card has the correct setting wrt half-duplex vs full-duplex. I had a situation where the card was assuming a half-duplex connection, but the network port (on the gateway) was hardwired to 100Mbit full-duplex. The performance penalty for samba file transfers was enormous. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: samba printing stopped after upgrade to 2.2.6
At 12:03 PM -0500 10/28/02, Vivek Khera wrote: DN == Dan Nelson [EMAIL PROTECTED] writes: but I have not enabled CUPS in samba at all. Does anyone know what I need to do to migrate successfully from samba 2.2.5 to 2.2.6? Here's my config: DN When you did the install, you probably just skipped that options dialog DN that came up, right? All the options on that page are select to DN enable, except CUPS which is select to _disable. Rebuild samba, and DN select the Without CUPS line. Quite annoying. I work around it by DN adding WITHOUT_CUPS=yes in /etc/make.conf, and setting BATCH=yes in DN net/samba/Makefile. CUPS is linked in both 2.2.5 and 2.2.6, but in 2.2.6 it seems to want to actually *use* it even though I don't configure it. Also, if I select the Disable CUPS flag, all it accomplishes is to not register the dependency. CUPS is still linked for some reason. Does your smbd have cups linked (as reported by ldd)? Be a little careful here. It sounds like you: 1) installed samba-with-cups a) which by definition would install CUPS, if you did not already have it installed. 2) backed off to previous version of samba a) which backs out the version of *samba* that was installed, but probably does not back out versions of any other ports which were installed while installing a new samba. 3) installed samba-without-cups a) ...but CUPS is probably still installed. b) if so, the configure scripts for samba will notice that CUPS is on the machine, and will probably use it. This would be the correct behavior, IMO, because if you *do* have CUPS installed then samba *should* use it. Some of that is just guessing on my part, but it sounds pretty plausible. I would suggest that you see if CUPS is installed. Also check to see if it is a recent install. If so, then /usr/local/sbin/pkg_deinstall cups and then try the samba-without-cups install once again. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: LPD protocol screwup and ctl_renametf error
At 1:12 PM -0400 10/18/02, TheGlenMann wrote: Docs on the subtleties on LPD seem to be in short supply. It looks like the PAGEPROTECT thing breaks the whole system, then the cannot rename seems to be Windows trying again to send the file... How can I determine what is wrong? I suspect that permissions are preventing transfer of the actual print file (given on the l line), as I cannot find it on the system. I do a lot of the support for lpr/lpd in freebsd. From a quick look at your message, I suspect that the windows side is not doing the right thing when it comes to sending the data-file for a print job. I'll try to take a longer look at your report, and give you a better answer within the next few days. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Help debugging printing
At 1:50 PM -0400 10/6/02, Gerard Samuel wrote: I setup and installed a printer yesterday, and installed LPRng and apsfilter from ports (fresh cvsup), and had apsfilter print out that funky test page. In continuing the setup the box, I am trying to print a file, and getting these results - hivemind# lpr lprng.sh lpr: Unable to connect to /var/run/printer: No such file or directory lpr: Check to see if the master 'lpd' process is running. jobs queued, but cannot start daemon. This probably means you are executing the version of 'lpr' which is in the base system, which is not the version from lprNG. You would want to get the version in /usr/local/bin/lpr. - The lpd daemon is running. hivemind# ps aux | grep lpd daemon 530 0.0 0.3 1476 1096 ?? Is1:07PM 0:00.00 lpd: lpd Waiting (lpd) I expect this is the version of lpd that comes with lprNG (which, of course, is what you wanted). The base-system lpr will not work with it. I ran LPRng's checkpc utility and got this - hivemind# checkpc Warning - lp: cannot open lp device '/dev/ulpt0' - Permission denied I know for a fact that /dev/ulpt0 exists, so I deleted it and created it again. hivemind# rm ulpt0 ./MAKEDEV ulpt0 ls -al ulpt0 crw--- 1 root wheel 113, 0 Oct 6 13:46 ulpt0 Does anyone know where my problem may be?? This part is all lprNG specific, so I have no idea what you need to do. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: /var/run/printer?
At 6:30 PM -0700 7/23/02, Ed Yu wrote: When I try to run 'lpc restart all', it shows lp: cannot open lock file lp: lpc: unable to connect to /var/run/printer: no such file or directory lpc: check to see if the master 'lpd' process is running. couldn't start daemon However, ps aux shows that lpd is running daemon 138 lpd: lpd waiting(lpd) ls -l /var/run shows lpd.515 and lprng but no /var/run/printer I read that /var/run/printer should be created by lpd but it is not. Why? The version of lpd which comes as part of freebsd does use /var/run/printer for communication between various processes (lpd, lpr, lpc, etc). This version of lpd should be on your system in /usr/sbin/lpd . The fact that you got that error message from lpc indicates that you were definitely running the version of lpc which also comes as part of the base freebsd operating system. You do have an lpd process running, but you say it shows up in 'ps' as: lpd: lpd waiting(lpd) The version of lpd which comes with freebsd would not show up that way. You also said /var/run had a file for 'lprng'. I do not run lprNG, but I expect that you have installed it, and that you have it running. It may even be working perfectly fine. The problem could be as simple as that you're using the base-system lpc, when you want to be using the version of 'lpc' which came with the lprNG package. The base-system lpc is in: /usr/sbin/lpc while I suspect that lprNG would have one in: /usr/local/sbin/lpc So, everything might be working perfectly fine, except that you do not have '/usr/local/sbin' in your setting for PATH. Thus, you are getting the system version of lpc instead of the lprNG version. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: /var/run/printer?
At 3:34 PM -0700 7/24/02, Ed Yu wrote: You are right. When I restart the machine after I uncommented LPD_ENABLE=YES, /var/run/printer shows up. I also did check /usr/local/sbin and there are lpc and lpd in it. I basically totally mixed LPR and LPRng. Hmm. I am not completely sure I understand what you did. It sounds like now you might have both the standard lpr and the alternative lprNG running. You only need to have one of them running. You just need to make sure you are using the versions of 'lpc' and 'lpr' which match the version of 'lpd' that you are using. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Question on order and targets of kernel and world builds
At 11:04 PM -0400 7/16/02, John Mills wrote: Hello - I would appreciate a bit more information on the 'world' and 'kernel' building process. Please point me at the right section of the Handbook or Greg's book if there is a succinct description. I have been doing 'CVSUP' followed by: # make buildworld # make installworld # make buildkernel # make installkernel without really knowing if this was a useful order or exactly what I was accomplishing with each target. You should check: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html for more details that you probably even need to know (because it includes information for older releases of freebsd). If you are fairly up-to-date with freebsd-stable, the preferred order would be more like: *READ* /usr/src/UPDATING [every time, just to make sure there are no special issues with this specific snapshot of freebsd] mergemaster -p make buildworld make buildkernel make installkernel [reboot, to make sure the kernel at least boots up] get into single user mode [usually by booting into it in the above step, although I often cheat on that...] make installworld mergemaster [go thru all the questions from mergemaster] reboot into your new world. You do not want to install the new world before you know whether the kernel that matches it will work on your hardware. If the kernel does *not* work (and I have had cases where this happens, although not very often on freebsd-stable), then you can easily back out by just renaming the kernel-related files in '/'. If you have done the installworld and *then* find out the new kernel does not work, well, you'll be in a world of hurt. Many people will try things in a different order, and will happen to have it work, and will thus insist that their order is the correct order (and usually that it saves them a lot of time). Their order may even work for six to eight months at a stretch, which they consider proof that it is a perfectly correct order. The documented order is the order you should stick with, because it's the only order that we actively *try* to keep working. If some other order happens to work, feel free to use it, but do not come complaining to us for the update where that alternate order does NOT happen to work... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
